Hi Vitaly, > -----Original Message----- > From: Vitaly Wool [mailto:vitalywool@xxxxxxxxx] > Sent: den 19 december 2010 23:58 > To: Linus Walleij > Cc: Par-Gunnar HJALMDAHL; Pavan Savoy; Alan Cox; Arnd Bergmann; Samuel > Ortiz; Marcel Holtmann; linux-kernel@xxxxxxxxxxxxxxx; linux- > bluetooth@xxxxxxxxxxxxxxx; Lukasz Rymanowski; Par-Gunnar Hjalmdahl > Subject: Re: [PATCH 00/11] mfd and bluetooth: Add CG2900 support > > Hi Linus, > > On Sun, Dec 19, 2010 at 10:23 PM, Linus Walleij > <linus.walleij@xxxxxxxxxx> wrote: > > I'm slightly confused by different comment threads on this patch set. > > let me first first repost the part from Arnd's email on the > architecture of the "shared transport" type of thing: > > > I believe we already agree it should be something like > > > > bt ti-radio st-e-radio ti-gps st-e-gps broadcom-radio > ... > > | | | | | | | > > +---------+----------+---------+--+----------+----------+---------+ > > | > > common-hci-module > > | > > +-----------+-----------+ > > | | | | > > serial spi i2c ... > > I think an explanation on how the patchset from Par maps to this > architecture could be a good starting point for confusion minimization > :) > > Thanks, > Vitaly I would say our design would map like this: common-hci-module: cg2900_core serial, spi, i2c,... : cg2900_uart together with hci_ldisc (for other transports it would be different files) bt, ti-radio, st-e-radio,...: cg2900_chip together with btcg2900 and other users per channel (cg2900_char_devices for users in User space) So it is not a 1-to-1 mapping for the upper parts. I would draw it like this: bt st-e-radio st-e-gps | | | +---------+----------+ | ti-xx st-e cg2900... | | +---------+----------+ | common-hci-module | +-----------+-----------+ | | | | serial spi i2c ... The reason for this difference I've gone through before. Basically there are so many special behaviors and needed handling that is individual for each chip (like startup and shutdown and in the case of CG2900 flow control over FM and BT channels for audio commands). If you then look at the users I guess it would be possible to have one BT user, but it would have to be modified to handle vendor specific commands (as btcg2900 does with BT_ENABLE command). As Arnd has drawn for FM and GPS the users would be completely individual since they don't have a standardized interface. /P-G -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
