From: Hans de Goede <hdegoede@redhat.com>
To: Matthias Kaehlcke <mka@chromium.org>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Arnd Bergmann <arnd@arndb.de>, Jim Broadus <jbroadus@gmail.com>,
Johnny Chuang <johnny.chuang.emc@gmail.com>,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH] HID: i2c-hid: Report wakeup events
Date: Tue, 2 Nov 2021 19:58:55 +0100 [thread overview]
Message-ID: <e3643a2e-8ea0-586c-62e0-4d85fd2c9a8e@redhat.com> (raw)
In-Reply-To: <20211102114017.1.I16ef7b761c8467be2106880e9b24ce304ae2b532@changeid>
Hi,
On 11/2/21 19:40, Matthias Kaehlcke wrote:
> The i2c-hid driver generally supports wakeup, bit it currently
> doesn't report wakeup events to the PM subsystem. Change that.
>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
Thanks, this looks reasonable to me:
Acked-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
> ---
>
> drivers/hid/i2c-hid/i2c-hid-core.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/hid/i2c-hid/i2c-hid-core.c b/drivers/hid/i2c-hid/i2c-hid-core.c
> index 517141138b00..68d9a089e3e8 100644
> --- a/drivers/hid/i2c-hid/i2c-hid-core.c
> +++ b/drivers/hid/i2c-hid/i2c-hid-core.c
> @@ -522,9 +522,12 @@ static void i2c_hid_get_input(struct i2c_hid *ihid)
>
> i2c_hid_dbg(ihid, "input: %*ph\n", ret_size, ihid->inbuf);
>
> - if (test_bit(I2C_HID_STARTED, &ihid->flags))
> + if (test_bit(I2C_HID_STARTED, &ihid->flags)) {
> + pm_wakeup_event(&ihid->client->dev, 0);
> +
> hid_input_report(ihid->hid, HID_INPUT_REPORT, ihid->inbuf + 2,
> ret_size - 2, 1);
> + }
>
> return;
> }
>
next prev parent reply other threads:[~2021-11-02 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 18:40 [PATCH] HID: i2c-hid: Report wakeup events Matthias Kaehlcke
2021-11-02 18:58 ` Hans de Goede [this message]
2021-11-19 14:50 ` Jiri Kosina
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=e3643a2e-8ea0-586c-62e0-4d85fd2c9a8e@redhat.com \
--to=hdegoede@redhat.com \
--cc=arnd@arndb.de \
--cc=benjamin.tissoires@redhat.com \
--cc=dianders@chromium.org \
--cc=jbroadus@gmail.com \
--cc=jikos@kernel.org \
--cc=johnny.chuang.emc@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=nathan@kernel.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).