From: David Henningsson <david.henningsson@canonical.com>
To: Andres Cimmarusti <acimmarusti@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
"tiwai@suse.de" <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"660111@bugs.debian.org" <660111@bugs.debian.org>,
Stephen Warren <swarren@nvidia.com>
Subject: Re: multiple, non-physically accesible, HDMI devices listed for Intel IbexPeak ALC269VB
Date: Thu, 23 Feb 2012 09:30:44 +0100 [thread overview]
Message-ID: <4F45F934.7040409@canonical.com> (raw)
In-Reply-To: <CAH=dYrGuG0WfBFAMVmJdT28pckZ3TXutRq61-K++ui5VXSr+YQ@mail.gmail.com>
On 02/23/2012 01:01 AM, Andres Cimmarusti wrote:
>> If the new two pins can be never used, i.e. physically unreachable,
>> we may disable these pins by giving the proper default pin-config
>> values. Usually it's a job of BIOS. But if BIOS doesn't do it, user
>> need to do it manually.
>>
>> Build your kernel with CONFIG_SND_HDA_HWDEP=y,
>> CONFIG_SND_HDA_RECONFIG=y, CONFIG_SND_HDA_PATCH_LOADER=y.
>> I guess most of distro kernels are built with them.
>> Then create a file containing below in /lib/firmware, such as,
>> /lib/firmware/ibx-hdmi:
>>
>> ================================================================
>> [codec]
>> 0x80862804 0x80860101 3
>> [pincfg]
>> 0x04 0x411111f0
>> 0x06 0x411111f0
>> ================================================================
>>
>> Now pass this file to "patch" module option for snd-hda-intel.
>> For example, create a file in /etc/modprobe.d/,
>> e.g. /etc/modprobe.d/50-hdmi.conf, containing the line
>>
>> options snd-hda-intel patch="ibx-hdmi"
>>
>> Then reload the driver or reboot. This will disable pins 0x04 and
>> 0x06 so that only the pin 0x05 will be used.
>
> I've tested this workaround and it works well. I don't suppose this
> could be added as a quirk to the kernel for this particular device?
> (when and only if there's only one physically accessible HDMI
> connector).
Stephen, could you comment on this? Are we guaranteed a certain board
configuration (i e which pins are physically connected or not) given a
PCI SSID, or anything else that can be used as a key to a quirk table? I
think I've asked you before and that the answer was "no", but my memory
could be failing me.
>> There are ways to configure pulseaudio to allow the user to select which
>> PCM device to use on a given sound card. David Henningsson made this work
>> for NVIDIA GPUs at least in Ubuntu, and I imagine the same technique
>> could be applied to Intel devices too.
>
> Mmm.. just in Ubuntu? was this work submitted upstream? It appears
> there are some related fixes shown in the Ubuntu pulseaudio changelog:
>
> http://changelogs.ubuntu.com/changelogs/pool/main/p/pulseaudio/pulseaudio_1.1-0ubuntu9/changelog
>
> I found a thread related to this issue here:
> http://www.mail-archive.com/pulseaudio-discuss@mail.0pointer.de/msg07433.html
> Started by yourself Stephen Warren! but it doesn't seem like it got anywhere...
>
>> As Takashi mentions, from a kernel perspective, this isn't really a
>> regression at all, but simply exposing all the features of the HW that
>> were previously hidden. Without that change, others can't use some HW
>> usefully at all. Unfortunately, pulseaudio makes some rather simplistic
>> assumptions about how HW works by default, and can be confused by the
>> additional features that are exposed.
>
> Agreed. But in the case of laptops, I don't think I've ever seen one
> that actually has more than one physical connector. I'm a little
> puzzled as to how all these outputs (in my case 3) make sense for my
> hardware...
Even if there is only one HDMI output, it's it not that uncommon,
actually. Many DVI outputs can output HDMI audio as well (when connected
through an HDMI monitor through DVI->HDMI adapter), and DisplayPort also
has audio support.
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2012-02-23 8:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 6:43 Bug#660111: multiple, non-physically accesible, HDMI devices listed for Intel IbexPeak ALC269VB Andres Cimmarusti
2012-02-22 7:44 ` Takashi Iwai
2012-02-23 6:46 ` David Henningsson
2012-03-03 23:36 ` Bug#660111: [alsa-devel] " Andres Cimmarusti
2012-03-04 2:43 ` David Henningsson
2012-03-05 14:39 ` Takashi Iwai
2012-02-22 16:45 ` Stephen Warren
2012-02-22 21:52 ` Jonathan Nieder
2012-02-23 0:01 ` Bug#660111: " Andres Cimmarusti
2012-02-23 0:39 ` Stephen Warren
2012-02-23 8:30 ` David Henningsson [this message]
2012-02-23 16:17 ` Stephen Warren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F45F934.7040409@canonical.com \
--to=david.henningsson@canonical.com \
--cc=660111@bugs.debian.org \
--cc=acimmarusti@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=jrnieder@gmail.com \
--cc=swarren@nvidia.com \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).