linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jayesh Choudhary <j-choudhary@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: <andrzej.hajda@intel.com>, <neil.armstrong@linaro.org>,
	<rfoss@kernel.org>, <Laurent.pinchart@ideasonboard.com>,
	<jonas@kwiboo.se>, <jernej.skrabec@gmail.com>,
	<airlied@gmail.com>, <daniel@ffwll.ch>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <sam@ravnborg.org>,
	<jani.nikula@intel.com>, <tzimmermann@suse.de>,
	<javierm@redhat.com>, <ville.syrjala@linux.intel.com>,
	<r-ravikumar@ti.com>, <lyude@redhat.com>,
	<alexander.deucher@amd.com>, <sjakhade@cadence.com>,
	<yamonkar@cadence.com>, <a-bhatia1@ti.com>,
	<tomi.valkeinen@ideasonboard.com>
Subject: Re: [PATCH 1/2] dt-bindings: drm/bridge: Add no-hpd property
Date: Thu, 23 Mar 2023 17:56:21 +0530	[thread overview]
Message-ID: <5cae1874-9c10-a909-906c-160ce3f91286@ti.com> (raw)
In-Reply-To: <d8be08b9-3043-d517-b5b8-86ea7a602e0b@linaro.org>



On 21/03/23 20:47, Krzysztof Kozlowski wrote:
> On 21/03/2023 15:28, Jayesh Choudhary wrote:
>>
>>
>> On 21/03/23 18:08, Krzysztof Kozlowski wrote:
>>> On 21/03/2023 13:02, Jayesh Choudhary wrote:
>>>>>
>>>>>> +    type: boolean
>>>>>> +    description:
>>>>>> +      Set if the HPD line on the bridge isn't hooked up to anything or is
>>>>>> +      otherwise unusable.
>>>>>
>>>>> It's the property of the panel, not bridge. Unless you want to say that
>>>>> bridge physically does not have HPD? Does it follow the standard in such
>>>>> case?
>>>>
>>>> MHDP does have hpd. But the mhdp driver should handle the cases when the
>>>
>>> This is about bindings, not driver. Your driver can still handle this as
>>> it wishes.
>>>
>>>> hpd pin of bridge is not connected to that of the DP-connector. This is
>>>> to add support for that. (optional property)
>>>
>>> Which is indicated by panel no-hpd, right?
>>
>> Actually no panel is involved in this. For TI SoC J721S2, the data
>> pipeline involves the bridge whose endpoint is directly the DP connector
>> with compatible 'dp-connector'. And in the binding dp-connector.yaml,
>> there isn't any 'no-hpd' property for this indication.
>>
>> Does this clarifies the issue? Or did I misinterpret your comment?
> 
> Yes, then you only need to narrow which hardware does not have HPD
> hooked up. Or at least clarify that it is not about driver having or not
> having HPD control...
> 

Okay. I will edit the commit message in v2. (after further review of the 
driver changes for this series)

I will mention that the mhdp bridge can work without its HPD pin hooked
up to the connector, but the current bridge driver throws an error when
hpd line is not connected to the connector. For such cases, using this 
optional property, we can bypass the hpd detection and instead use the 
auxiliary channels connected to the DP connector to confirm the connection.

Thanks,
-Jayesh



  reply	other threads:[~2023-03-23 12:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 14:08 [PATCH 0/2] "no-hpd" support in CDNS DP bridge driver Jayesh Choudhary
2023-03-16 14:08 ` [PATCH 1/2] dt-bindings: drm/bridge: Add no-hpd property Jayesh Choudhary
2023-03-17 12:38   ` Krzysztof Kozlowski
2023-03-21 12:02     ` Jayesh Choudhary
2023-03-21 12:38       ` Krzysztof Kozlowski
2023-03-21 14:28         ` Jayesh Choudhary
2023-03-21 15:17           ` Krzysztof Kozlowski
2023-03-23 12:26             ` Jayesh Choudhary [this message]
2023-03-16 14:08 ` [PATCH 2/2] drm: bridge: cdns-mhdp8546: Add support for no-hpd Jayesh Choudhary

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=5cae1874-9c10-a909-906c-160ce3f91286@ti.com \
    --to=j-choudhary@ti.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=a-bhatia1@ti.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=andrzej.hajda@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=javierm@redhat.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lyude@redhat.com \
    --cc=neil.armstrong@linaro.org \
    --cc=r-ravikumar@ti.com \
    --cc=rfoss@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=sjakhade@cadence.com \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=tzimmermann@suse.de \
    --cc=ville.syrjala@linux.intel.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;
as well as URLs for NNTP newsgroup(s).