From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: Add WM1811A audio CODEC to Arndale bindings
Date: Wed, 24 Jul 2013 10:50:38 +0900 [thread overview]
Message-ID: <0deb01ce8810$3295b790$97c126b0$@org> (raw)
In-Reply-To: <20130702092507.GV27646@sirena.org.uk>
Mark Brown wrote:
>
> On Tue, Jul 02, 2013 at 10:51:36AM +0530, Tushar Behera wrote:
>
> > Arndale board also comes with two other audio codec boards - ALC5631Q
> > and AK4678. Different audio codec boards came with different shipments.
>
> This is the default though and since they didn't bother providing any
> way of identifying the modules we just have to put them all in the
> device tree and hope that the individual CODEC drivers can do runtime
> identification (the WM1811A can but I don't know about the other two,
> nobody supported them upstream).
Basically, I agree with Mark Brown's opinion, at this moment would be better
if upstreamed WM1811A could be supported on Arndale and if further
supporting of two codecs is required, we could discuss again next time. And
they should be identified in the kernel at runtime.
- Kukjin
next prev parent reply other threads:[~2013-07-24 1:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 21:36 [PATCH 1/3] ARM: dts: Put Arndale fixed voltage regulators on a simple-bus Mark Brown
2013-07-01 21:36 ` [PATCH 2/3] ARM: dts: Hook up supplies for Arndale S5M8767 Mark Brown
2013-07-01 21:36 ` [PATCH 3/3] ARM: dts: Add WM1811A audio CODEC to Arndale bindings Mark Brown
2013-07-01 21:47 ` Fabio Estevam
2013-07-01 22:38 ` Mark Brown
2013-07-02 5:21 ` Tushar Behera
2013-07-02 9:25 ` Mark Brown
2013-07-24 1:50 ` Kukjin Kim [this message]
2013-07-05 23:36 ` [PATCH 1/3] ARM: dts: Put Arndale fixed voltage regulators on a simple-bus Tomasz Figa
2013-07-06 9:19 ` Mark Brown
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='0deb01ce8810$3295b790$97c126b0$@org' \
--to=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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