All of lore.kernel.org
 help / color / mirror / Atom feed
From: "K, Kiran" <kiran.k@intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "open list:BLUETOOTH SUBSYSTEM" <linux-bluetooth@vger.kernel.org>,
	"Srivatsa, Ravishankar" <ravishankar.srivatsa@intel.com>,
	"Tumkur Narayan, Chethan" <chethan.tumkur.narayan@intel.com>,
	"An, Tedd" <tedd.an@intel.com>,
	"Von Dentz, Luiz" <luiz.von.dentz@intel.com>
Subject: RE: [PATCH v1] Bluetooth: btintel: Fix boot address
Date: Tue, 31 Aug 2021 12:57:13 +0000	[thread overview]
Message-ID: <DM8PR11MB5573FB6D0E9726DD82C43A7CF5CC9@DM8PR11MB5573.namprd11.prod.outlook.com> (raw)
In-Reply-To: <7E8C3893-19CD-44D6-B224-A3434F65BA95@holtmann.org>

HI Marcel,

> -----Original Message-----
> From: Marcel Holtmann <marcel@holtmann.org>
> Sent: Monday, August 30, 2021 8:38 PM
> To: K, Kiran <kiran.k@intel.com>
> Cc: open list:BLUETOOTH SUBSYSTEM <linux-bluetooth@vger.kernel.org>;
> Srivatsa, Ravishankar <ravishankar.srivatsa@intel.com>; Tumkur Narayan,
> Chethan <chethan.tumkur.narayan@intel.com>; An, Tedd
> <tedd.an@intel.com>; Von Dentz, Luiz <luiz.von.dentz@intel.com>
> Subject: Re: [PATCH v1] Bluetooth: btintel: Fix boot address
> 
> Hi Kiran,
> 
> > Cache Boot address present in firmware file which is later used
> > Intel_Soft_Reset command to bring controller from boot mode to
> > operational mode.
> >
> > Signed-off-by: Kiran K <kiran.k@intel.com>
> > ---
> > drivers/bluetooth/btintel.c | 31 +++++++++++++------------------
> > 1 file changed, 13 insertions(+), 18 deletions(-)
> >
> > diff --git a/drivers/bluetooth/btintel.c b/drivers/bluetooth/btintel.c
> > index f1705b46fc88..80d6dd7ae51a 100644
> > --- a/drivers/bluetooth/btintel.c
> > +++ b/drivers/bluetooth/btintel.c
> > @@ -1037,8 +1037,9 @@ static bool btintel_firmware_version(struct
> > hci_dev *hdev,
> >
> > 			params = (void *)(fw_ptr + sizeof(*cmd));
> >
> > -			bt_dev_info(hdev, "Boot Address: 0x%x",
> > -				    le32_to_cpu(params->boot_addr));
> > +			*boot_addr = le32_to_cpu(params->boot_addr);
> > +
> > +			bt_dev_info(hdev, "Boot Address: 0x%x",
> *boot_addr);
> >
> 
> so this hunk looks good and is described in the commit message.
> 
> > 			bt_dev_info(hdev, "Firmware Version: %u-%u.%u",
> > 				    params->fw_build_num, params-
> >fw_build_ww, @@ -1071,9 +1072,6
> > @@ int btintel_download_firmware(struct hci_dev *hdev,
> > 		/* Skip version checking */
> > 		break;
> > 	default:
> > -		/* Skip reading firmware file version in bootloader mode */
> > -		if (ver->fw_variant == 0x06)
> > -			break;
> >
> > 		/* Skip download if firmware has the same version */
> > 		if (btintel_firmware_version(hdev, ver->fw_build_num, @@
> -1114,19
> > +1112,16 @@ static int btintel_download_fw_tlv(struct hci_dev *hdev,
> > 	int err;
> > 	u32 css_header_ver;
> >
> > -	/* Skip reading firmware file version in bootloader mode */
> > -	if (ver->img_type != 0x01) {
> > -		/* Skip download if firmware has the same version */
> > -		if (btintel_firmware_version(hdev, ver->min_fw_build_nn,
> > -					     ver->min_fw_build_cw,
> > -					     ver->min_fw_build_yy,
> > -					     fw, boot_param)) {
> > -			bt_dev_info(hdev, "Firmware already loaded");
> > -			/* Return -EALREADY to indicate that firmware has
> > -			 * already been loaded.
> > -			 */
> > -			return -EALREADY;
> > -		}
> > +	/* Skip download if firmware has the same version */
> > +	if (btintel_firmware_version(hdev, ver->min_fw_build_nn,
> > +				     ver->min_fw_build_cw,
> > +				     ver->min_fw_build_yy,
> > +				     fw, boot_param)) {
> > +		bt_dev_info(hdev, "Firmware already loaded");
> > +		/* Return -EALREADY to indicate that firmware has
> > +		 * already been loaded.
> > +		 */
> > +		return -EALREADY;
> > 	}
> 
> This part however isn’t.

Ack. I have separated the patches with proper commit message and sent an updated version.
> 
> Regards
> 
> Marcel

Thanks,
Kiran


      reply	other threads:[~2021-08-31 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 11:58 [PATCH v1] Bluetooth: btintel: Fix boot address Kiran K
2021-08-20 13:22 ` [v1] " bluez.test.bot
2021-08-30 15:07 ` [PATCH v1] " Marcel Holtmann
2021-08-31 12:57   ` K, Kiran [this message]

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=DM8PR11MB5573FB6D0E9726DD82C43A7CF5CC9@DM8PR11MB5573.namprd11.prod.outlook.com \
    --to=kiran.k@intel.com \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.org \
    --cc=ravishankar.srivatsa@intel.com \
    --cc=tedd.an@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.