linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH] ASoC: dfbmcs320: make the driver common for other BT modules
Date: Thu, 16 May 2013 13:29:00 +0200	[thread overview]
Message-ID: <5194C2FC.70804@metafoo.de> (raw)
In-Reply-To: <CAGsJ_4yoXj+e7A20SM5+ctLvE2QRTp0bzDeKfCZSUHTO8BPq5A@mail.gmail.com>

On 05/16/2013 12:31 PM, Barry Song wrote:
> 2013/5/16 Lars-Peter Clausen <lars@metafoo.de>:
>> On 05/16/2013 08:53 AM, 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.
>> [...]
>>> -static struct platform_driver dfmcs320_driver = {
>>> +static struct platform_driver bt_handsfree_driver = {
>>>       .driver = {
>>> -             .name = "dfbmcs320",
>>> +             .name = "bt-handsfree",
>>>               .owner = THIS_MODULE,
>>
>> In my opinion it's a good idea to keep a platform_id list of all the
>> supported devices.
> 
> i have no idea how many bluetooth handsfree module exist in the world.
> there must be many. actually the driver works for almost all BT
> handsfree.
> so my basic idea is making the codes as common as possible.

you don't have to know all the device names, but I'd prefer to keep at least
dfbmcs320 in the device id list.

- Lars

  reply	other threads:[~2013-05-16 11:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16  6:53 [PATCH] ASoC: dfbmcs320: make the driver common for other BT modules Barry Song
2013-05-16  9:51 ` Lars-Peter Clausen
2013-05-16 10:31   ` [alsa-devel] " Barry Song
2013-05-16 11:29     ` Lars-Peter Clausen [this message]
2013-05-16 12:00       ` Barry Song
2013-05-16 17:35         ` 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=5194C2FC.70804@metafoo.de \
    --to=lars@metafoo.de \
    --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).