[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4b690859-be5a-c331-8243-b875136d4807@linaro.org>
Date: Fri, 28 Apr 2023 15:27:04 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Shazad Hussain <quic_shazhuss@...cinc.com>, agross@...nel.org,
andersson@...nel.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org
Cc: dmitry.baryshkov@...aro.org, athierry@...hat.com, robh@...nel.org,
konrad.dybcio@...aro.org, Vinod Koul <vkoul@...nel.org>,
Kishon Vijay Abraham I <kishon@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Wesley Cheng <quic_wcheng@...cinc.com>,
linux-arm-msm@...r.kernel.org, linux-phy@...ts.infradead.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-usb@...r.kernel.org
Subject: Re: [PATCH v2 1/6] dt-bindings: usb: qcom,dwc3: Add bindings for
SA8775P
On 28/04/2023 15:08, Shazad Hussain wrote:
> Add the compatible string for SA8775P SoC from Qualcomm.
>
> Signed-off-by: Shazad Hussain <quic_shazhuss@...cinc.com>
> ---
(...)
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - qcom,sa8775p-dwc3
> + then:
> + properties:
> + interrupts:
> + minItems: 3
> + maxItems: 4
> + interrupt-names:
> + minItems: 3
> + items:
> + - const: pwr_event
> + - const: dp_hs_phy_irq
> + - const: dm_hs_phy_irq
> + - const: ss_phy_irq
Why the last interrupt line is optional? Is it really optional?
Best regards,
Krzysztof
Powered by blists - more mailing lists