From: Greg KH <gregkh@linuxfoundation.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Felipe Balbi <balbi@kernel.org>,
linux-usb@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org,
Kathiravan T <kathirav@codeaurora.org>,
Balaji Prakash J <bjagadee@codeaurora.org>
Subject: Re: [PATCH] usb: dwc3: reference clock configuration
Date: Mon, 8 Feb 2021 07:56:58 +0100 [thread overview]
Message-ID: <YCDgupJbubjnu2+v@kroah.com> (raw)
In-Reply-To: <8fc38cb73afd31269f1ea0c28e73604c53cebb17.1612764006.git.baruch@tkos.co.il>
On Mon, Feb 08, 2021 at 08:00:06AM +0200, Baruch Siach wrote:
> From: Balaji Prakash J <bjagadee@codeaurora.org>
>
> DWC_USB3_GFLADJ and DWC_USB3_GUCTL registers contain options
> to control the behavior of controller with respect to SOF and ITP.
> The reset values of these registers are aligned for 19.2 MHz
> reference clock source. This change will add option to override
> these settings for reference clock other than 19.2 MHz
>
> Tested on IPQ6018 SoC based CP01 board with 24MHz reference clock.
>
> Signed-off-by: Balaji Prakash J <bjagadee@codeaurora.org>
> [ baruch: mention tested hardware ]
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> .../devicetree/bindings/usb/dwc3.txt | 5 ++
Bindings should be split into a separate patch (1/2) so that the DT
maintainers can review it easier.
Also, always run checkpatch on your submissions before sending them out.
thanks,
greg k-h
next prev parent reply other threads:[~2021-02-08 6:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 6:00 [PATCH] usb: dwc3: reference clock configuration Baruch Siach
2021-02-08 6:56 ` Greg KH [this message]
2021-02-08 18:26 ` Bjorn Andersson
2021-02-10 6:10 ` Baruch Siach
2021-02-15 16:58 ` Kathiravan T
2021-02-25 16:47 ` Kathiravan T
2021-03-24 8:14 ` Jack Pham
2021-03-31 0:52 ` Thinh Nguyen
2021-03-31 1:17 ` Thinh Nguyen
2021-04-07 11:56 ` Kathiravan T
2021-04-08 1:53 ` Thinh Nguyen
2021-04-08 2:23 ` Bjorn Andersson
2021-04-08 2:50 ` Thinh Nguyen
2021-04-08 2:54 ` Thinh Nguyen
2021-04-08 3:15 ` Bjorn Andersson
2021-04-08 3:39 ` Thinh Nguyen
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=YCDgupJbubjnu2+v@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=agross@kernel.org \
--cc=balbi@kernel.org \
--cc=baruch@tkos.co.il \
--cc=bjagadee@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=kathirav@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.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).