summaryrefslogtreecommitdiffstats
path: root/Documentation/sound/alsa/HD-Audio.txt
diff options
context:
space:
mode:
authorTakashi Iwai <tiwai@suse.de>2010-03-01 12:38:54 +0100
committerTakashi Iwai <tiwai@suse.de>2010-03-01 12:38:54 +0100
commita91a4aa1ee994abeb2190a1bb2f703933609a703 (patch)
tree1237ed9b6784e5c260245ccf3dde389c3125311d /Documentation/sound/alsa/HD-Audio.txt
parent12c2a682b55a40f2a986e36d6632110029bc63a5 (diff)
parent61c2d2b5e7241d4410ab8227ef4f76c1aba8210b (diff)
downloadtalos-obmc-linux-a91a4aa1ee994abeb2190a1bb2f703933609a703.tar.gz
talos-obmc-linux-a91a4aa1ee994abeb2190a1bb2f703933609a703.zip
Merge branch 'topic/hda' into for-linus
Diffstat (limited to 'Documentation/sound/alsa/HD-Audio.txt')
-rw-r--r--Documentation/sound/alsa/HD-Audio.txt27
1 files changed, 27 insertions, 0 deletions
diff --git a/Documentation/sound/alsa/HD-Audio.txt b/Documentation/sound/alsa/HD-Audio.txt
index 6325bec06a72..f4dd3bf99d12 100644
--- a/Documentation/sound/alsa/HD-Audio.txt
+++ b/Documentation/sound/alsa/HD-Audio.txt
@@ -452,6 +452,33 @@ Similarly, the lines after `[verb]` are parsed as `init_verbs`
sysfs entries, and the lines after `[hint]` are parsed as `hints`
sysfs entries, respectively.
+Another example to override the codec vendor id from 0x12345678 to
+0xdeadbeef is like below:
+------------------------------------------------------------------------
+ [codec]
+ 0x12345678 0xabcd1234 2
+
+ [vendor_id]
+ 0xdeadbeef
+------------------------------------------------------------------------
+
+In the similar way, you can override the codec subsystem_id via
+`[subsystem_id]`, the revision id via `[revision_id]` line.
+Also, the codec chip name can be rewritten via `[chip_name]` line.
+------------------------------------------------------------------------
+ [codec]
+ 0x12345678 0xabcd1234 2
+
+ [subsystem_id]
+ 0xffff1111
+
+ [revision_id]
+ 0x10
+
+ [chip_name]
+ My-own NEWS-0002
+------------------------------------------------------------------------
+
The hd-audio driver reads the file via request_firmware(). Thus,
a patch file has to be located on the appropriate firmware path,
typically, /lib/firmware. For example, when you pass the option
OpenPOWER on IntegriCloud