Linux bluetooth development
 help / color / mirror / Atom feed
From: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv3 1/3] Bluetooth: Allow to set AMP type for virtual HCI
Date: Wed, 16 Nov 2011 10:22:15 +0200	[thread overview]
Message-ID: <20111116082209.GC30662@aemeltch-MOBL1> (raw)
In-Reply-To: <1321405993.15441.500.camel@aeonflux>

Hi Marcel,

On Wed, Nov 16, 2011 at 10:13:10AM +0900, Marcel Holtmann wrote:
> Hi Andrei,
> 
> > > Type can be changed during re-opening device /dev/vhci.
> > > 
> > > Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> > > Acked-by: Marcel Holtmann <marcel@holtmann.org>
> > > ---
> > >  drivers/bluetooth/hci_vhci.c |    8 ++++++++
> > >  1 files changed, 8 insertions(+), 0 deletions(-)
> > > 
> > > diff --git a/drivers/bluetooth/hci_vhci.c b/drivers/bluetooth/hci_vhci.c
> > > index 2e302a1..2ed6ab1 100644
> > > --- a/drivers/bluetooth/hci_vhci.c
> > > +++ b/drivers/bluetooth/hci_vhci.c
> > > @@ -41,6 +41,8 @@
> > >  
> > >  #define VERSION "1.3"
> > >  
> > > +static bool amp;
> > > +
> > >  struct vhci_data {
> > >  	struct hci_dev *hdev;
> > >  
> > > @@ -239,6 +241,9 @@ static int vhci_open(struct inode *inode, struct file *file)
> > >  	hdev->bus = HCI_VIRTUAL;
> > >  	hdev->driver_data = data;
> > >  
> > > +	if (amp)
> > > +		hdev->dev_type = HCI_AMP;
> > > +
> > 
> > I am thinking about changing lines above to:
> > 
> > -       if (amp)
> > +       if (amp) {
> >                 hdev->dev_type = HCI_AMP;
> > +               hdev->amp_type = AMP_CTRL_BLUETOOTH_ONLY;
> > +       }
> > 
> > to indicate that that "the AMP Controller is only used by the Bluetooth
> > technology and will not be shared with other non-Bluetooth technologies".
> 
> this can not be static information at this point. It will change
> depending on how the WiFi subsystem or WiFi drivers want it to be.
> 
> And lets cross the bridge when we get to it. This is too early to figure
> out what to do here.

The code only emulates virtual HCI amp_type. The reason why I added it is
to reply for A2MP Discover Req. If we leave field as 0 it would mean that
that controller is powered down.

This value can be read with "read local amp info", I can implement this
command in hciemu as other option.

Best regards 
Andrei Emeltchenko 

  reply	other threads:[~2011-11-16  8:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 10:42 [PATCHv3 0/3] Trivial fixes for emulating AMP HCI Emeltchenko Andrei
2011-11-14 10:42 ` [PATCHv3 1/3] Bluetooth: Allow to set AMP type for virtual HCI Emeltchenko Andrei
2011-11-15 12:09   ` Emeltchenko Andrei
2011-11-15 14:22     ` Emeltchenko Andrei
2011-11-16  1:13     ` Marcel Holtmann
2011-11-16  8:22       ` Emeltchenko Andrei [this message]
2011-11-16  9:17         ` Marcel Holtmann
2011-11-14 10:42 ` [PATCHv3 2/3] Bluetooth: Move scope of kernel parameter enable_hs Emeltchenko Andrei
2011-11-14 10:42 ` [PATCHv3 3/3] Bluetooth: Do not set HCI_RAW when HS enabled Emeltchenko Andrei
2011-11-16 18:56   ` Gustavo Padovan

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=20111116082209.GC30662@aemeltch-MOBL1 \
    --to=andrei.emeltchenko.news@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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