Hi Par-Gunnar, > > * Par-Gunnar Hjalmdahl <par-gunnar.p.hjalmdahl@xxxxxxxxxxxxxx> [2010-09-24 15:52:16 +0200]: > > > >> This patch adds support for using the ST-Ericsson CG2900 > >> connectivity controller as a driver for the BlueZ Bluetooth > >> stack. > >> This patch registers as a driver into the BlueZ framework and, when > >> opened by BlueZ, it registers as user for bt_cmd, bt_acl, and bt_evt > >> channels. > > > > First of all your your commit message and subject should be improved. > > The subject should bee something like: > > > > "Bluetooth: Add support for ST-Ericsson CG2900" > > > > and in the commit message you explain the details of the patch. > > And normally we do not use the BlueZ word in kernelspace. > > > > OK. This is the first patch I've created within the community and of > course there are bound to be errors... ;-) > Since it was part of a big patch delivery I used quite similar names > across the different patches and I understand that this is an error > since the different patches are targeting different communities. > > >> > >> Signed-off-by: Par-Gunnar Hjalmdahl <par-gunnar.p.hjalmdahl@xxxxxxxxxxxxxx> > >> --- > >> drivers/bluetooth/Kconfig | 7 + > >> drivers/bluetooth/Makefile | 2 + > >> drivers/bluetooth/cg2900_hci.c | 896 ++++++++++++++++++++++++++++++++++++++++ > >> 3 files changed, 905 insertions(+), 0 deletions(-) > >> create mode 100644 drivers/bluetooth/cg2900_hci.c > > > > Your patch looks a way complicated to a UART driver. Look at the others > > drivers at drivers/bluetooth/ and see how we implemented other UART > > drivers. > > > > Well, mainly that's because it is not a UART driver. It is a driver > against CG2900 which currently have only UART as transport but quite > soon will get SPI as transport as well. For this Bluetooth driver the > actual physical transport used is not known. It just knows it has a > reliable transport below which delivers complete Bluetooth packets. inside the Bluetooth driver please just use BT_DBG. That is hooked up into dynamic_debug feature of the kernel and you can do whatever you need for debugging. I will not accept huge debug frameworks in the Bluetooth subsystem. Use what the kernel offers you. You selective control based on every single debug statement. It doesn't get better than that. Regards Marcel -- 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
