From: Bastien Nocera <hadess@hadess.net>
To: Marcel Holtmann <marcel@holtmann.org>, abhijeet.kumar@intel.com
Cc: "Gustavo F. Padovan" <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluettoth: btusb: Prevent USB devices to autosuspend while setting interface
Date: Wed, 15 Nov 2017 15:01:17 +0100 [thread overview]
Message-ID: <1510754477.2510.23.camel@hadess.net> (raw)
In-Reply-To: <395C47EC-9D79-451D-B774-9F6D6555F100@holtmann.org>
On Wed, 2017-11-15 at 14:54 +0100, Marcel Holtmann wrote:
> Hi Abhijeet,
>
> > Runtime resume USB device in order to ensure that PM framework
> > knows
> > that the we might be using the device in a short time and doesn't
> > autosuspend the device while we update it's interface.
> >
> > Signed-off-by: Abhijeet Kumar <abhijeet.kumar@intel.com>
> > ---
> > drivers/bluetooth/btusb.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> > index 7a5c06aaa181..588aabf991be 100644
> > --- a/drivers/bluetooth/btusb.c
> > +++ b/drivers/bluetooth/btusb.c
> > @@ -1444,6 +1444,12 @@ static void btusb_work(struct work_struct
> > *work)
> > data->sco_skb = NULL;
> > spin_unlock_irqrestore(&data->rxlock, flags);
> >
> > + /*
> > + *Letting runtime PM know that we wish to
> > use
> > + *the device in a short time.
> > + */
> > + pm_runtime_get(&data->udev->dev);
> > +
>
> the indentation is wrong here and the comment coding style if off.
> Please fix.
And there's a typo in the commit message ("its interface").
next prev parent reply other threads:[~2017-11-15 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 12:11 [PATCH] Bluettoth: btusb: Prevent USB devices to autosuspend while setting interface abhijeet.kumar
2017-11-15 13:54 ` Marcel Holtmann
2017-11-15 14:01 ` Bastien Nocera [this message]
2017-11-15 14:23 ` Johan Hovold
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=1510754477.2510.23.camel@hadess.net \
--to=hadess@hadess.net \
--cc=abhijeet.kumar@intel.com \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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).