From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Adam Ford <aford173@gmail.com>
Cc: linux-input@vger.kernel.org,
Adam Ford-BE <aford@beaconembedded.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Input: ili210x: Enable suspend/resume functions
Date: Wed, 4 Nov 2020 08:22:57 -0800 [thread overview]
Message-ID: <20201104162257.GB1003057@dtor-ws> (raw)
In-Reply-To: <CAHCN7xLMGhuGq8WFn8B2W_dwAgDgjo1YczDnf0uJJw3kvJWhjw@mail.gmail.com>
Hi Adam,
On Wed, Nov 04, 2020 at 10:15:47AM -0600, Adam Ford wrote:
> On Fri, Sep 18, 2020 at 9:34 AM Adam Ford <aford173@gmail.com> wrote:
> >
> > Some people may wish to wake their system from sleep, so this
> > patch enables a suspend and resume function which enables
> > and disables IRQ wake functions.
> >
> > Signed-off-by: Adam Ford <aford173@gmail.com>
>
> Gentle ping. Any feedback on this?
Ah, sorry. This should not be needed as for I2C devices that are
configured as wakeup sources I2C core takes care of declaring interrupt
line as wake IRQ and should configure it accordingly during the system
state transitions.
See drivers/i2c/i2c-core-base.c - calls to
dev_pm_set_[dedicated_]wake_irq() in i2c_device_probe().
>
> >
> > diff --git a/drivers/input/touchscreen/ili210x.c b/drivers/input/touchscreen/ili210x.c
> > index 199cf3daec10..9b1a61447054 100644
> > --- a/drivers/input/touchscreen/ili210x.c
> > +++ b/drivers/input/touchscreen/ili210x.c
> > @@ -474,6 +474,28 @@ static int ili210x_i2c_probe(struct i2c_client *client,
> > return 0;
> > }
> >
> > +static int __maybe_unused ili210x_i2c_suspend(struct device *dev)
> > +{
> > + struct i2c_client *client = to_i2c_client(dev);
> > +
> > + if (device_may_wakeup(&client->dev))
> > + enable_irq_wake(client->irq);
> > +
> > + return 0;
> > +}
> > +
> > +static int __maybe_unused ili210x_i2c_resume(struct device *dev)
> > +{
> > + struct i2c_client *client = to_i2c_client(dev);
> > +
> > + if (device_may_wakeup(&client->dev))
> > + disable_irq_wake(client->irq);
> > +
> > + return 0;
> > +}
> > +
> > +static SIMPLE_DEV_PM_OPS(ili210x_i2c_pm, ili210x_i2c_suspend, ili210x_i2c_resume);
> > +
> > static const struct i2c_device_id ili210x_i2c_id[] = {
> > { "ili210x", (long)&ili210x_chip },
> > { "ili2117", (long)&ili211x_chip },
> > @@ -495,6 +517,7 @@ MODULE_DEVICE_TABLE(of, ili210x_dt_ids);
> > static struct i2c_driver ili210x_ts_driver = {
> > .driver = {
> > .name = "ili210x_i2c",
> > + .pm = &ili210x_i2c_pm,
> > .of_match_table = ili210x_dt_ids,
> > },
> > .id_table = ili210x_i2c_id,
> > --
> > 2.25.1
> >
Thanks.
--
Dmitry
prev parent reply other threads:[~2020-11-04 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 14:33 [PATCH] Input: ili210x: Enable suspend/resume functions Adam Ford
2020-11-04 16:15 ` Adam Ford
2020-11-04 16:22 ` Dmitry Torokhov [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=20201104162257.GB1003057@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.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