RE: [PATCH 4/6] drivers:misc: sources for Init manager module

[Pavan Savoy]

--- On Thu, 25/3/10, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote:

> From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
> Subject: RE: [PATCH 4/6] drivers:misc: sources for Init manager module
> To: "Savoy, Pavan" <pavan_savoy@xxxxxx>
> Cc: "Pavan Savoy" <pavan_savoy@xxxxxxxxxxx>, "Greg KH" <gregkh@xxxxxxx>, "alan@xxxxxxxxxxxxxxxxxxx" <alan@xxxxxxxxxxxxxxxxxxx>, "Deosthali, Amey" <adeosthali@xxxxxx>, "Alathur, Pramodh" <pramodh_ag@xxxxxx>
> Date: Thursday, 25 March, 2010, 3:05 AM
> Hi Pavan,
> 
> > Find enclosed the design document, where in figure-1
> pretty much explains the different protocols for FM, GPS, BT
> and HCI-LL.
> 
> just after quickly going through that document, I think you
> should
> create an actual ST bus. The ST line discipline should be
> just one
> transport driver for that bus. Since you clearly looking
> into SPI and
> other transports as well.

Had planned a range of TTY drivers for SPI/SlimBus 'ala usb-serial device driver for that.
And hence somehow assumed TTY line discipline should be enough.

SPI/SlimBus I tend to agree, their device nodes in user space is not used, and settings like bus freq, CPOL/CPHA are all set via drivers (for spi atleast).

Even after doing that, what about the requirement of opening an tty device upon request from BT or FM when chip is on UART ?

> 
> And then the bus can export Bluetooth, FM and GPS devices.
> And we can
> have separate drivers for these devices.

Hnm, Any such example drivers to look around ?

> You might wanna pick a different name than ST to not make
> ST
> Microelectronics unhappy and next time they call their next
> thing TI ;)

I had called it SHUART for some reason earlier, Yep point to be considered.
Thanks,

> Regards
> 
> Marcel
> 
> 
> 


      Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads.yahoo.com/in/internetexplorer/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/