From: Harikrishna shenoy <h-shenoy@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <robh@kernel.org>,
<Laurent.pinchart@ideasonboard.com>, <airlied@gmail.com>,
<andrzej.hajda@intel.com>, <conor+dt@kernel.org>,
<devarsht@ti.com>, <devicetree@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>, <jernej.skrabec@gmail.com>,
<jonas@kwiboo.se>, <krzk+dt@kernel.org>,
<linux-kernel@vger.kernel.org>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<neil.armstrong@linaro.org>, <rfoss@kernel.org>, <s-jain1@ti.com>,
<simona@ffwll.ch>, <sjakhade@cadence.com>, <tzimmermann@suse.de>,
<u-kumar1@ti.com>, <yamonkar@cadence.com>, <pthombar@cadence.com>
Subject: Re: [PATCH] dt-bindings: drm/bridge: Update reg-name list for cdns,mhdp8546 compatible
Date: Mon, 10 Nov 2025 15:53:31 +0530 [thread overview]
Message-ID: <9599e17c-96d5-448f-96a2-bbcfcc3657a2@ti.com> (raw)
In-Reply-To: <eb86cb58-6520-4a24-9e04-f10e2466fac6@kernel.org>
On 07/11/25 18:57, Krzysztof Kozlowski wrote:
> On 07/11/2025 14:15, Harikrishna Shenoy wrote:
>> Remove j721e-intg register name from reg-name list for cdns,mhdp8546
>> compatible. The j721e-intg registers are specific to TI SoCs, so they
>> are not required for compatibles other than ti,j721e-mhdp8546.
>>
>> Move the register name constraints to the appropriate compatibility
>> sections to ensure the correct register names are used with each
>> compatible value.
>>
>> Fixes: 7169d082e7e6 ("dt-bindings: drm/bridge: MHDP8546 bridge binding changes for HDCP")
>> Signed-off-by: Harikrishna Shenoy <h-shenoy@ti.com>
>> ---
>>
>> Links to some discussions pointing to need for a fixes patch:
>> https://lore.kernel.org/all/20250903220312.GA2903503-robh@kernel.org/
>> https://lore.kernel.org/all/d2367789-6b54-4fc2-bb7c-609c0fe084d3@ti.com/
>>
>> .../bindings/display/bridge/cdns,mhdp8546.yaml | 13 +++++++------
>> 1 file changed, 7 insertions(+), 6 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml
>> index c2b369456e4e2..2fdb4f7108ed5 100644
>> --- a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml
>> +++ b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml
>> @@ -30,10 +30,6 @@ properties:
>>
>> reg-names:
>> minItems: 1
>> - items:
>> - - const: mhdptx
>> - - const: j721e-intg
>> - - const: mhdptx-sapb
>>
>> clocks:
>> maxItems: 1
>> @@ -103,7 +99,10 @@ allOf:
>> maxItems: 3
>> reg-names:
>> minItems: 2
>> - maxItems: 3
>> + items:
>> + - const: mhdptx
>> + - const: j721e-intg
>> + - const: mhdptx-sapb
>> else:
>> properties:
>> reg:
>> @@ -111,7 +110,9 @@ allOf:
>> maxItems: 2
>> reg-names:
>> minItems: 1
>> - maxItems: 2
>> + items:
>> + - const: mhdptx
>> + - const: mhdptx-sapb
>
> This does not match regs now. Look which entry is the second - it is
> always DSS_EDP0_INTG_CFG_VP
> Optional item should be the last, not the middle. That's why DT
Hi Krzysztof,
Thanks for the review, will update the reg-description for
ti,j721e-mhdp8546 j721e-intg is mandatory and for cdns,mhdp8546
j721e-intg is
not needed, will update and separate the reg description list according
to compatibles as well.
> maintainers ask (and it is even documented) to post complete bindings.
> Complete means all registers, entire address space.
>
I understand the need to post complete bindings, but this is a fixes
patch which tries to address the concerns raised in previous
discussions, not sure if it would be appropriate to add other register
in address space like DSC which have not been updated in binding?
Regards,
Hari
> Best regards,
> Krzysztof
prev parent reply other threads:[~2025-11-10 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 13:15 Harikrishna Shenoy
2025-11-07 13:27 ` Krzysztof Kozlowski
2025-11-10 10:23 ` Harikrishna shenoy [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=9599e17c-96d5-448f-96a2-bbcfcc3657a2@ti.com \
--to=h-shenoy@ti.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=pthombar@cadence.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=s-jain1@ti.com \
--cc=simona@ffwll.ch \
--cc=sjakhade@cadence.com \
--cc=tzimmermann@suse.de \
--cc=u-kumar1@ti.com \
--cc=yamonkar@cadence.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®