From: s-vadapalli <s-vadapalli@ti.com>
To: Paresh Bhagat <p-bhagat@ti.com>
Cc: <nm@ti.com>, <vigneshr@ti.com>, <praneeth@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<khasim@ti.com>, <v-singh1@ti.com>, <afd@ti.com>, <bb@ti.com>,
<devarsht@ti.com>, <s-vadapalli@ti.com>
Subject: Re: [PATCH v3 1/2] arm64: dts: ti: k3-am62a-main: Fix main padcfg length
Date: Wed, 3 Sep 2025 12:02:28 +0530 [thread overview]
Message-ID: <6e206470-89a2-46c3-8fb9-357a56b2d03b@ti.com> (raw)
In-Reply-To: <20250903062513.813925-2-p-bhagat@ti.com>
On Wed, Sep 03, 2025 at 11:55:12AM +0530, Paresh Bhagat wrote:
> From: Vibhore Vardhan <vibhore@ti.com>
>
> The main pad configuration register region starts with the register
> MAIN_PADCFG_CTRL_MMR_CFG0_PADCONFIG0 with address 0x000f4000 and ends
> with the MAIN_PADCFG_CTRL_MMR_CFG0_PADCONFIG150 register with address
> 0x000f4258, as a result of which, total size of the region is 0x25c
> instead of 0x2ac.
>
> Reference Docs
> TRM (AM62A) - https://www.ti.com/lit/ug/spruj16b/spruj16b.pdf
> TRM (AM62D) - https://www.ti.com/lit/ug/sprujd4/sprujd4.pdf
>
> Fixes: 5fc6b1b62639c ("arm64: dts: ti: Introduce AM62A7 family of SoCs")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Vibhore Vardhan <vibhore@ti.com>
> Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Reviewed-by: Siddharth Vadapalli <s-vadapalli@ti.com>
Regards,
Siddharth.
next prev parent reply other threads:[~2025-09-03 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 6:25 [PATCH v3 0/2] Add USB support for AM62D2 Paresh Bhagat
2025-09-03 6:25 ` [PATCH v3 1/2] arm64: dts: ti: k3-am62a-main: Fix main padcfg length Paresh Bhagat
2025-09-03 6:32 ` s-vadapalli [this message]
2025-09-03 6:25 ` [PATCH v3 2/2] arm64: dts: ti: k3-am62d2-evm: Enable USB support Paresh Bhagat
2025-09-12 9:51 ` [PATCH v3 0/2] Add USB support for AM62D2 Nishanth Menon
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=6e206470-89a2-46c3-8fb9-357a56b2d03b@ti.com \
--to=s-vadapalli@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=khasim@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=p-bhagat@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=v-singh1@ti.com \
--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®