From: Harikrishna Shenoy <h-shenoy@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<r-ravikumar@ti.com>, <m-chawdhry@ti.com>, <b-padhi@ti.com>,
<u-kumar1@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<aradhya.bhatia@linux.dev>, <devarsht@ti.com>, <s-jain1@ti.com>
Subject: Re: [PATCH v2 1/2] arm64: dts: ti: k3-j721e-main: Update DSS EDP integration configuration register
Date: Mon, 8 Sep 2025 11:50:54 +0530 [thread overview]
Message-ID: <ab3b7c55-842e-47fe-b7c2-d076da08c3c0@ti.com> (raw)
In-Reply-To: <ffcc5d3f-bf3f-47a5-a034-a20c59f93ff1@ideasonboard.com>
On 9/8/25 11:46, Tomi Valkeinen wrote:
> Hi,
>
> On 07/09/2025 21:28, Harikrishna Shenoy wrote:
>> Fix size of DSS_EDP0_INT_CFG_VP to 256B as stated in
>> TRM Table 2-1 MAIN Domain Memory Map.
>> Link: https://www.ti.com/lit/zip/spruil1/SPRUIL_DRA829_TDA4VM
> What issues does this cause?
>
> Tomi
Hi Tomi,
No issues seen in driver functionality yet, but it might when we enable
HDCP,MST which driver supports but not enabled yet.
so thought it is better to align as per TRM, hence aligning the size as
per TRM.
>> Fixes: 92c996f4ceab ("arm64: dts: ti: k3-j721e-*: add DP & DP PHY")
>> Reviewed-by: Devarsh Thakkar <devarsht@ti.com>
>> Signed-off-by: Harikrishna Shenoy <h-shenoy@ti.com>
>> ---
>> arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-j721e-main.dtsi b/arch/arm64/boot/dts/ti/k3-j721e-main.dtsi
>> index ab3666ff4297..3fa7537d5414 100644
>> --- a/arch/arm64/boot/dts/ti/k3-j721e-main.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-j721e-main.dtsi
>> @@ -1863,7 +1863,7 @@ mhdp: dp-bridge@a000000 {
>> * the PHY driver.
>> */
>> reg = <0x00 0x0a000000 0x00 0x030a00>, /* DSS_EDP0_V2A_CORE_VP_REGS_APB */
>> - <0x00 0x04f40000 0x00 0x20>; /* DSS_EDP0_INTG_CFG_VP */
>> + <0x00 0x04f40000 0x00 0x100>; /* DSS_EDP0_INTG_CFG_VP */
>> reg-names = "mhdptx", "j721e-intg";
>>
>> clocks = <&k3_clks 151 36>;
next prev parent reply other threads:[~2025-09-08 6:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 18:28 [PATCH v2 0/2] Update DSS EDP integration configuration register Harikrishna Shenoy
2025-09-07 18:28 ` [PATCH v2 1/2] arm64: dts: ti: k3-j721e-main: " Harikrishna Shenoy
2025-09-08 4:34 ` Beleswar Prasad Padhi
2025-09-08 4:51 ` Harikrishna Shenoy
2025-09-08 6:16 ` Tomi Valkeinen
2025-09-08 6:20 ` Harikrishna Shenoy [this message]
2025-09-08 6:28 ` Tomi Valkeinen
2025-09-09 1:54 ` Kumar, Udit
2025-09-07 18:28 ` [PATCH v2 2/2] arm64: dts: ti: k3-j784s4-j742s2-main-common: " Harikrishna Shenoy
2025-09-08 4:37 ` Beleswar Prasad Padhi
2025-09-08 4:50 ` Harikrishna Shenoy
2025-09-08 4:59 ` Beleswar Prasad Padhi
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=ab3b7c55-842e-47fe-b7c2-d076da08c3c0@ti.com \
--to=h-shenoy@ti.com \
--cc=aradhya.bhatia@linux.dev \
--cc=b-padhi@ti.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=nm@ti.com \
--cc=r-ravikumar@ti.com \
--cc=robh@kernel.org \
--cc=s-jain1@ti.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=u-kumar1@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