Linux bluetooth development
 help / color / mirror / Atom feed
From: Kumar Gala <galak@codeaurora.org>
To: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>
Cc: linux-arm-msm@vger.kernel.org,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC 0/2] Add hci_smd driver
Date: Tue, 11 Feb 2014 14:00:13 -0600	[thread overview]
Message-ID: <2AA076F5-9C40-4449-84FB-FC68809197DF@codeaurora.org> (raw)
In-Reply-To: <CAMudyAsomuEjkpnj_2Dmqikx_t+nYsEcv_Ai0e6xzuFjG7vGbw@mail.gmail.com>


On Feb 11, 2014, at 10:23 AM, Lukasz Rymanowski <lukasz.rymanowski@tieto.com> wrote:

> Hi
> 
> On 7 February 2014 12:35, Lukasz Rymanowski <lukasz.rymanowski@tieto.com> wrote:
>> Hello,
>> 
>> This is a try (long shoot) to upstream hci shared memory driver (hci_smd)
>> which is used on Qualcomm platforms and BT chips.
>> 
>> To make it build with upstream tree I had to introduce some simple SMD API.
>> The idea here is that since SMD channel is represented by platform device
>> (as it is done in mach-msm),
>> then platfrom_data contains smd_data which contains API for that channel.
>> 
>> Writing this SMD API I was inspired with MSM-SMD and since I'm not an expert
>> in this area I'm asking for comments here.
>> 
>> Maybe instead of SMD API I made, I should expose functions like smd_open(), smd_write()
>> etc. something similar how sdio does, and  just deliver to upstream dummy device
>> implementing this SMD API?
>> 
>> Other options I was considering is to implement  module inside mach-msm which
>> would handle registering SMD BT Channels and when it is done, it would register
>> new platform device like "smd-bt". Then I could move smd.h to some bluetooth includes
>> (althought don't now where at the moment) and hci_smd would register driver for "smd-bt"
>> In this case I would also could rid of one static variable I have now in hci_smd
>> 
>> Comments on those options are welcome.
>> 
>> Anyway, Hci_smd is based on one of the older version of this driver found in msm kernel
>> branch, so there are no wakelocks as in new version and also workqueues are used
>> instead of takslet.
>> 
>> Since SMD expose two channels, one for CMD/EVENT and one for ACL Data I decide to
>> do separate worqueues for this. This is to make sure that ACL data never blocks EVENT
>> packages
>> 
> 
> Adding linux-arm-msm group for comments on SMD API.
> 
> BR
> Lukasz

What chip/SoC/board are you trying to get bluetooth support on?

- k

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation


  reply	other threads:[~2014-02-11 20:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07 11:35 [RFC 0/2] Add hci_smd driver Lukasz Rymanowski
2014-02-07 11:35 ` [RFC 1/2] Add basic API for shared memory driver Lukasz Rymanowski
2014-02-11 16:23   ` Lukasz Rymanowski
2014-02-07 11:35 ` [RFC 2/2] bluetooth: Add initial support for BT chip over SMD Lukasz Rymanowski
2014-02-11 16:24   ` Lukasz Rymanowski
2014-02-11 16:23 ` [RFC 0/2] Add hci_smd driver Lukasz Rymanowski
2014-02-11 20:00   ` Kumar Gala [this message]
2014-02-12  9:11     ` Lukasz Rymanowski

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=2AA076F5-9C40-4449-84FB-FC68809197DF@codeaurora.org \
    --to=galak@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lukasz.rymanowski@tieto.com \
    /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