From: Andre Przywara <andre.przywara@arm.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Sanjay Chitroda" <sanjayembeddedse@gmail.com>,
"Michal Piekos" <michal.piekos@mmpsystems.pl>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Chen-Yu Tsai" <wens@kernel.org>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Samuel Holland" <samuel@sholland.org>,
"Maksim Kiselev" <bigunclemax@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] iio: adc: sun20i-gpadc: add A523 gpadc support
Date: Wed, 13 May 2026 23:34:38 +0200 [thread overview]
Message-ID: <20260513233438.2715cfb5@ryzen.lan> (raw)
In-Reply-To: <20260513171638.77af3b24@jic23-huawei>
On Wed, 13 May 2026 17:16:38 +0100
Jonathan Cameron <jic23@kernel.org> wrote:
Hi,
> On Wed, 13 May 2026 13:53:49 +0200
> Andre Przywara <andre.przywara@arm.com> wrote:
>
> > Hi Sanjay,
> >
> > thanks for having a look!
> >
> > On 5/13/26 13:44, Sanjay Chitroda wrote:
> > >
> > >
> > > On 13 May 2026 10:29:43 am IST, Michal Piekos <michal.piekos@mmpsystems.pl> wrote:
> > >> A523 differs from existing sun20i-gpadc-iio by having two clocks; bus
> > >> clock and module clock.
> > >>
> > >> Change driver to enable all clocks.
> > >>
> > >> Signed-off-by: Michal Piekos <michal.piekos@mmpsystems.pl>
> > >> ---
> > >> drivers/iio/adc/sun20i-gpadc-iio.c | 11 +++++++----
> > >> 1 file changed, 7 insertions(+), 4 deletions(-)
> > >>
> > >> diff --git a/drivers/iio/adc/sun20i-gpadc-iio.c b/drivers/iio/adc/sun20i-gpadc-iio.c
> > >> index 861c14da75ad..3f1f07b3a385 100644
> > >> --- a/drivers/iio/adc/sun20i-gpadc-iio.c
> > >> +++ b/drivers/iio/adc/sun20i-gpadc-iio.c
> > >> @@ -180,7 +180,7 @@ static int sun20i_gpadc_probe(struct platform_device *pdev)
> > >> struct iio_dev *indio_dev;
> > >> struct sun20i_gpadc_iio *info;
> > >> struct reset_control *rst;
> > >> - struct clk *clk;
> > >> + struct clk_bulk_data *clks;
> > >> int irq;
> > >> int ret;
> > >>
> > >> @@ -205,9 +205,11 @@ static int sun20i_gpadc_probe(struct platform_device *pdev)
> > >> if (IS_ERR(info->regs))
> > >> return PTR_ERR(info->regs);
> > >>
> > >> - clk = devm_clk_get_enabled(dev, NULL);
> > >> - if (IS_ERR(clk))
> > >> - return dev_err_probe(dev, PTR_ERR(clk), "failed to enable bus clock\n");
> > >> + ret = devm_clk_bulk_get_all_enabled(dev, &clks);
> > >> + if (ret <= 0)
> > >
> > > Thank you Michal for the change.
> > >
> > > Have you validated the changes ?
> > > It looks while success ret would be 0 and it would give return error.
> >
> > But devm_clk_bulk_get_all_enabled() returns the number of clocks found
> > and enabled. And since we need at least one, I think this is correct,
> > and the error message below reflects that.
>
> True but passing 0 to dev_err_probe() isn't going to do the right thing.
>
> Though from this function, 0 is an error you need to return an error code
> not 0 which to the caller looks like a success.
Ah, that's true - should have read your email first before answering to
Andy ;-)
So yeah, that needs a split handling, for == 0, and for < 0.
Cheers,
Andre
>
>
>
> >
> > To me that change looks good:
> >
> > Reviewed-by: Andre Przywara <andre.przywara@arm.com>
> >
> > Cheers,
> > Andre
> >
> >
> > >
> > > Thanks, Sanjay
> > >
> > >
> > >> + return dev_err_probe(
> > >> + dev, ret,
> > >> + "failed to enable clocks or no clocks defined\n");
> > >>
> > >> rst = devm_reset_control_get_exclusive(dev, NULL);
> > >> if (IS_ERR(rst))
> > >> @@ -243,6 +245,7 @@ static int sun20i_gpadc_probe(struct platform_device *pdev)
> > >>
> > >> static const struct of_device_id sun20i_gpadc_of_id[] = {
> > >> { .compatible = "allwinner,sun20i-d1-gpadc" },
> > >> + { .compatible = "allwinner,sun55i-a523-gpadc" },
> > >> { }
> > >> };
> > >> MODULE_DEVICE_TABLE(of, sun20i_gpadc_of_id);
> > >>
> > >
> >
>
>
next prev parent reply other threads:[~2026-05-13 21:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 4:59 [PATCH v2 0/3] Add GPADC support for A523 Michal Piekos
2026-05-13 4:59 ` [PATCH v2 1/3] dt-bindings: iio: adc: Add GPADC for Allwinner A523 Michal Piekos
2026-05-13 19:15 ` Conor Dooley
2026-05-13 4:59 ` [PATCH v2 2/3] iio: adc: sun20i-gpadc: add A523 gpadc support Michal Piekos
2026-05-13 11:44 ` Sanjay Chitroda
2026-05-13 11:53 ` Andre Przywara
2026-05-13 16:16 ` Jonathan Cameron
2026-05-13 21:34 ` Andre Przywara [this message]
2026-05-13 20:12 ` Andy Shevchenko
2026-05-13 21:19 ` Andre Przywara
2026-05-13 21:34 ` Andy Shevchenko
2026-05-13 20:10 ` Andy Shevchenko
2026-05-13 4:59 ` [PATCH v2 3/3] arm64: dts: allwinner: a523: add gpadc node Michal Piekos
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=20260513233438.2715cfb5@ryzen.lan \
--to=andre.przywara@arm.com \
--cc=andy@kernel.org \
--cc=bigunclemax@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jernej.skrabec@gmail.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--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=michal.piekos@mmpsystems.pl \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=sanjayembeddedse@gmail.com \
--cc=wens@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