Message ID | 20230405142440.191939-2-j-choudhary@ti.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:b0ea:0:b0:3b6:4342:cba0 with SMTP id b10csp357838vqo; Wed, 5 Apr 2023 07:39:30 -0700 (PDT) X-Google-Smtp-Source: AKy350aucWUxhTiJAyrmcs88kGCAj7o/pPSNubUui+LXY/mVszf2xtK3ZbALPIpfBrvjNPeXS+ka X-Received: by 2002:a05:6402:1ad1:b0:4fb:5089:6e01 with SMTP id ba17-20020a0564021ad100b004fb50896e01mr1958186edb.6.1680705570374; Wed, 05 Apr 2023 07:39:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680705570; cv=none; d=google.com; s=arc-20160816; b=OtX0h/97nSYJiD/RpRWF0kERQ81PVIsOxyXvzeomTPpvvvq/rHxDSbvqQgKLgr90TY DFOpCxbYw6AWdXW+bzOdV3M3HTlYWGa2jeSwWVd8R4rUZHSkjbdrWAj/NJbDT5kMsUMU F/iO4X9CyirIpe75PIzUVjaGmCHp5k0su07bmSU79h75B3RcnwRGAP3uLmAcxMGNrczy 3EYFvh3MRJJ6d7zGbQ0GdkH76h7bI+qQDqUT9J4RCf7BPiT7pHwA2t3HPMPcT79FyrO4 F0udYKYmz8d7e1BIXeYosZZ9v2YAiZWexJ2S30o+o+dH9Eag98yoS3LVJZFqv0U3B270 bYMw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=qDO37Rl2u94OwUVPnEAZxBPCa+75piDWj4gv5a2V2Zc=; b=S0uZ5ucz6+xiFpdejO+XKZ6BrKtQhun+/RxrRseGByWne/IVtCAZq/yTwIjedxtVOk LPJ9ccLZbxfPY+EF3yBicjaNNSKazOxSjE8yQf+34sGnOWh98CBjDNm9RR+Qm7ITpGXJ gK9Cp6AIywnoIzAiXPXK4Aewo4O6oN6FPtGs+cxkCeLO+dVTGxvGeDHGrXJk928dlpSw ZNv4bVT5N32sngRwZbFl8pGx5hvALK3cCWvQIJU7hwb9a0Oi4TSNQordqEBrOH8Kzett tggsjOrS4ML0AE7I+uvR/LBk8CzMEE8jubqQRCWo2PMbGexoUOHoidmfH8T9R34PexVB 4ssw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=fryHPY1m; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id p21-20020a056402075500b004fd298d4b3esi4666106edy.373.2023.04.05.07.39.06; Wed, 05 Apr 2023 07:39:30 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=fryHPY1m; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238300AbjDEOZZ (ORCPT <rfc822;lkml4gm@gmail.com> + 99 others); Wed, 5 Apr 2023 10:25:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54514 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238280AbjDEOZV (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 5 Apr 2023 10:25:21 -0400 Received: from lelv0143.ext.ti.com (lelv0143.ext.ti.com [198.47.23.248]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 993564EFD; Wed, 5 Apr 2023 07:25:13 -0700 (PDT) Received: from fllv0034.itg.ti.com ([10.64.40.246]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 335EOhSK059451; Wed, 5 Apr 2023 09:24:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1680704683; bh=qDO37Rl2u94OwUVPnEAZxBPCa+75piDWj4gv5a2V2Zc=; h=From:To:CC:Subject:Date:In-Reply-To:References; b=fryHPY1mKzdLY30aiXYYZCvvFh7EQQgCwL3LiFwtyzgwyq+wJ14EzQvP+dzhWrGb/ VRB9i0mIT4ZgujImeAPThTeFi5LDvAxZkIvIFk+BXL0Y/wXXrnWmFjmxiggCkZhxyc E4NnR9mZ8myUIwSTVCfqaeDxY/c374a4CWz1hTHk= Received: from DLEE109.ent.ti.com (dlee109.ent.ti.com [157.170.170.41]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 335EOhTO064579 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 5 Apr 2023 09:24:43 -0500 Received: from DLEE110.ent.ti.com (157.170.170.21) by DLEE109.ent.ti.com (157.170.170.41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.16; Wed, 5 Apr 2023 09:24:43 -0500 Received: from lelv0326.itg.ti.com (10.180.67.84) by DLEE110.ent.ti.com (157.170.170.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.16 via Frontend Transport; Wed, 5 Apr 2023 09:24:43 -0500 Received: from localhost (ileaxei01-snat2.itg.ti.com [10.180.69.6]) by lelv0326.itg.ti.com (8.15.2/8.15.2) with ESMTP id 335EOgNt014784; Wed, 5 Apr 2023 09:24:43 -0500 From: Jayesh Choudhary <j-choudhary@ti.com> To: <dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <krzysztof.kozlowski@linaro.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>, <j-choudhary@ti.com> Subject: [PATCH v2 1/2] dt-bindings: drm/bridge: Add no-hpd property Date: Wed, 5 Apr 2023 19:54:39 +0530 Message-ID: <20230405142440.191939-2-j-choudhary@ti.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20230405142440.191939-1-j-choudhary@ti.com> References: <20230405142440.191939-1-j-choudhary@ti.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-Spam-Status: No, score=-2.5 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_PASS, SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1762347524162289015?= X-GMAIL-MSGID: =?utf-8?q?1762347524162289015?= |
Series |
"no-hpd" support in CDNS DP bridge driver
|
|
Commit Message
Jayesh Choudhary
April 5, 2023, 2:24 p.m. UTC
From: Rahul T R <r-ravikumar@ti.com> 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, we need an indication for no-hpd, using which we can bypass the hpd detection and instead use the auxiliary channels connected to the DP connector to confirm the connection. So add no-hpd property to the bindings, to disable hpd when not connected or unusable. Signed-off-by: Rahul T R <r-ravikumar@ti.com> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com> --- .../devicetree/bindings/display/bridge/cdns,mhdp8546.yaml | 6 ++++++ 1 file changed, 6 insertions(+)
Comments
Hi Jayesh, Thank you for the patch. On Wed, Apr 05, 2023 at 07:54:39PM +0530, Jayesh Choudhary wrote: > From: Rahul T R <r-ravikumar@ti.com> > > 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, we need an indication for > no-hpd, using which we can bypass the hpd detection and instead use the > auxiliary channels connected to the DP connector to confirm the > connection. > So add no-hpd property to the bindings, to disable hpd when not > connected or unusable. > > Signed-off-by: Rahul T R <r-ravikumar@ti.com> > Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com> > --- > .../devicetree/bindings/display/bridge/cdns,mhdp8546.yaml | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml > index c2b369456e4e..3a6c6d837593 100644 > --- a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml > +++ b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml > @@ -57,6 +57,12 @@ properties: > interrupts: > maxItems: 1 > > + cdns,no-hpd: > + type: boolean > + description: > + Set if the HPD line on the bridge isn't hooked up to anything or is > + otherwise unusable. I'm fine with the non connected part, but concerned with "otherwise unusable". It's very vague and could thus be abused. Do you have particular use cases in mind for this ? If so, restricting this to those use cases, or at least giving examples, would help. > + > ports: > $ref: /schemas/graph.yaml#/properties/ports >
On 05/04/2023 16:24, Jayesh Choudhary wrote: > From: Rahul T R <r-ravikumar@ti.com> > > 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, we need an indication for > no-hpd, using which we can bypass the hpd detection and instead use the > auxiliary channels connected to the DP connector to confirm the > connection. > So add no-hpd property to the bindings, to disable hpd when not > connected or unusable. Your subject prefixes miss device specific part. You do not add no-hpd to all bridges. It's also not drm. It is a display directory. > > Signed-off-by: Rahul T R <r-ravikumar@ti.com> > Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com> > --- > .../devicetree/bindings/display/bridge/cdns,mhdp8546.yaml | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml > index c2b369456e4e..3a6c6d837593 100644 > --- a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml > +++ b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml > @@ -57,6 +57,12 @@ properties: > interrupts: > maxItems: 1 > > + cdns,no-hpd: No improvements - use existing no-hpd name. Best regards, Krzysztof
On 06/04/23 07:10, Laurent Pinchart wrote: > Hi Jayesh, > > Thank you for the patch. > > On Wed, Apr 05, 2023 at 07:54:39PM +0530, Jayesh Choudhary wrote: >> From: Rahul T R <r-ravikumar@ti.com> >> >> 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, we need an indication for >> no-hpd, using which we can bypass the hpd detection and instead use the >> auxiliary channels connected to the DP connector to confirm the >> connection. >> So add no-hpd property to the bindings, to disable hpd when not >> connected or unusable. >> >> Signed-off-by: Rahul T R <r-ravikumar@ti.com> >> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com> >> --- >> .../devicetree/bindings/display/bridge/cdns,mhdp8546.yaml | 6 ++++++ >> 1 file changed, 6 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml >> index c2b369456e4e..3a6c6d837593 100644 >> --- a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml >> +++ b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml >> @@ -57,6 +57,12 @@ properties: >> interrupts: >> maxItems: 1 >> >> + cdns,no-hpd: >> + type: boolean >> + description: >> + Set if the HPD line on the bridge isn't hooked up to anything or is >> + otherwise unusable. > > I'm fine with the non connected part, but concerned with "otherwise > unusable". It's very vague and could thus be abused. Do you have > particular use cases in mind for this ? If so, restricting this to those > use cases, or at least giving examples, would help. Okay. Will do that in next version. Thanks. > >> + >> ports: >> $ref: /schemas/graph.yaml#/properties/ports >> >
On 11/04/23 11:36, Krzysztof Kozlowski wrote: > On 05/04/2023 16:24, Jayesh Choudhary wrote: >> From: Rahul T R <r-ravikumar@ti.com> >> >> 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, we need an indication for >> no-hpd, using which we can bypass the hpd detection and instead use the >> auxiliary channels connected to the DP connector to confirm the >> connection. >> So add no-hpd property to the bindings, to disable hpd when not >> connected or unusable. > > Your subject prefixes miss device specific part. You do not add no-hpd > to all bridges. > > It's also not drm. It is a display directory. Sorry messed the commit heading. Will fix it. > >> >> Signed-off-by: Rahul T R <r-ravikumar@ti.com> >> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com> >> --- >> .../devicetree/bindings/display/bridge/cdns,mhdp8546.yaml | 6 ++++++ >> 1 file changed, 6 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml >> index c2b369456e4e..3a6c6d837593 100644 >> --- a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml >> +++ b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml >> @@ -57,6 +57,12 @@ properties: >> interrupts: >> maxItems: 1 >> >> + cdns,no-hpd: > > No improvements - use existing no-hpd name. > > Okay will change it to "no-hpd" > > Best regards, > Krzysztof >
diff --git a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml index c2b369456e4e..3a6c6d837593 100644 --- a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml +++ b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml @@ -57,6 +57,12 @@ properties: interrupts: maxItems: 1 + cdns,no-hpd: + type: boolean + description: + Set if the HPD line on the bridge isn't hooked up to anything or is + otherwise unusable. + ports: $ref: /schemas/graph.yaml#/properties/ports