Hi Tedd, > This patch adds the routine to apply the DDC parameter from device > specific ddc file. > > Once the device is rest to operational mode, optionally, it can > download the device specific configration (DDC) parameters before > the BlueZ starts the stack initialization. > > It opens the DDC file based on HW_VARIANT and DEV_REVISION and > send ID/Value with HCI_Intel_Write_DDC command. > > Format of DDC file > DDC file contains one or more number of DDC structure. > > DDC Structure > It has 'Length' field of one octet, DDC 'ID' field of > two octets followed by the array of DDC 'Value' that gives > the value of parameters itself. > 'Length' contains the length of DDC 'ID' and DDC 'Value'. > > +------------+----------+ > | Size(byte) | Name | > +------------+----------+ > | 1 | Length | > +------------+----------+ > | 2 | ID | > +------------+----------+ > | Length - 2 | Value | > +------------+----------+ > > Signed-off-by: Tedd Ho-Jeong An <tedd.an@xxxxxxxxx> > --- > drivers/bluetooth/btusb.c | 42 ++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 42 insertions(+) patch has been applied to bluetooth-next tree. However I did a few minor wording changes in the comments and BT_INFO sections. 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
