From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH 1/3] ASoC: bt-sco: enable OF support
Date: Tue, 6 Aug 2013 18:04:30 +0100 [thread overview]
Message-ID: <20130806170430.GL6427@sirena.org.uk> (raw)
In-Reply-To: <CAGsJ_4w3fS=vzZmeJOxhKO1TdL9d6pgbrjtzfPugOSOprLV+nw@mail.gmail.com>
On Tue, Aug 06, 2013 at 08:09:18AM +0800, Barry Song wrote:
> 2013/7/17 Mark Brown <broonie@kernel.org>:
> > There is likely to be a control interface for the BT device hanging off
> > a UART but it's not clear there's much more meaningful data for those
> > than there is here.
> so the idea is that we don't add codec platform device in uart, and we
> add a dt node for it as we are doing here?
Well, I think it's more OK to add a node like this one (possibly with a
link to the UART) but if you can add it based on it hanging off the UART
that's even better.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130806/e86652a7/attachment.sig>
next prev parent reply other threads:[~2013-08-06 17:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 6:12 [PATCH 1/3] ASoC: bt-sco: enable OF support Barry Song
2013-07-17 6:12 ` [PATCH 2/3] ASoC: hdmi-codec: " Barry Song
2013-07-17 8:49 ` Mark Rutland
2013-07-17 9:57 ` Mark Brown
2013-08-06 0:03 ` [alsa-devel] " Barry Song
2013-07-17 6:12 ` [PATCH 3/3] ASoC: hdmi-codec: let the driver support HDMI sink Barry Song
2013-07-17 9:52 ` Mark Brown
2013-07-17 8:40 ` [PATCH 1/3] ASoC: bt-sco: enable OF support Mark Rutland
2013-07-17 9:47 ` Mark Brown
2013-08-06 0:09 ` [alsa-devel] " Barry Song
2013-08-06 17:04 ` Mark Brown [this message]
2013-08-07 7:59 ` Barry Song
2013-08-07 14:46 ` Mark Brown
2013-08-09 8:41 ` Barry Song
2013-08-11 11:05 ` Mark Brown
2013-07-17 15:18 ` Sergei Shtylyov
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=20130806170430.GL6427@sirena.org.uk \
--to=broonie@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;
as well as URLs for NNTP newsgroup(s).