From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org, Felipe Balbi <balbi@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Roger Quadros <rogerq@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH 1/2] dt-bindings: usb: Add documentation for AM62 USB Wrapper module
Date: Wed, 23 Mar 2022 10:21:40 +0100 [thread overview]
Message-ID: <65609100-3664-11e3-f229-c203e52888f0@kernel.org> (raw)
In-Reply-To: <8b8dcc55-dda8-0715-ccff-22fbe84ff18a@ti.com>
On 23/03/2022 10:17, Aswath Govindraju wrote:
> Hi Krzysztof,
(...)
>>> +
>>> + ti,syscon-phy-pll-refclk:
>>> + $ref: /schemas/types.yaml#/definitions/phandle-array
>>> + items:
>>> + - items:
>>> + - description: Phandle to the SYSCON entry
>>> + - description: USB phy control register offset within SYSCON
>>> + description: Specifier for configuring frequency of ref clock input.
>>
>> This is a bit strange. The ref clock is the "ref" input clock, right? In
>> such case use clk_set_rate()... Using syscon for managing clocks is not
>> the proper way.
>>
>
> The syscon property is not being used to set the ref clock frequency but
> is rather being used to indicate the input clock frequency for USB PHY
> operation. I think the description seems be misleading. I will update it
> in the respin, to reflect the above description.
Yes, please, it will help.
>
>> Plus all the issues pointed out by Roger.
>>
>>> +
>>> + '#address-cells':
>>> + const: 2
>>> +
>>> + '#size-cells':
>>> + const: 2
>>
>> No children allowed?
>>
>> I understand this is a wrapper, which explains why you do not include
>> usb-hcd.yaml schema. But since it is a wrapper, what is it wrapping?
>>
>
> Yes, there is a child node, which would be the dwc3-contoller node.
> Would adding the child node too in the example help capture this better?
Yes, please, because then you will also spot errors when running
dt_binding_check.
You need patternProperties for "^usb@[0-9a-f]+$" referencing Synopsys
schema. Something like:
Documentation/devicetree/bindings/usb/samsung,exynos-dwc3.yaml
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-23 9:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 5:35 [PATCH 0/2] AM62: Add support for AM62 USB wrapper driver Aswath Govindraju
2022-03-23 5:35 ` [PATCH 1/2] dt-bindings: usb: Add documentation for AM62 USB Wrapper module Aswath Govindraju
2022-03-23 6:17 ` Roger Quadros
2022-03-23 6:19 ` Roger Quadros
2022-03-23 7:54 ` Roger Quadros
2022-03-23 9:05 ` Krzysztof Kozlowski
2022-03-23 9:17 ` Aswath Govindraju
2022-03-23 9:21 ` Krzysztof Kozlowski [this message]
2022-03-23 5:35 ` [PATCH 2/2] drivers: usb: dwc3: Add AM62 USB wrapper driver Aswath Govindraju
2022-03-23 9:33 ` kernel test robot
2022-03-23 12:17 ` 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=65609100-3664-11e3-f229-c203e52888f0@kernel.org \
--to=krzk@kernel.org \
--cc=a-govindraju@ti.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rogerq@kernel.org \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).