From: Jonathan Cameron <jic23@kernel.org>
To: Aren Moynihan <aren@peacevolution.org>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Chen-Yu Tsai" <wens@csie.org>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Samuel Holland" <samuel@sholland.org>,
"Kaustabh Chakraborty" <kauschluss@disroot.org>,
"Barnabás Czémán" <trabarni@gmail.com>,
"Ondrej Jirman" <megi@xff.cz>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, "Dragan Simic" <dsimic@manjaro.org>,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v3 3/6] iio: light: stk3310: Implement vdd and leda supplies
Date: Mon, 28 Oct 2024 20:38:39 +0000 [thread overview]
Message-ID: <20241028203839.65debe2b@jic23-huawei> (raw)
In-Reply-To: <ggpxs4mlkobdkvqxbzroeogqe2kxlixne7ly4njb5ynnszvvkv@3gusj5w53bbj>
On Mon, 28 Oct 2024 12:37:14 -0400
Aren Moynihan <aren@peacevolution.org> wrote:
> On Mon, Oct 28, 2024 at 04:38:37PM +0200, Andy Shevchenko wrote:
> > On Mon, Oct 28, 2024 at 10:19:57AM -0400, Aren Moynihan wrote:
> > > The vdd and leda supplies must be powered on for the chip to function
> > > and can be powered off during system suspend.
> > >
> > > Co-developed-by: Ondrej Jirman <megi@xff.cz>
> >
> > Missing SoB. Please, read Submitting Patches documentation for understanding
> > what has to be done here.
> >
> > > Signed-off-by: Aren Moynihan <aren@peacevolution.org>
> >
> > ...
> >
> > > Notes:
> > > I'm not sure what the proper way to handle attribution for this patch
> > > is. It was origionally based on a patch by Ondrej Jirman[1], but I have
> > > rewritten a large portion if it. I have included a Co-developed-by tag
> > > to indicate this, but haven't sent him this patch, so I'm not sure what
> > > to do about a Signed-off-by.
> >
> > Ah, seems you already aware of this issue. So, either drop Co-developed-by
> > (and if you wish you may give a credit in a free form inside commit message)
> > or make sure you get his SoB tag.
>
> Alright, thanks for clarifying that.
>
> > > mutex_init(&data->lock);
> >
> > Somewhere (in the previous patch?) you want to switch to devm_mutex_init().
>
> Good catch, it looks like that was being leaked before this refactor.
> Yeah that sounds like the right place, I'll include it in v4.
Not really on the leaking. Take a look at the cleanup for devm_mutex_init().
It's debug only and not all that useful in most cases.
However, it is good to not assume that now we have a devm_mutex_init()
available that is easy to use.
>
> > > + ret = devm_regulator_bulk_get(&client->dev, ARRAY_SIZE(data->supplies),
> > > + data->supplies);
> > > + if (ret)
> > > + return dev_err_probe(&client->dev, ret, "get regulators failed\n");
> >
> > > + return dev_err_probe(&client->dev, ret,
> > > + "regulator enable failed\n");
> >
> > > + ret = devm_add_action_or_reset(&client->dev, stk3310_regulators_disable, data);
> > > + if (ret)
> > > + return dev_err_probe(&client->dev, ret,
> > > + "failed to register regulator cleanup\n");
> >
> > With
> >
> > struct devuce *dev = &client->dev;
> >
> > at the top of the function makes these and more lines neater.
> >
> [snip]
> >
> > While changing to RCT order here, it seems you have inconsistent approach
> > elsewhere (in your own patches!). Please, be consistent with chosen style.
>
> Sounds easy enough to fix, I'll include these in v4.
>
> Thanks taking the time to review
> - Aren
next prev parent reply other threads:[~2024-10-28 21:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 14:19 [PATCH v3 0/6] iio: light: stk3310: support powering off during suspend Aren Moynihan
2024-10-28 14:19 ` [PATCH v3 1/6] dt-bindings: iio: light: stk33xx: add vdd and leda regulators Aren Moynihan
2024-10-28 14:19 ` [PATCH v3 2/6] iio: light: stk3310: handle all remove logic with devm callbacks Aren Moynihan
2024-10-28 14:19 ` [PATCH v3 3/6] iio: light: stk3310: Implement vdd and leda supplies Aren Moynihan
2024-10-28 14:38 ` Andy Shevchenko
2024-10-28 16:37 ` Aren Moynihan
2024-10-28 20:38 ` Jonathan Cameron [this message]
2024-10-28 20:44 ` Dragan Simic
2024-10-28 14:19 ` [PATCH v3 4/6] iio: light: stk3310: use dev_err_probe where possible Aren Moynihan
2024-10-28 14:44 ` Andy Shevchenko
2024-10-28 14:19 ` [PATCH v3 5/6] iio: light: stk3310: log error if reading the chip id fails Aren Moynihan
2024-10-28 14:45 ` Andy Shevchenko
2024-10-28 15:29 ` Aren
2024-10-28 15:59 ` Andy Shevchenko
2024-10-28 14:20 ` [PATCH v3 6/6] arm64: dts: allwinner: pinephone: Add power supplies to stk3311 Aren Moynihan
2024-10-28 20:42 ` [PATCH v3 0/6] iio: light: stk3310: support powering off during suspend 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=20241028203839.65debe2b@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=aren@peacevolution.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=jernej.skrabec@gmail.com \
--cc=kauschluss@disroot.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=megi@xff.cz \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=trabarni@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wens@csie.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