From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Alain Michaud <alainm@chromium.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
chromeos-bluetooth-upstreaming@chromium.org
Subject: Re: [BlueZ PATCH 2/2] input: Make HID devices wake capable
Date: Tue, 21 Jan 2020 14:15:44 -0800 [thread overview]
Message-ID: <CABBYNZLV_x5zv_McY1bA1253B2j=Yn8KHHiH59xg=eBy07P70w@mail.gmail.com> (raw)
In-Reply-To: <CABBYNZJBf_FxO-=nVRqtC9MPEsD8dyXoGhFQPRYg0SB4wQG51Q@mail.gmail.com>
Hi Abhishek,
On Fri, Jan 17, 2020 at 2:16 PM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> Hi Abhishek,
>
> On Fri, Jan 17, 2020 at 1:28 PM Abhishek Pandit-Subedi
> <abhishekpandit@chromium.org> wrote:
> >
> > HID devices can wake the host from a suspended state. Mark them as wake
> > capable when they are accepted.
>
> My suggestion is that we do this via application so we let the user
> decide if he wants or not to wake up the system, you may still opt-in
> to always enable to wake up in your system setting if you choose to,
> going this route actually means the user can select not to wake up if
> the device is somewhat broken or misbehaving in some respect which is
> not that uncommon nowadays.
Will there be any follow up on this or you didn't quite understand
what Im suggesting here?
> > ---
> >
> > profiles/input/device.c | 1 +
> > profiles/input/hog.c | 1 +
> > 2 files changed, 2 insertions(+)
> >
> > diff --git a/profiles/input/device.c b/profiles/input/device.c
> > index 2cb3811c8..a6b0e8053 100644
> > --- a/profiles/input/device.c
> > +++ b/profiles/input/device.c
> > @@ -1381,6 +1381,7 @@ int input_device_register(struct btd_service *service)
> > }
> >
> > btd_service_set_user_data(service, idev);
> > + device_set_wake_capable(device, true);
> >
> > return 0;
> > }
> > diff --git a/profiles/input/hog.c b/profiles/input/hog.c
> > index 83c017dcb..8627f3557 100644
> > --- a/profiles/input/hog.c
> > +++ b/profiles/input/hog.c
> > @@ -159,6 +159,7 @@ static int hog_probe(struct btd_service *service)
> > return -EINVAL;
> >
> > btd_service_set_user_data(service, dev);
> > + device_set_wake_capable(device, true);
> > return 0;
> > }
> >
> > --
> > 2.25.0.341.g760bfbb309-goog
> >
>
>
> --
> Luiz Augusto von Dentz
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2020-01-21 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 21:28 [BlueZ PATCH 1/2] adapter: Add set wake capable operation Abhishek Pandit-Subedi
2020-01-17 21:28 ` [BlueZ PATCH 2/2] input: Make HID devices wake capable Abhishek Pandit-Subedi
2020-01-17 22:16 ` Luiz Augusto von Dentz
2020-01-21 22:15 ` Luiz Augusto von Dentz [this message]
2020-01-21 22:23 ` Abhishek Pandit-Subedi
2020-01-17 22:06 ` [BlueZ PATCH 1/2] adapter: Add set wake capable operation Luiz Augusto von Dentz
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='CABBYNZLV_x5zv_McY1bA1253B2j=Yn8KHHiH59xg=eBy07P70w@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=abhishekpandit@chromium.org \
--cc=alainm@chromium.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--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).