From: Lee Jones <lee@kernel.org>
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Philipp Zabel <p.zabel@pengutronix.de>,
Mark Brown <broonie@kernel.org>
Subject: Re: [RFC PATCH v3 2/2] mfd: syscon: allow reset control for syscon devices
Date: Wed, 4 Jan 2023 17:57:39 +0000 [thread overview]
Message-ID: <Y7W+E2/bywt16BqJ@google.com> (raw)
In-Reply-To: <33f6f9e66c8143515d36d17bf33d95362830f83f.camel@codeconstruct.com.au>
On Thu, 05 Jan 2023, Jeremy Kerr wrote:
> Hi Lee,
>
> > > @@ -124,7 +127,17 @@ static struct syscon *of_syscon_register(struct device_node *np, bool check_clk)
> > > } else {
> > > ret = regmap_mmio_attach_clk(regmap, clk);
> > > if (ret)
> > > - goto err_attach;
> > > + goto err_attach_clk;
> > > + }
> > > +
> > > + reset = of_reset_control_get_optional_exclusive(np, NULL);
> > > + if (IS_ERR(reset)) {
> > > + ret = PTR_ERR(reset);
> > > + goto err_attach_clk;
> > > + } else {
> > > + ret = reset_control_deassert(reset);
> > > + if (ret)
> > > + goto err_reset;
> > > }
> >
> > The else is superfluous, right?
>
> Yep, we could move that reset_control_deassert() out of the else block.
> If there are no other changes, I'll send a v4 with that.
I'd wait a little while to give Arnd a chance to respond.
Might save you a little work.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-01-04 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 2:56 [RFC PATCH v3 0/2] Add reset control for mfd syscon devices Jeremy Kerr
2022-12-11 2:56 ` [RFC PATCH v3 1/2] dt-bindings: mfd/syscon: Add resets property Jeremy Kerr
2022-12-11 2:57 ` [RFC PATCH v3 2/2] mfd: syscon: allow reset control for syscon devices Jeremy Kerr
2023-01-04 16:54 ` Lee Jones
2023-01-04 17:35 ` Jeremy Kerr
2023-01-04 17:57 ` Lee Jones [this message]
2023-01-04 22:34 ` Arnd Bergmann
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=Y7W+E2/bywt16BqJ@google.com \
--to=lee@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.