From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Prashant Malani <pmalani@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
bleung@chromium.org, swboyd@chromium.org,
heikki.krogerus@linux.intel.com,
"Andrzej Hajda" <andrzej.hajda@intel.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@linux.ie>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Hsin-Yi Wang" <hsinyi@chromium.org>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Jonas Karlman" <jonas@kwiboo.se>,
"José Expósito" <jose.exposito89@gmail.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Maxime Ripard" <maxime@cerno.tech>,
"Neil Armstrong" <narmstrong@baylibre.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Pin-Yen Lin" <treapking@chromium.org>,
"Robert Foss" <robert.foss@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Sam Ravnborg" <sam@ravnborg.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Xin Ji" <xji@analogixsemi.com>
Subject: Re: [PATCH 4/7] dt-bindings: drm/bridge: anx7625: Add mode-switch support
Date: Thu, 9 Jun 2022 08:41:44 +0200 [thread overview]
Message-ID: <fac58827-5b82-81a2-e782-99056180c0ed@linaro.org> (raw)
In-Reply-To: <CACeCKaeHocnAuY5D-oVt1fhgRGkNT014RcK3JSe6piKoXNtKCQ@mail.gmail.com>
On 08/06/2022 23:56, Prashant Malani wrote:
> On Wed, Jun 8, 2022 at 10:08 AM Prashant Malani <pmalani@chromium.org> wrote:
>>
>> Hi Krzysztof,
>>
>> Thank you for looking at the patch.
>>
>> On Jun 08 11:24, Krzysztof Kozlowski wrote:
>>> On 07/06/2022 21:00, Prashant Malani wrote:
>>>> Analogix 7625 can be used in systems to switch USB Type-C DisplayPort
>>>> alternate mode lane traffic between 2 Type-C ports.
>>>>
>>>> Update the binding to accommodate this usage by introducing a switch
>>>> property.
>>>>
>>>> Signed-off-by: Prashant Malani <pmalani@chromium.org>
>>>> ---
>>>> .../display/bridge/analogix,anx7625.yaml | 56 +++++++++++++++++++
>>>> 1 file changed, 56 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml b/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml
>>>> index 35a48515836e..7e1f655ddfcc 100644
>>>> --- a/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml
>>>> +++ b/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml
>>>> @@ -105,6 +105,26 @@ properties:
>>>> - port@0
>>>> - port@1
>>>>
>>>> + switches:
>>>> + type: object
>>>> + description: Set of switches controlling DisplayPort traffic on
>>>> + outgoing RX/TX lanes to Type C ports.
>>>> +
>>>> + properties:
>>>> + switch:
>>>
>>> You allow only one switch with such schema, so no need for "switches"...
>>
>> See below comment (summary: we'd like to allow 1 or 2 switches).
>>>
>>>> + $ref: /schemas/usb/typec-switch.yaml#
>>>> + maxItems: 2
>>>
>>> Are you sure this works? what are you limiting here with maxItems? I
>>> think you wanted patternProperties...
>>
>> Yeah, I might not have used the DT syntax correctly here.
>> What I'm aiming for is:
>> "switches" should can contain 1 or 2 "switch" nodes.
>> 2 is the maximum (limitation of the hardware).
>>
>>>
>>>> +
>>>> + properties:
>>>> + reg:
>>>> + maxItems: 1
>>>> +
>>>> + required:
>>>> + - reg
>>>> +
>>>> + required:
>>>> + - switch@0
>>>
>>> This does not match the property.
>>>
>>> You also need unevaluatedProperties:false
>>
>> Ack, will update this in the next version.
>
> Actually, could you kindly clarify which of the two needs this?
> "switches" or "switch" ?
> I interpreted "switch" as requiring it, but I thought it better to confirm.
Depends what do you want to have there. If two properties called
"switch", then "switches" is ok. However old code had only one property
thus switches with maximum one switch is a bit weird.
Looking at example you wanted to switch@[01], so you need to use
patternProperties.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-06-09 6:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 19:00 [PATCH 0/7] usb: typec: Introduce typec-switch binding Prashant Malani
2022-06-07 19:00 ` [PATCH 1/7] usb: typec: mux: Allow muxes to specify mode-switch Prashant Malani
2022-06-07 19:00 ` [PATCH 2/7] usb: typec: mux: Add CONFIG guards for functions Prashant Malani
2022-06-08 20:13 ` Prashant Malani
2022-06-07 19:00 ` [PATCH 3/7] dt-bindings: usb: Add Type-C switch binding Prashant Malani
2022-06-08 9:18 ` Krzysztof Kozlowski
2022-06-08 9:21 ` Krzysztof Kozlowski
2022-06-08 17:15 ` Prashant Malani
2022-06-09 6:43 ` Krzysztof Kozlowski
2022-06-07 19:00 ` [PATCH 4/7] dt-bindings: drm/bridge: anx7625: Add mode-switch support Prashant Malani
2022-06-08 9:24 ` Krzysztof Kozlowski
2022-06-08 17:08 ` Prashant Malani
2022-06-08 21:56 ` Prashant Malani
2022-06-09 6:41 ` Krzysztof Kozlowski [this message]
2022-06-09 18:24 ` Prashant Malani
2022-06-07 19:00 ` [PATCH 5/7] drm/bridge: anx7625: Register number of Type C switches Prashant Malani
2022-06-07 19:00 ` [PATCH 6/7] drm/bridge: anx7625: Register Type-C mode switches Prashant Malani
2022-06-08 18:14 ` kernel test robot
2022-06-08 18:35 ` kernel test robot
2022-06-08 22:31 ` kernel test robot
2022-06-07 19:00 ` [PATCH 7/7] drm/bridge: anx7625: Add typec_mux_set callback function Prashant Malani
2022-06-09 0:14 ` kernel test robot
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=fac58827-5b82-81a2-e782-99056180c0ed@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=andrzej.hajda@intel.com \
--cc=bleung@chromium.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=hsinyi@chromium.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=jose.exposito89@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=narmstrong@baylibre.com \
--cc=nfraprado@collabora.com \
--cc=pmalani@chromium.org \
--cc=robert.foss@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=swboyd@chromium.org \
--cc=treapking@chromium.org \
--cc=tzimmermann@suse.de \
--cc=xji@analogixsemi.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