alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jorge Fernandez Monteagudo <jorgefm@cirsa.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Support new HDA codec
Date: Mon, 27 Feb 2012 14:07:39 +0000	[thread overview]
Message-ID: <20120227140739.GG3191@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AB277FB27524F74C87ACAFF84F2767490D56E514A4@NTMBOX.central.cirsa.com>


[-- Attachment #1.1: Type: text/plain, Size: 947 bytes --]

On Mon, Feb 27, 2012 at 03:01:11PM +0100, Jorge Fernandez Monteagudo wrote:
> > Mark Brown wrote

> > It should be very standards confirming and not require any magic Wolfson
> > specific verbs to use the functionality, a generic HDA driver should do
> > fine with an appropriate setup from the BIOS.

> With the generic HDA the only enabled path is DAC1 and PORT-A, the first
> it founds. In our carrier design we only use the stereo differential and
> SPIDF outputs. I've implemented a 'patch_wolfson.c' in order to enable these
> outputs and share the stream through both outputs, because I've no access
> to the BIOS code. The inputs are not used in our carrier, then I've not
> implemented anything.

Please share this code.  

Whatever is being done to work around the BIOS probably ought to be
board specific, even if the BIOS is not configurable hopefully there's
enough information been added to distinguish the board.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2012-02-27 14:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-21 11:14 Support new HDA codec Jorge Fernandez Monteagudo
2012-02-24 15:51 ` Takashi Iwai
2012-02-25 11:50   ` Mark Brown
2012-02-25 18:02     ` Takashi Iwai
2012-02-27 13:51       ` Mark Brown
     [not found]         ` <AB277FB27524F74C87ACAFF84F2767490D56E514A4@NTMBOX.central.cirsa.com>
2012-02-27 14:07           ` Mark Brown [this message]
     [not found]             ` <AB277FB27524F74C87ACAFF84F2767490D56E514C0@NTMBOX.central.cirsa.com>
2012-03-05 12:16               ` Mark Brown
2013-08-25  9:44         ` Mikel García
2013-08-26 12:39           ` 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=20120227140739.GG3191@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jorgefm@cirsa.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).