From: Rob Herring <robh@kernel.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
linux-usb@vger.kernel.org, Felipe Balbi <balbi@kernel.org>,
Andy Gross <agross@kernel.org>,
Balaji Prakash J <bjagadee@codeaurora.org>,
Robert Marko <robert.marko@sartura.hr>,
Rob Herring <robh+dt@kernel.org>,
Kathiravan T <kathirav@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Jack Pham <jackp@codeaurora.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 1/4] dt-bindings: usb: dwc3: add reference clock period
Date: Tue, 31 Aug 2021 20:37:45 -0500 [thread overview]
Message-ID: <YS7ZafoBpPC/+j2k@robh.at.kernel.org> (raw)
In-Reply-To: <f5ea5bc3664a98a684ad4b699a1ac610e847176f.1630389452.git.baruch@tkos.co.il>
On Tue, 31 Aug 2021 08:57:29 +0300, Baruch Siach wrote:
> Document the snps,ref-clock-period-ns property that describes reference
> clock period when it deviates from the default set value.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> v2:
>
> Address comments from Rob Herring:
>
> Use standard unit suffix
>
> Reword description
> ---
> Documentation/devicetree/bindings/usb/snps,dwc3.yaml | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2021-09-01 1:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 5:57 [PATCH v3 1/4] dt-bindings: usb: dwc3: add reference clock period Baruch Siach
2021-08-31 5:57 ` [PATCH v3 2/4] usb: dwc3: reference clock period configuration Baruch Siach
2021-08-31 7:27 ` Felipe Balbi
2021-08-31 5:57 ` [PATCH v3 3/4] dt-bindings: usb: qcom,dwc3: add binding for IPQ6018 Baruch Siach
2021-08-31 5:57 ` [PATCH v3 4/4] arm64: qcom: ipq6018: add usb3 DT description Baruch Siach
2021-08-31 7:27 ` [PATCH v3 1/4] dt-bindings: usb: dwc3: add reference clock period Felipe Balbi
2021-09-01 1:37 ` Rob Herring [this message]
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=YS7ZafoBpPC/+j2k@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=agross@kernel.org \
--cc=balbi@kernel.org \
--cc=baruch@tkos.co.il \
--cc=bjagadee@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jackp@codeaurora.org \
--cc=kathirav@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robert.marko@sartura.hr \
--cc=robh+dt@kernel.org \
/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).