linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Bin.Shi@csr.com (Bin Shi)
To: linux-arm-kernel@lists.infradead.org
Subject: Linux Bluetooth HFP through usp pcm design questions
Date: Wed, 05 May 2010 09:46:54 +0800	[thread overview]
Message-ID: <1273024014.9369.1.camel@ben-desktop> (raw)

Hi all,

        
        

I am working on vendor ARM1136 platform. Nowdays, I want to integrate
CSR BC06 chip to my board with HFP profile, bluetooth chip connect its
pcm interface with platform's usp interface. 

        

As I know, HFP profile should has at least two deamons, one for host and
one for target(BC06). In low level, driver for usp pcm should be
available, which is compatible with BC06 frame format. Now, audio path
is OK for playback and capture with ALSA.

        

My questions are:
1) How could I control stream path: eg headphone voice->BC06->usp
interface->platform speaker?
2) Should it be strictly sync for controlling this application?
3) Data format between usp interface and headphone interface(bypass
bluetooth) should be pcm stream?

        
        

Any suggestion would be welcomed! Thanks.




---
Best Regards,
Bin Shi








Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100505/efcc9f18/attachment-0001.htm>

             reply	other threads:[~2010-05-05  1:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05  1:46 Bin Shi [this message]
2010-05-12 13:27 ` Linux Bluetooth HFP through usp pcm design questions Eric Miao
2010-05-13  1:58   ` Bin Shi

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=1273024014.9369.1.camel@ben-desktop \
    --to=bin.shi@csr.com \
    --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).