From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
kernel@collabora.com,
Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2] arm64: dts: mt8192: Follow binding order for SCP registers
Date: Thu, 5 May 2022 15:40:03 +0200 [thread overview]
Message-ID: <1b42b5aa-2020-b545-72ab-96ec14ef454a@gmail.com> (raw)
In-Reply-To: <20220504214516.2957504-1-nfraprado@collabora.com>
On 04/05/2022 23:45, Nícolas F. R. A. Prado wrote:
> The dt-binding for SCP documents the reg-names order as sram, cfg,
> l1tcm. Update the SCP node on the mt8192 devicetree to follow that
> order, which gets rid of a dtbs_check warning. This doesn't change any
> behavior since the SCP driver accesses the memory regions through the
> names anyway.
>
> Fixes: c63556ec6bfe ("arm64: dts: mt8192: Add SCP node")
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
>
Applied thanks!
> ---
>
> Changes in v2:
> - Added missing Fixes tag
>
> arch/arm64/boot/dts/mediatek/mt8192.dtsi | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8192.dtsi b/arch/arm64/boot/dts/mediatek/mt8192.dtsi
> index 26dbe9ecc528..733aec2e7f77 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8192.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8192.dtsi
> @@ -699,9 +699,9 @@ spi7: spi@1101e000 {
> scp: scp@10500000 {
> compatible = "mediatek,mt8192-scp";
> reg = <0 0x10500000 0 0x100000>,
> - <0 0x10700000 0 0x8000>,
> - <0 0x10720000 0 0xe0000>;
> - reg-names = "sram", "l1tcm", "cfg";
> + <0 0x10720000 0 0xe0000>,
> + <0 0x10700000 0 0x8000>;
> + reg-names = "sram", "cfg", "l1tcm";
> interrupts = <GIC_SPI 435 IRQ_TYPE_LEVEL_HIGH 0>;
> clocks = <&infracfg CLK_INFRA_SCPSYS>;
> clock-names = "main";
prev parent reply other threads:[~2022-05-05 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 21:45 [PATCH v2] arm64: dts: mt8192: Follow binding order for SCP registers Nícolas F. R. A. Prado
2022-05-05 2:50 ` Chen-Yu Tsai
2022-05-05 8:16 ` AngeloGioacchino Del Regno
2022-05-05 13:40 ` Matthias Brugger [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=1b42b5aa-2020-b545-72ab-96ec14ef454a@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=nfraprado@collabora.com \
--cc=robh+dt@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).