[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2b2f268-182a-5ba4-2541-f0a401eda1c8@linaro.org>
Date: Tue, 29 Aug 2023 09:42:27 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Wesley Cheng <quic_wcheng@...cinc.com>,
Rob Herring <robh@...nel.org>
Cc: srinivas.kandagatla@...aro.org, mathias.nyman@...el.com,
perex@...ex.cz, broonie@...nel.org, lgirdwood@...il.com,
krzysztof.kozlowski+dt@...aro.org, agross@...nel.org,
Thinh.Nguyen@...opsys.com, bgoswami@...cinc.com,
andersson@...nel.org, gregkh@...uxfoundation.org, tiwai@...e.com,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
alsa-devel@...a-project.org, devicetree@...r.kernel.org,
linux-usb@...r.kernel.org, quic_jackp@...cinc.com,
quic_plai@...cinc.com
Subject: Re: [PATCH v3 11/28] dt-bindings: usb: dwc3: Add
snps,num-hc-interrupters definition
On 29/08/2023 09:19, Wesley Cheng wrote:
>>>
>>> This is a XHCI feature, but the DWC3 design is built in a way that DWC3
>>> host initializes the XHCI device and populates the properties associated
>>> to XHCI dev.
>>
>> You speak about driver now, not bindings. If driver has limitations,
>> change it. Not really problem of bindings.
>>
>
> Its the limitation of the HW. Depending on how the SNPS DWC3 controller
> was implemented the vendor it can support less than the value mentioned
> in the Synopsys databook.
Then what is "XHCI dev"? A Linux device? Then a driver topic. What is
"populates the properties" - what or whose properties? Of Linux device?
Then a driver topic...
Best regards,
Krzysztof
Powered by blists - more mailing lists