From: Jonathan Cameron <jic23@kernel.org>
To: David Heidelberg <david@ixit.cz>
Cc: Dmitry Osipenko <digetx@gmail.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v5 6/7] iio: light: al3320a implement devm_add_action_or_reset
Date: Fri, 21 Feb 2020 11:11:59 +0000 [thread overview]
Message-ID: <20200221111159.53100ccc@archlinux> (raw)
In-Reply-To: <1581795779.188492.1@ixit.cz>
On Sat, 15 Feb 2020 20:42:59 +0100
David Heidelberg <david@ixit.cz> wrote:
> Thank you for fixes, it does look good.
> Only thing is fixes which should go into commit "iio: light: al3320a
> implement suspend support"[1] when into "iio: light: al3320a implement
> devm_add_action_or_reset" [2].
>
> + return i2c_smbus_write_byte_data(client, AL3320A_REG_CONFIG, val);
>
> and
>
> +static SIMPLE_DEV_PM_OPS(al3320a_pm_ops, al3320a_suspend,
> al3320a_resume);
>
>
> Thank you very much for merging and next time
> I'll spend more time with review and doing final build test.
Gah. I messed that up. Anyhow, now fixed and pushed out with changes
in the right patch.
Thanks,
Jonathan
>
> David
>
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?h=testing&id=d74856400b2dcb2e0eab2132c779408809566431
> [2]
> https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?h=testing&id=4b1b42bcd993258628fabc5e35f20a202b1e9f7b
>
>
> On Sat, Feb 15, 2020 at 18:38, Jonathan Cameron <jic23@kernel.org>
> wrote:
> > On Tue, 11 Feb 2020 20:12:00 +0100
> > David Heidelberg <david@ixit.cz> wrote:
> >
> >> Use devm_add_action_or_reset to automatically disable the device
> >> and allow you to get rid of the remove function entirely.
> >>
> >> Signed-off-by: David Heidelberg <david@ixit.cz>
> >
> > This doesn't build as is. I've fixed up but please take a close
> > look at the result.
> >
> >> ---
> >> drivers/iio/light/al3320a.c | 20 ++++++++++++++------
> >> 1 file changed, 14 insertions(+), 6 deletions(-)
> >>
> >> diff --git a/drivers/iio/light/al3320a.c
> >> b/drivers/iio/light/al3320a.c
> >> index affa4c6c199a..49e73e24fff6 100644
> >> --- a/drivers/iio/light/al3320a.c
> >> +++ b/drivers/iio/light/al3320a.c
> >> @@ -87,6 +87,13 @@ static int al3320a_set_pwr(struct i2c_client
> >> *client, bool pwr)
> >> return i2c_smbus_write_byte_data(data->client,
> >> AL3320A_REG_CONFIG, val);
> >> }
> >>
> >> +static void al3320a_set_pwr_off(void *_data)
> >> +{
> >> + struct al3320a_data *data = _data;
> >> +
> >> + al3320a_set_pwr(data->client, false);
> >> +}
> >> +
> >> static int al3320a_init(struct al3320a_data *data)
> >> {
> >> int ret;
> >> @@ -206,12 +213,14 @@ static int al3320a_probe(struct i2c_client
> >> *client,
> >> dev_err(&client->dev, "al3320a chip init failed\n");
> >> return ret;
> >> }
> >> - return devm_iio_device_register(&client->dev, indio_dev);
> >> -}
> >>
> >> -static int al3320a_remove(struct i2c_client *client)
> >> -{
> >> - return al3320a_set_pwr(client, false);
> >> + ret = devm_add_action_or_reset(&client->dev,
> >> + al3320a_set_pwr_off,
> >> + data);
> >> + if (ret < 0)
> >> + return ret;
> >> +
> >> + return devm_iio_device_register(&client->dev, indio_dev);
> >> }
> >>
> >> static int __maybe_unused al3320a_suspend(struct device *dev)
> >> @@ -238,7 +247,6 @@ static struct i2c_driver al3320a_driver = {
> >> .pm = &al3320a_pm_ops,
> >> },
> >> .probe = al3320a_probe,
> >> - .remove = al3320a_remove,
> >> .id_table = al3320a_id,
> >> };
> >>
> >
>
>
next prev parent reply other threads:[~2020-02-21 11:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 19:11 [PATCH v5 0/7] iio: light: AL3010 introduction David Heidelberg
2020-02-11 19:11 ` [PATCH v5 1/7] dt-bindings: iio: light: add support for Dyna-Image AL3320A David Heidelberg
2020-02-15 16:59 ` Jonathan Cameron
2020-02-18 21:01 ` Rob Herring
2020-02-11 19:11 ` [PATCH v5 2/7] dt-bindings: iio: light: add support for Dyna-Image AL3010 David Heidelberg
2020-02-15 17:00 ` Jonathan Cameron
2020-02-18 21:01 ` Rob Herring
2020-02-11 19:11 ` [PATCH v5 3/7] iio: light: al3320a slightly improve code formatting David Heidelberg
2020-02-15 17:08 ` Jonathan Cameron
2020-02-11 19:11 ` [PATCH v5 4/7] iio: light: add Dyna-Image AL3010 driver David Heidelberg
2020-02-14 15:58 ` Jonathan Cameron
2020-02-14 22:09 ` [PATCH v6] " David Heidelberg
2020-02-15 17:09 ` Jonathan Cameron
2020-02-11 19:11 ` [PATCH v5 5/7] iio: light: al3320a implement suspend support David Heidelberg
2020-02-15 17:15 ` Jonathan Cameron
2020-02-15 17:34 ` David Heidelberg
2020-02-15 18:34 ` Jonathan Cameron
2020-02-15 17:20 ` Jonathan Cameron
2020-02-11 19:12 ` [PATCH v5 6/7] iio: light: al3320a implement devm_add_action_or_reset David Heidelberg
2020-02-15 17:22 ` Jonathan Cameron
2020-02-15 18:38 ` Jonathan Cameron
2020-02-15 19:42 ` David Heidelberg
2020-02-21 11:11 ` Jonathan Cameron [this message]
2020-02-11 19:12 ` [PATCH v5 7/7] iio: light: al3320a allow module autoload and polish David Heidelberg
2020-02-15 17:22 ` Jonathan Cameron
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=20200221111159.53100ccc@archlinux \
--to=jic23@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=david@ixit.cz \
--cc=digetx@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pmeerw@pmeerw.net \
--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).