linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Savoy, Pavan" <pavan_savoy@ti.com>,
	Jiri Slaby <jirislaby@gmail.com>,
	"gregkh@suse.de" <gregkh@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] drivers:staging:ti-st: move TI_ST from staging
Date: Fri, 08 Oct 2010 10:32:26 +0200	[thread overview]
Message-ID: <1286526746.6145.178.camel@aeonflux> (raw)
In-Reply-To: <20101007213503.657bcab0@lxorguk.ukuu.org.uk>

Hi Alan,

> > ldisc is the ONLY way to do it, isn't it? Do I have any other option?
> 
> Userspace but even then it wouldn't solve your problem
> 
> > The situation was something similar here.
> > What I was trying to get to is how we can have a per-device context if a driver is just a line discipline driver?
> 
> tty->driver_data
> 		TTY private data
> tty->disc_data
> 		LDISC per instance private data
> 
> So when your ldisc is opened attach your data to the tty->disc_data, and
> when it is closed free the data.
> 
> > I have 3 sub-devices if you will on a device which is interfaced over UART,
> > One of them is Bluetooth which requires any UART Bluetooth device to have its
> > Own line discipline - N_HCI.
> 
> The problem is that your chip by the sound of it does not talk the
> bluetooth ldisc - it talks something more complex.
> 
> The obvious question then is
> 
> Does it talk
> 
> 1.	HCI with bits nailed on
> 2.	Something rather different which contains muxed data some of
> which is reformatted up to create HCI
> 
> In the first case it may be worth seeing if the existing N_HCI could
> support forwarding unknown frame types to a helper. In the latter it's a
> lot trickier. It is possible to create a mux tty layer (see n_gsm.c) but
> that is almost certainly overkill for this.
> 
> I wonder what Marcel thinks in terms of re-using the bluetooth ldisc ?

If you get a sane proposal, then yes, N_HCI could act as multiplexer and
forward certain frame types.

This all depends on how clear the separation is. If you expect to send
HCI commands from these "clients" then there is a problem with the
Bluetooth subsystem and its enforced flow control. You don't wanna mess
with that since it has side effects. And I am not giving outside drivers
real control over. The Bluetooth drivers have to stay dumb transport
drivers without any Bluetooth core logic.

So can you give me a few quick hints on what you would need to forward
actually.

Regards

Marcel



      parent reply	other threads:[~2010-10-08  8:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1286381895-11329-1-git-send-email-pavan_savoy@ti.com>
     [not found] ` <1286381895-11329-2-git-send-email-pavan_savoy@ti.com>
     [not found]   ` <4CACD234.7020900@gmail.com>
     [not found]     ` <19F8576C6E063C45BE387C64729E739404AA21CEA1@dbde02.ent.ti.com>
     [not found]       ` <4CACF5A7.3010601@gmail.com>
     [not found]         ` <19F8576C6E063C45BE387C64729E739404AA21CEC6@dbde02.ent.ti.com>
     [not found]           ` <4CAD7DAB.8030209@gmail.com>
     [not found]             ` <19F8576C6E063C45BE387C64729E739404AA21D193@dbde02.ent.ti.com>
     [not found]               ` <4CAE10C0.9000106@gmail.com>
     [not found]                 ` <19F8576C6E063C45BE387C64729E739404AA21D220@dbde02.ent.ti.com>
     [not found]                   ` <20101007203801.1c55a1d3@lxorguk.ukuu.org.uk>
     [not found]                     ` <19F8576C6E063C45BE387C64729E739404AA21D23B@dbde02.ent.ti.com>
2010-10-07 20:35                       ` [PATCH 1/2] drivers:staging:ti-st: move TI_ST from staging Alan Cox
2010-10-07 20:17                         ` Savoy, Pavan
2010-10-07 20:59                           ` Alan Cox
2010-10-07 20:46                             ` Savoy, Pavan
2010-10-08  8:32                         ` Marcel Holtmann [this message]

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=1286526746.6145.178.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=jirislaby@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavan_savoy@ti.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;
as well as URLs for NNTP newsgroup(s).