From: Vaishnav Achath <vaishnav.a@ti.com>
To: Jai Luthra <j-luthra@ti.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Andrew Davis <afd@ti.com>,
Bryan Brattlof <bb@ti.com>, Dhruva Gole <d-gole@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Devarsh Thakkar <devarsht@ti.com>,
Aradhya Bhatia <a-bhatia1@ti.com>
Subject: Re: [PATCH 1/4] arm64: dts: ti: k3-am62p: Fix memory ranges for DMSS
Date: Mon, 12 Feb 2024 17:33:54 +0530 [thread overview]
Message-ID: <994c6ff1-96ed-4dde-94a1-43f6cab2a005@ti.com> (raw)
In-Reply-To: <20240201-am62p_csi-v1-1-c83bb9eaeb49@ti.com>
Hi Jai,
Thanks for the patch.
On 01/02/24 18:37, Jai Luthra wrote:
> The INTR module for DMASS1 (CSI specific DMASS) is outside the currently
> available ranges, as it starts at 0x4e400000. So fix the ranges property
> to enable programming the interrupts correctly.
>
> Fixes: 29075cc09f43 ("arm64: dts: ti: Introduce AM62P5 family of SoCs")
> Signed-off-by: Jai Luthra <j-luthra@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am62p.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62p.dtsi b/arch/arm64/boot/dts/ti/k3-am62p.dtsi
> index 84ffe7b9dcaf..4f22b5d9fb9f 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62p.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62p.dtsi
> @@ -71,7 +71,7 @@ cbass_main: bus@f0000 {
> <0x00 0x43600000 0x00 0x43600000 0x00 0x00010000>, /* SA3 sproxy data */
> <0x00 0x44043000 0x00 0x44043000 0x00 0x00000fe0>, /* TI SCI DEBUG */
> <0x00 0x44860000 0x00 0x44860000 0x00 0x00040000>, /* SA3 sproxy config */
> - <0x00 0x48000000 0x00 0x48000000 0x00 0x06400000>, /* DMSS */
> + <0x00 0x48000000 0x00 0x48000000 0x00 0x06408000>, /* DMSS */
Reviewed-by: Vaishnav Achath <vaishnav.a@ti.com>
> <0x00 0x60000000 0x00 0x60000000 0x00 0x08000000>, /* FSS0 DAT1 */
> <0x00 0x70000000 0x00 0x70000000 0x00 0x00010000>, /* OCSRAM */
> <0x01 0x00000000 0x01 0x00000000 0x00 0x00310000>, /* A53 PERIPHBASE */
>
next prev parent reply other threads:[~2024-02-12 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 13:06 [PATCH 0/4] arm64: dts: ti: Enable camera for SK-AM62P Jai Luthra
2024-02-01 13:07 ` [PATCH 1/4] arm64: dts: ti: k3-am62p: Fix memory ranges for DMSS Jai Luthra
2024-02-12 12:03 ` Vaishnav Achath [this message]
2024-02-01 13:07 ` [PATCH 2/4] arm64: dts: ti: k3-am62p: Add DMASS1 for CSI Jai Luthra
2024-02-12 12:05 ` Vaishnav Achath
2024-02-01 13:07 ` [PATCH 3/4] arm64: dts: ti: k3-am62p: Add nodes for CSI-RX Jai Luthra
2024-02-12 12:06 ` Vaishnav Achath
2024-02-01 13:07 ` [PATCH 4/4] arm64: dts: ti: Enable overlays for SK-AM62P Jai Luthra
2024-02-12 12:07 ` Vaishnav Achath
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=994c6ff1-96ed-4dde-94a1-43f6cab2a005@ti.com \
--to=vaishnav.a@ti.com \
--cc=a-bhatia1@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-luthra@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
/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
all inboxes | Powered by JetHome®