From: Marcel Holtmann <marcel@holtmann.org>
To: Raghuram Hegde <raghuram.hegde@intel.com>
Cc: Bluez mailing list <linux-bluetooth@vger.kernel.org>,
Chethan T N <chethan.tumkur.narayan@intel.com>
Subject: Re: [PATCH] btusb: Add shutdown routine for BTUSB_INTEL_NEW devices
Date: Mon, 28 Jan 2019 13:05:01 +0100 [thread overview]
Message-ID: <91F174CE-3CBE-4D3B-B0C9-E350C01F3DDF@holtmann.org> (raw)
In-Reply-To: <1548665625-23742-1-git-send-email-raghuram.hegde@intel.com>
Hi Raghuram,
> btusb_shutdown_intel routine shall reset the controller
> and stop all BT operation.
> Advantages:
> 1. Power save on the platform
> 2. Host and controller will be in Sync.
>
> Signed-off-by: Raghuram Hegde <raghuram.hegde@intel.com>
> Signed-off-by: Chethan T N <chethan.tumkur.narayan@intel.com>
> ---
> drivers/bluetooth/btusb.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index 5de0c2e59b97..66483ca3d870 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -3139,6 +3139,7 @@ static int btusb_probe(struct usb_interface *intf,
> hdev->manufacturer = 2;
> hdev->send = btusb_send_frame_intel;
> hdev->setup = btusb_setup_intel_new;
> + hdev->shutdown = btusb_shutdown_intel;
> hdev->hw_error = btintel_hw_error;
> hdev->set_diag = btintel_set_diag;
> hdev->set_bdaddr = btintel_set_bdaddr;
I assumed that this was only needed for the older ROM versions of the Intel controllers and not the newer RAM versions. I have been told they don’t inherit the LED issue that we tried to fix with this. Please read the comments in btusb_shutdown_intel and amend comments if needed and provide a detailed commit message.
Regards
Marcel
next prev parent reply other threads:[~2019-01-28 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 8:53 [PATCH] btusb: Add shutdown routine for BTUSB_INTEL_NEW devices raghuram.hegde
2019-01-28 12:05 ` Marcel Holtmann [this message]
2019-01-28 15:36 ` chethan tn
2019-01-28 16:00 ` Marcel Holtmann
2019-01-28 16:03 ` chethan tn
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=91F174CE-3CBE-4D3B-B0C9-E350C01F3DDF@holtmann.org \
--to=marcel@holtmann.org \
--cc=chethan.tumkur.narayan@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=raghuram.hegde@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 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).