From: sashiko-bot@kernel.org
To: "Larisa Grigore" <larisa.grigore@oss.nxp.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, imx@lists.linux.dev,
conor+dt@kernel.org, Frank.Li@kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2 08/10] arm64: dts: freescale: s32n79: Add UFS host controller
Date: Mon, 14 Sep 2026 14:01:56 +0000 [thread overview]
Message-ID: <20260914140157.434091F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260914125000.30812-9-larisa.grigore@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Missing Clock Enable for the UFS Core Clock
--
commit 90b92b70b82e1240cda14e91539c0096398b8f62
Author: Larisa Grigore <larisa.grigore@oss.nxp.com>
arm64: dts: freescale: s32n79: Add UFS host controller
Add the S32N79 UFS host controller node to the SoC dtsi. The controller
remains disabled by default and is enabled by board dts files as needed.
> diff --git a/arch/arm64/boot/dts/freescale/s32n79.dtsi b/arch/arm64/boot/dts/freescale/s32n79.dtsi
> index 94ab58783fdc8..0b51ca8bc7f9b 100644
> --- a/arch/arm64/boot/dts/freescale/s32n79.dtsi
> +++ b/arch/arm64/boot/dts/freescale/s32n79.dtsi
> @@ -100,6 +100,16 @@ uart7: serial@4aa40000 {
> status = "disabled";
> };
>
> + ufshc: ufs@4ac80000 {
> + compatible = "nxp,s32n79-ufshc", "jedec,ufs-2.0";
> + reg = <0x4ac80000 0x1000>, <0x4ac40000 0x1000>;
> + reg-names = "ufshc", "scm";
> + interrupt-parent = <&irqsteer_coss>;
> + interrupts = <211>;
> + clocks = <&clks 0x92>;
[Severity: High]
Does this node need a clock-names property to ensure the clock is enabled?
Without clock-names, the UFS core framework's automatic clock management
(ufshcd_setup_clocks) is bypassed. The ufs-nxp-s32n7 driver fetches this
clock via devm_clk_get() in ufs_s32n_init():
ufs->core_clk = devm_clk_get(dev, NULL);
if (IS_ERR(ufs->core_clk))
return dev_err_probe(dev, PTR_ERR(ufs->core_clk),
"Failed to get core clock.\n");
However, the driver never calls clk_prepare_enable(). Additionally, without a
power-domains property, the generic PM domain framework will not implicitly
enable the clock.
Could this cause the Common Clock Framework to disable it as an unused clock
during late initialization, leading to a bus lockup or synchronous external
abort when the device's memory-mapped registers are accessed?
> + status = "disabled";
> + };
> +
> irqsteer_coss: interrupt-controller@4ed00000 {
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260914125000.30812-1-larisa.grigore@oss.nxp.com?part=8
next prev parent reply other threads:[~2026-09-14 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 12:49 [PATCH v2 00/10] Add S32N79RDB UFS support Larisa Grigore
2026-09-14 12:49 ` [PATCH v2 01/10] ufs: unipro: Move Tx/Rx FSM state definitions to unipro.h Larisa Grigore
2026-09-14 12:49 ` [PATCH v2 02/10] ufs: unipro: Add TX/RX FSM state attributes Larisa Grigore
2026-09-14 12:49 ` [PATCH v2 03/10] ufs: host: Add common Hibern8 TX FSM polling helper Larisa Grigore
2026-09-14 13:25 ` sashiko-bot
2026-09-14 12:49 ` [PATCH v2 04/10] scsi: ufs: Move Versal2 M-PHY CREG access helpers into ufshcd-dwc Larisa Grigore
2026-09-14 12:49 ` [PATCH v2 05/10] scsi: ufs: dwc: Export common clock divider and link status helpers Larisa Grigore
2026-09-14 12:49 ` [PATCH v2 06/10] dt-bindings: ufs: Add NXP S32N79 UFS host controller Larisa Grigore
2026-09-14 12:49 ` [PATCH v2 07/10] scsi: ufs: Add NXP S32N79 UFS host controller driver Larisa Grigore
2026-09-14 12:49 ` [PATCH v2 08/10] arm64: dts: freescale: s32n79: Add UFS host controller Larisa Grigore
2026-09-14 14:01 ` sashiko-bot [this message]
2026-09-14 12:49 ` [PATCH v2 09/10] arm64: dts: freescale: s32n79-rdb: Enable UFS Larisa Grigore
2026-09-14 12:50 ` [PATCH v2 10/10] MAINTAINERS: Add NXP S32N7 UFS host controller entry Larisa Grigore
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=20260914140157.434091F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=larisa.grigore@oss.nxp.com \
--cc=linux-scsi@vger.kernel.org \
--cc=robh@kernel.org \
--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