From: sashiko-bot@kernel.org
To: "Rosen Penev" <rosenp@gmail.com>
Cc: linux-rtc@vger.kernel.org,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH v3] rtc: stmp3xxx: use devm_platform_ioremap_resource()
Date: Sun, 04 Oct 2026 22:18:35 +0000 [thread overview]
Message-ID: <20261004221836.613FF1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261004221327.416323-1-rosenp@gmail.com>
> Replace the open-coded platform_get_resource() plus devm_ioremap()
> sequence with a single devm_platform_ioremap_resource() call, which folds
> the resource lookup and mapping into one step and returns an ERR_PTR on
> failure, checked with IS_ERR() and propagated via PTR_ERR().
>
> Move the mapping ahead of the devm_kzalloc() so that an error or deferred
> probe is handled before the rtc_data allocation, avoiding needless work.
>
> The fsl,stmp3xxx-rtc nodes in imx23.dtsi (reg = <0x8005c000 0x2000>) and
> imx28.dtsi (reg = <0x80056000 0x2000>) each provide a single
> non-overlapping IORESOURCE_MEM window, so the region reservation now
> performed by devm_platform_ioremap_resource() introduces no conflict.
>
> Keep the alarm IRQ in a local, as it is only used in probe, and fail
> probe on a platform_get_irq() error instead of passing it to
> devm_request_irq(). Drop the open-coded error messages, as
> devm_platform_ioremap_resource() and devm_request_irq() already
> report failures.
>
> Assisted-by: LLM
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261004221327.416323-1-rosenp@gmail.com?part=1
prev parent reply other threads:[~2026-10-04 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 22:13 [PATCH v3] rtc: stmp3xxx: use devm_platform_ioremap_resource() Rosen Penev
2026-10-04 22:18 ` sashiko-bot [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=20261004221836.613FF1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-rtc@vger.kernel.org \
--cc=rosenp@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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