From: Krzysztof Kozlowski <krzk@kernel.org>
To: niravkumar.l.rabara@intel.com, Dinh Nguyen <dinguyen@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
nirav.rabara@altera.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: socfpga: agilex5: fix gpio0 address
Date: Wed, 12 Feb 2025 16:31:53 +0100 [thread overview]
Message-ID: <162eef45-3740-4197-adf4-8f20850b332c@kernel.org> (raw)
In-Reply-To: <20250212100131.2668403-1-niravkumar.l.rabara@intel.com>
On 12/02/2025 11:01, niravkumar.l.rabara@intel.com wrote:
> From: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
>
> Fix gpio0 controller address for Agilex5.
How do you fix it exactly?
>
> Fixes: 3f7c869e143a ("arm64: dts: socfpga: agilex5: Add gpio0 node and spi dma handshake id")
> Cc: stable@vger.kernel.org
> Signed-off-by: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
> ---
> arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi b/arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi
> index 51c6e19e40b8..9e4ef24c8318 100644
> --- a/arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi
> +++ b/arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi
> @@ -222,7 +222,7 @@ i3c1: i3c@10da1000 {
> status = "disabled";
> };
>
> - gpio0: gpio@ffc03200 {
> + gpio0: gpio@10c03200 {
I see now warning. Are you sure you tested it according to
maintainer-soc-clean-dts profile?
> compatible = "snps,dw-apb-gpio";
> reg = <0xffc03200 0x100>;
> #address-cells = <1>;
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-12 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 10:01 [PATCH] arm64: dts: socfpga: agilex5: fix gpio0 address niravkumar.l.rabara
2025-02-12 15:31 ` Krzysztof Kozlowski [this message]
2025-02-12 16:03 ` Rabara, Niravkumar L
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=162eef45-3740-4197-adf4-8f20850b332c@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nirav.rabara@altera.com \
--cc=niravkumar.l.rabara@intel.com \
--cc=robh@kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).