linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "K, Kiran" <kiran.k@intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: RE: [PATCH v9 10/10] Bluetooth: Add support for msbc coding format
Date: Wed, 23 Jun 2021 03:24:01 +0000	[thread overview]
Message-ID: <DM8PR11MB5573E6535A15DBE24306AE1FF5089@DM8PR11MB5573.namprd11.prod.outlook.com> (raw)
In-Reply-To: <AA50351C-7DF2-4732-8493-A57616918B11@holtmann.org>

Hi Marcel,

> -----Original Message-----
> From: Marcel Holtmann <marcel@holtmann.org>
> Sent: Wednesday, June 16, 2021 1:14 AM
> To: K, Kiran <kiran.k@intel.com>
> Cc: linux-bluetooth@vger.kernel.org
> Subject: Re: [PATCH v9 10/10] Bluetooth: Add support for msbc coding
> format
> 
> Hi Kiran,
> 
> > In Enhanced_Setup_Synchronous_Command, add support for msbc coding
> > format
> >
> > Signed-off-by: Kiran K <kiran.k@intel.com>
> > Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
> > Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
> > ---
> > include/net/bluetooth/bluetooth.h |  1 +
> > net/bluetooth/hci_conn.c          | 27 ++++++++++++++++++++++++++-
> > 2 files changed, 27 insertions(+), 1 deletion(-)
> >
> > diff --git a/include/net/bluetooth/bluetooth.h
> > b/include/net/bluetooth/bluetooth.h
> > index af2809121571..056699224da7 100644
> > --- a/include/net/bluetooth/bluetooth.h
> > +++ b/include/net/bluetooth/bluetooth.h
> > @@ -175,6 +175,7 @@ struct bt_codecs {
> >
> > #define CODING_FORMAT_CVSD		0x02
> > #define CODING_FORMAT_TRANSPARENT	0x03
> > +#define CODING_FORMAT_MSBC		0x05
> >
> > __printf(1, 2)
> > void bt_info(const char *fmt, ...);
> > diff --git a/net/bluetooth/hci_conn.c b/net/bluetooth/hci_conn.c index
> > 9569b21adb88..73c134459361 100644
> > --- a/net/bluetooth/hci_conn.c
> > +++ b/net/bluetooth/hci_conn.c
> > @@ -328,6 +328,32 @@ bool hci_enhanced_setup_sync(struct hci_conn
> *conn, __u16 handle)
> > 	cp.rx_bandwidth   = cpu_to_le32(0x00001f40);
> >
> > 	switch (conn->codec.id) {
> > +	case CODING_FORMAT_MSBC:
> > +		if (!find_next_esco_param(conn, esco_param_msbc,
> > +					  ARRAY_SIZE(esco_param_msbc)))
> > +			return false;
> > +
> > +		param = &esco_param_msbc[conn->attempt - 1];
> > +		cp.tx_coding_format.id = 0x05;
> > +		cp.rx_coding_format.id = 0x05;
> > +		cp.tx_codec_frame_size = __cpu_to_le16(60);
> > +		cp.rx_codec_frame_size = __cpu_to_le16(60);
> > +		cp.in_bandwidth = __cpu_to_le32(32000);
> > +		cp.out_bandwidth = __cpu_to_le32(32000);
> > +		cp.in_coding_format.id = 0x04;
> > +		cp.out_coding_format.id = 0x04;
> > +		cp.in_coded_data_size = __cpu_to_le16(16);
> > +		cp.out_coded_data_size = __cpu_to_le16(16);
> > +		cp.in_pcm_data_format = 2;
> > +		cp.out_pcm_data_format = 2;
> > +		cp.in_pcm_sample_payload_msb_pos = 0;
> > +		cp.out_pcm_sample_payload_msb_pos = 0;
> > +		cp.in_data_path = conn->codec.data_path;
> > +		cp.out_data_path = conn->codec.data_path;
> > +		cp.in_trasnport_unit_size = 1;
> > +		cp.out_trasnport_unit_size = 1;
> 
> so s/trasnport/transport/
> 
> Please spellcheck your structs.

Ack.

> 
> > +		break;
> > +
> > 	case CODING_FORMAT_TRANSPARENT:
> > 		if (!find_next_esco_param(conn, esco_param_msbc,
> > 					  ARRAY_SIZE(esco_param_msbc)))
> > @@ -383,7 +409,6 @@ bool hci_enhanced_setup_sync(struct hci_conn
> *conn, __u16 handle)
> > 		cp.in_trasnport_unit_size = 16;
> > 		cp.out_trasnport_unit_size = 16;
> > 		break;
> > -
> 
> We can not have these random hunks in patches. You need to review your
> final set before sending it out.

Ack.

> 
> Regards
> 
> Marcel

Thanks,
Kiran



  reply	other threads:[~2021-06-23  3:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 12:24 [PATCH v9 01/10] Bluetooth: enumerate local supported codec and cache details Kiran K
2021-06-08 12:24 ` [PATCH v9 02/10] Bluetooth: Add support for Read Local Supported Codecs V2 Kiran K
2021-06-08 12:24 ` [PATCH v9 03/10] Bluetooth: Add a callback function to retireve data path Kiran K
2021-06-15 19:26   ` Marcel Holtmann
2021-06-16  2:56     ` K, Kiran
2021-06-16  5:17       ` Marcel Holtmann
2021-06-08 12:24 ` [PATCH v9 04/10] Bluetooth: btintel: set get_data_path callback Kiran K
2021-06-15 19:30   ` Marcel Holtmann
2021-06-16  3:02     ` K, Kiran
2021-06-08 12:24 ` [PATCH v9 05/10] Bluetooth: Add BT_CODEC option for getsockopt for SCO socket Kiran K
2021-06-15 19:37   ` Marcel Holtmann
2021-06-08 12:24 ` [PATCH v9 06/10] Bluetooth: Add a callback function to set data path Kiran K
2021-06-15 19:37   ` Marcel Holtmann
2021-06-08 12:24 ` [PATCH v9 07/10] Bluetooth: btintel: define callback " Kiran K
2021-06-15 19:39   ` Marcel Holtmann
2021-06-16  3:10     ` K, Kiran
2021-06-16  5:18       ` Marcel Holtmann
2021-06-17  7:53         ` K, Kiran
2021-06-17 10:19           ` Marcel Holtmann
2021-06-23  3:21             ` K, Kiran
2021-06-08 12:24 ` [PATCH v9 08/10] Bluetooth: Add BT_CODEC option for setsockopt over SCO Kiran K
2021-06-08 12:24 ` [PATCH v9 09/10] Bluetooth: Add support for HCI_Enhanced_Setup_Synchronous_Connection command Kiran K
2021-06-08 12:24 ` [PATCH v9 10/10] Bluetooth: Add support for msbc coding format Kiran K
2021-06-15 19:43   ` Marcel Holtmann
2021-06-23  3:24     ` K, Kiran [this message]
2021-06-08 13:39 ` [v9,01/10] Bluetooth: enumerate local supported codec and cache details bluez.test.bot
2021-06-08 18:49 ` [PATCH v9 01/10] " kernel test robot
2021-06-15 19:25 ` Marcel Holtmann
2021-06-16  2:51   ` K, Kiran
2021-06-16  5:15     ` Marcel Holtmann

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=DM8PR11MB5573E6535A15DBE24306AE1FF5089@DM8PR11MB5573.namprd11.prod.outlook.com \
    --to=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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).