From: Richard Leitner <richard.leitner@skidata.com>
To: Marco Felsch <m.felsch@pengutronix.de>, <robh+dt@kernel.org>,
<fancer.lancer@gmail.com>
Cc: <linux-usb@vger.kernel.org>, <devicetree@vger.kernel.org>,
<kernel@pengutronix.de>
Subject: Re: [PATCH 4/4] usb: usb251xb: add pm_ops
Date: Wed, 18 Sep 2019 10:15:09 +0200 [thread overview]
Message-ID: <2c720a64-5ca6-5f5c-1b7e-ea2d63f83bd0@skidata.com> (raw)
In-Reply-To: <20190917144449.32739-5-m.felsch@pengutronix.de>
On 17/09/2019 16:44, Marco Felsch wrote:
> Currently the driver don't support pm_ops. These ops are not necessary
> if the supply isn't switchable (always on). This assumptions seems to be
> wrong because no one needs a powered hub during suspend-to-ram/disk.
>
> So adding simple_dev_pm_ops to be able to switch off the hub during
> suspend and to restore the config after a resume operation.
>
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
Hi,
please feel free to add:
Acked-by: Richard Leitner <richard.leitner@skidata.com>
regards;Richard.L
> ---
> drivers/usb/misc/usb251xb.c | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/drivers/usb/misc/usb251xb.c b/drivers/usb/misc/usb251xb.c
> index bc031d33f433..5bba19937da1 100644
> --- a/drivers/usb/misc/usb251xb.c
> +++ b/drivers/usb/misc/usb251xb.c
> @@ -701,6 +701,29 @@ static int usb251xb_i2c_probe(struct i2c_client *i2c,
> return usb251xb_probe(hub);
> }
>
> +static int __maybe_unused usb251xb_suspend(struct device *dev)
> +{
> + struct i2c_client *client = to_i2c_client(dev);
> + struct usb251xb *hub = i2c_get_clientdata(client);
> +
> + return regulator_disable(hub->vdd);
> +}
> +
> +static int __maybe_unused usb251xb_resume(struct device *dev)
> +{
> + struct i2c_client *client = to_i2c_client(dev);
> + struct usb251xb *hub = i2c_get_clientdata(client);
> + int err;
> +
> + err = regulator_enable(hub->vdd);
> + if (err)
> + return err;
> +
> + return usb251xb_connect(hub);
> +}
> +
> +static SIMPLE_DEV_PM_OPS(usb251xb_pm_ops, usb251xb_suspend, usb251xb_resume);
> +
> static const struct i2c_device_id usb251xb_id[] = {
> { "usb2512b", 0 },
> { "usb2512bi", 0 },
> @@ -718,6 +741,7 @@ static struct i2c_driver usb251xb_i2c_driver = {
> .driver = {
> .name = DRIVER_NAME,
> .of_match_table = of_match_ptr(usb251xb_of_match),
> + .pm = &usb251xb_pm_ops,
> },
> .probe = usb251xb_i2c_probe,
> .id_table = usb251xb_id,
>
prev parent reply other threads:[~2019-09-18 8:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 14:44 [PATCH 0/4] Add simple-pm ops Marco Felsch
2019-09-17 14:44 ` [PATCH 1/4] dt-bindings: usb: usb251xb: add documentation for voltage supply Marco Felsch
2019-09-18 8:13 ` Richard Leitner
2019-09-30 23:07 ` Rob Herring
2019-09-17 14:44 ` [PATCH 2/4] usb: usb251xb: add vdd supply support Marco Felsch
2019-09-18 8:14 ` Richard Leitner
2019-09-17 14:44 ` [PATCH 3/4] usb: usb251xb: simplify reset helper Marco Felsch
2019-09-18 8:14 ` Richard Leitner
2019-09-17 14:44 ` [PATCH 4/4] usb: usb251xb: add pm_ops Marco Felsch
2019-09-18 8:15 ` Richard Leitner [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=2c720a64-5ca6-5f5c-1b7e-ea2d63f83bd0@skidata.com \
--to=richard.leitner@skidata.com \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-usb@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=robh+dt@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).