All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: HDA codec in embedded device
Date: Thu, 31 May 2012 10:02:21 -0600	[thread overview]
Message-ID: <4FC7960D.6000405@wwwdotorg.org> (raw)
In-Reply-To: <20120531061302.GA11605@avionic-0098.adnet.avionic-design.de>

On 05/31/2012 12:13 AM, Thierry Reding wrote:
> Hi,
> 
> I work on an Atom-based platform that uses a Realtek ALC892 codec connected
> via HDA. The current code in patch_realtek.c seems to assume a standard
> desktop setup and maps the ports accordingly. The setup that I have is
> entirely different and involves, among other things, to reconfigure some of
> the ports typically used as outputs as inputs and vice versa. It'll also need
> to provide a way to pass through some inputs on the outputs without going
> through the DAC.
> 
> All of these features are supported by the ALC982, but I don't see how this
> could be implemented with the current driver. My question is how this could
> possibly be solved in a way acceptable for mainline?

The way I solved this was to add a machine-specific fixup rto
alc269_fixups[] that set up the pin default registers as required by the
HW prior to the parser interpreting those fields. I assume the same
would work on the alc982.

I think in general as Takashi mentioned, the driver assumes that the pin
default registers are already set up to values correct for the HW.
Typically, I believe this is done by the SBIOS or audio card BIOS prior
to the OS starting, or perhaps by EEPROM/straps in the HW. Is there a
way that can be made to happen?

  parent reply	other threads:[~2012-05-31 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31  6:13 HDA codec in embedded device Thierry Reding
2012-05-31  7:57 ` Takashi Iwai
2012-05-31 16:02 ` Stephen Warren [this message]
2012-05-31 16:52   ` Thierry Reding
2012-05-31 17:54     ` Takashi Iwai

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=4FC7960D.6000405@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=thierry.reding@avionic-design.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.