From: sashiko-bot@kernel.org
To: "Mukesh Ojha" <mukesh.ojha@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 14/24] arm64: dts: qcom: sm4450: Reduce OS PDC DRV span to 0x10000
Date: Wed, 27 May 2026 09:53:42 +0000 [thread overview]
Message-ID: <20260527095343.9192E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260527094333.2311731-15-mukesh.ojha@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Reducing the `reg` span to 0x10000 in the device tree is futile without an accompanying driver change and will intentionally trigger a boot warning.
--
commit befb5e3c3aa5e0f54a7fff3d0f4a5e96013f4a7e
Author: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
arm64: dts: qcom: sm4450: Reduce OS PDC DRV span to 0x10000
The OS PDC DRV register window on sm4450 spans 0x10000 bytes, so this
commit reduces the size of the first reg entry from 0x30000 to 0x10000.
> diff --git a/arch/arm64/boot/dts/qcom/sm4450.dtsi b/arch/arm64/boot/dts/qcom/sm4450.dtsi
> --- a/arch/arm64/boot/dts/qcom/sm4450.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm4450.dtsi
> @@ -464,7 +464,7 @@ dispcc: clock-controller@af00000 {
>
> pdc: interrupt-controller@b220000 {
> compatible = "qcom,sm4450-pdc", "qcom,pdc";
> - reg = <0 0x0b220000 0 0x30000>, <0 0x174000f0 0 0x64>;
> + reg = <0 0x0b220000 0 0x10000>, <0 0x174000f0 0 0x64>;
[Severity: Medium]
Will this change cause a boot warning and fail to actually reduce the mapping
size?
Looking at the qcom-pdc driver in drivers/irqchip/qcom-pdc.c, it enforces a
minimum mapping size of QCOM_PDC_SIZE (0x30000) for all devices to maintain
backward compatibility. In qcom_pdc_probe(), it calculates the size as:
res_size = max_t(resource_size_t, resource_size(&res), QCOM_PDC_SIZE);
If the device tree provides a size smaller than 0x30000 (like 0x10000), the
driver automatically expands the mapping back to 0x30000 and logs a warning:
"%pOF: invalid reg size, please fix DT".
Since there are no accompanying driver changes to gracefully accept the smaller
size for newer compatibles like "qcom,sm4450-pdc", does this patch introduce a
spurious warning on every boot without achieving the intended mapping
reduction?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260527094333.2311731-1-mukesh.ojha@oss.qualcomm.com?part=14
next prev parent reply other threads:[~2026-05-27 9:53 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 9:43 [PATCH v2 00/24] dt-bindings/dts: qcom: Fix PDC OS Direct Resource Voter region window size Mukesh Ojha
2026-05-27 9:43 ` [PATCH v2 01/24] dt-bindings: qcom,pdc: Fix OS DRV reg size in example Mukesh Ojha
2026-05-27 9:43 ` [PATCH v2 02/24] arm64: dts: qcom: sdm845: Reduce OS PDC DRV span to 0x10000 Mukesh Ojha
2026-05-27 10:17 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 03/24] arm64: dts: qcom: sdm670: " Mukesh Ojha
2026-05-27 10:06 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 04/24] arm64: dts: qcom: sc7180: " Mukesh Ojha
2026-05-27 10:06 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 05/24] arm64: dts: qcom: sc7280: " Mukesh Ojha
2026-05-27 10:07 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 06/24] arm64: dts: qcom: sc8180x: " Mukesh Ojha
2026-05-27 10:07 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 07/24] arm64: dts: qcom: sm8150: " Mukesh Ojha
2026-05-27 10:17 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 08/24] arm64: dts: qcom: sc8280xp: " Mukesh Ojha
2026-05-27 10:15 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 09/24] arm64: dts: qcom: sm8250: " Mukesh Ojha
2026-05-27 10:04 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 10/24] arm64: dts: qcom: sm8350: " Mukesh Ojha
2026-05-27 10:23 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 11/24] arm64: dts: qcom: sm8450: " Mukesh Ojha
2026-05-27 10:01 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 12/24] arm64: dts: qcom: sm8550: " Mukesh Ojha
2026-05-27 10:06 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 13/24] arm64: dts: qcom: sm8650: " Mukesh Ojha
2026-05-27 10:02 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 14/24] arm64: dts: qcom: sm4450: " Mukesh Ojha
2026-05-27 9:53 ` sashiko-bot [this message]
2026-05-27 9:43 ` [PATCH v2 15/24] arm64: dts: qcom: x1e80100: " Mukesh Ojha
2026-05-27 10:11 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 16/24] arm64: dts: qcom: sm6350: " Mukesh Ojha
2026-05-27 10:12 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 17/24] arm64: dts: qcom: sar2130p: " Mukesh Ojha
2026-05-27 10:14 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 18/24] arm64: dts: qcom: talos: " Mukesh Ojha
2026-05-27 10:16 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 19/24] arm64: dts: qcom: monaco: " Mukesh Ojha
2026-05-27 9:43 ` [PATCH v2 20/24] arm64: dts: qcom: lemans: " Mukesh Ojha
2026-05-27 10:32 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 21/24] arm64: dts: qcom: sdx75: " Mukesh Ojha
2026-05-27 10:24 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 22/24] arm64: dts: qcom: milos: " Mukesh Ojha
2026-05-27 10:25 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 23/24] arm64: dts: qcom: qdu1000: " Mukesh Ojha
2026-05-27 10:22 ` sashiko-bot
2026-05-27 9:43 ` [PATCH v2 24/24] arm64: dts: qcom: eliza: " Mukesh Ojha
2026-05-27 10:15 ` sashiko-bot
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=20260527095343.9192E1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=mukesh.ojha@oss.qualcomm.com \
--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