lkml.org 
[lkml]   [2020]   [Jan]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH v3 1/2] dt-bindings: usb: qcom,dwc3: Convert USB DWC3 bindings
Hi,

On Wed, Dec 25, 2019 at 9:56 PM Sandeep Maheswaram (Temp)
<sanm@codeaurora.org> wrote:
>
> Hi
>
> On 12/18/2019 12:44 AM, Doug Anderson wrote:
> > Hi,
> >
> > On Sun, Dec 15, 2019 at 9:40 PM Sandeep Maheswaram <sanm@codeaurora.org> wrote:
> >>
> >>
> >> + items:
> >> + - description: System Config NOC clock. Not present on "qcom,msm8996-dwc3" compatible.
> >> + - description: Master/Core clock, have to be >= 125 MHz for SS operation and >= 60MHz for HS operation
> > To make the grammer gooder, s/have/has/
> >
> >
> >> + - description: System bus AXI clock. Not present on "qcom,msm8996-dwc3" compatible.
> >> + - description: Mock utmi clock needed for ITP/SOF generation in host mode.Its frequency should be 19.2MHz.
> >> + - description: Sleep clock, used for wakeup when USB3 core goes into low power mode (U3).
> > * Please word wrap to ~80 chracters.
> > * As Stephen says, order matters. Please match order of old bindings
> > (and in clock-names)
> > * Please end each with a period.
>
> Regarding the order of clocks, If I change the order I am facing error
> in make dtbs_check
>
> linux-next/arch/arm64/boot/dts/qcom/sc7180-idp.dt.yaml: usb@a6f8800:
> clock-names:0: 'core' was expected
> linux-next/arch/arm64/boot/dts/qcom/sc7180-idp.dt.yaml: usb@a6f8800:
> clock-names:1: 'mock_utmi' was expected
> linux-next/arch/arm64/boot/dts/qcom/sc7180-idp.dt.yaml: usb@a6f8800:
> clock-names:2: 'sleep' was expected
> linux-next/arch/arm64/boot/dts/qcom/sc7180-idp.dt.yaml: usb@a6f8800:
> clock-names:3: 'cfg_noc' was expected
> linux-next/arch/arm64/boot/dts/qcom/sc7180-idp.dt.yaml: usb@a6f8800:
> clock-names:4: 'iface' was expected
>
> Need to modify in the sc7180.dtsi and sdm845.dtsi to avoid the error .
> Please let me know how to proceed.

Ick. OK, so I guess technically the old bindings didn't specify
order. It seems like it was implied that the required clocks should
come before the optional, but I guess it wasn't explicit...

Ugh, it gets even worse, at least for msm8996. It looks like things
are nicely consistent for all the new ones. They _all_ do:

"cfg_noc", "core", "iface", "mock_utmi", "sleep";

...but msm8996 is a mess. It looks to have two USB ports (usb2 and
usb3). Both ports have exactly the same compatible string listed, AKA
"qcom,msm8996-dwc3", "qcom,dwc3". ...but we don't seem to use
"clock-names" for either port and things seem jumbled. Specifically:

* USB3 port: actually has 6 clocks listed instead of 5 (but, on the
plus side, the first 5 match everyone else in ordering). The 6th
clock seems to be an extra PHY clock listed which seems wrong.

* USB2 port: has 5 clocks. Missing "iface" but has the extra "PHY"
clock. AKA listed order is: "cfg_noc", "core", "mock_utmi", "sleep",
extra PHY clock.


If I had to make a decision, I'd do this:

* For 8996, document exactly what's in the device tree.

* For everything except 8996, use the order that your current patch
has (AKA also document what's in device trees).

* Consider seeing if we can remove the "PHY" clock from the 8996
device tree. If you can, make it optional (but deprecated) to supply
it.


Probably something like this (UNTESTED) would work. Optionally you
could figure out how to be smarter and list 6 clocks for the PHY with
the node name "usb@6af8800" and 5 clocks for the PHY with the node
name "usb@76f8800", but I'm not sure it's worth it.


allOf:
- if:
properties:
compatible:
contains:
const: "qcom,msm8996-dwc3"
then:
anyOf:
- properties:
# For USB 3 port with node name usb@6af8800
clocks:
items:
- description: System Config NOC clock.
- description: Master/Core clock, has to be >= 125 MHz for
SS operation and >= 60MHz for HS operation.
- description: System bus AXI clock.
- description: Mock utmi clock needed for ITP/SOF
generation in host mode. Its frequency should be 19.2MHz.
- description: Sleep clock, used for wakeup when USB3 core
goes into low power mode (U3).
- description: PHY clock. ((Maybe optional? If so, set
minItems to 5))
- properties:
# For USB 2 port with node name usb@76f8800
clocks:
items:
- description: System Config NOC clock.
- description: Master/Core clock, has to be >= 60MHz.
- description: Mock utmi clock needed for ITP/SOF
generation in host mode. Its frequency should be 19.2MHz.
- description: Sleep clock, used for wakeup when USB3 core
goes into low power mode (U3).
- description: PHY clock. ((Maybe optional? If so, set
minItems to 4))
else:
properties:
clocks:
items:
- description: System Config NOC clock.
- description: Master/Core clock, has to be >= 125 MHz for
SS operation and >= 60MHz for HS operation.
- description: System bus AXI clock.
- description: Mock utmi clock needed for ITP/SOF generation
in host mode. Its frequency should be 19.2MHz.
- description: Sleep clock, used for wakeup when USB3 core
goes into low power mode (U3).
clock-names:
items:
- const: cfg_noc
- const: core
- const: iface
- const: mock_utmi
- const: sleep

NOTE: looking at the current Linux driver, it is very simplistic and
just enables all listed clocks in bulk. It never refers to clocks by
name.

-Doug

\
 
 \ /
  Last update: 2020-01-07 04:48    [W:0.063 / U:4.740 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site