From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ASoC: dfbmcs320: make the driver common for other BT modules
Date: Fri, 17 May 2013 12:15:23 +0100 [thread overview]
Message-ID: <20130517111523.GM1627@sirena.org.uk> (raw)
In-Reply-To: <1368757177-15372-1-git-send-email-Baohua.Song@csr.com>
On Fri, May 17, 2013 at 10:19:37AM +0800, Barry Song wrote:
> DFBM-CS320 is only one of bluetooth modules using CSR bluetooth chips,
> we don't want everyone to have a seperate codec driver. anyway, the
> feature of Bluetooth handsfree is same on all platforms, so this patch
> makes the DFBM-CS320 driver become a common BT handsfree driver.
Sorry, should have thought of this before but why are we calling this
"handsfree"? It's just a generic bluetooth link as far as the host
system is concerned, "bt-sco" might be more appropriate?
Otherwise this looks OK for ASoC though I'd expect to see a change to
registration of the OpenMoko BT device (perhaps I missed it though).
-------------- 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/20130517/09653d70/attachment.sig>
next prev parent reply other threads:[~2013-05-17 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 2:19 [PATCH v2] ASoC: dfbmcs320: make the driver common for other BT modules Barry Song
2013-05-17 11:15 ` Mark Brown [this message]
2013-05-18 11:03 ` [alsa-devel] " Barry Song
2013-05-18 11:25 ` Mark Brown
2013-05-18 11:32 ` Lars-Peter Clausen
2013-05-18 11:34 ` Barry Song
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=20130517111523.GM1627@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