From: Jack Pham <quic_jackp@quicinc.com>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bin Yang <yangbin@rock-chips.com>,
"Heiko Stuebner" <heiko@sntech.de>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Subject: Re: [PATCH v1 4/8] usb: dwc3: core: do not use 3.0 clock when operating in 2.0 mode
Date: Fri, 25 Feb 2022 09:16:01 -0800 [thread overview]
Message-ID: <20220225171601.GF13801@jackp-linux.qualcomm.com> (raw)
In-Reply-To: <20220225145432.422130-5-pgwipeout@gmail.com>
+Thinh
Hi Peter,
On Fri, Feb 25, 2022 at 09:54:27AM -0500, Peter Geis wrote:
> From: Bin Yang <yangbin@rock-chips.com>
>
> In the 3.0 device core, if the core is programmed to operate in
> 2.0 only, then setting the GUCTL1.DEV_FORCE_20_CLK_FOR_30_CLK makes
> the internal 2.0(utmi/ulpi) clock to be routed as the 3.0 (pipe)
> clock. Enabling this feature allows the pipe3 clock to be not-running
> when forcibly operating in 2.0 device mode.
>
> Signed-off-by: Bin Yang <yangbin@rock-chips.com>
> Signed-off-by: Peter Geis <pgwipeout@gmail.com>
> ---
> drivers/usb/dwc3/core.c | 4 ++++
> drivers/usb/dwc3/core.h | 1 +
> 2 files changed, 5 insertions(+)
>
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index 18adddfba3da..032d40794fae 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -1167,6 +1167,10 @@ static int dwc3_core_init(struct dwc3 *dwc)
> if (dwc->parkmode_disable_ss_quirk)
> reg |= DWC3_GUCTL1_PARKMODE_DISABLE_SS;
>
> + if (dwc->maximum_speed == USB_SPEED_HIGH ||
> + dwc->maximum_speed == USB_SPEED_FULL)
> + reg |= DWC3_GUCTL1_DEV_FORCE_20_CLK_FOR_30_CLK;
> +
I doubt this is applicable to all revisions of the DWC_usb3x IP cores?
For instance in the programming guide for DWC_usb31 1.90a bit 26 of
GUCTL1 is 'Reserved'. While I do see it in the DWC_usb3 databook,
table 4-8 entry "Remove pipe_clk mux for 2.0 mode?" mentions this
feature was only added in v2.90a.
So this setting at least needs a revision check to make sure we're not
causing unexpected behavior. Something like
DWC3_VER_IS_WITHIN(DWC3, 290A, ANY)
Jack
> dwc3_writel(dwc->regs, DWC3_GUCTL1, reg);
> }
>
> diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
> index eb9c1efced05..ea3ca04406bb 100644
> --- a/drivers/usb/dwc3/core.h
> +++ b/drivers/usb/dwc3/core.h
> @@ -259,6 +259,7 @@
> /* Global User Control 1 Register */
> #define DWC3_GUCTL1_DEV_DECOUPLE_L1L2_EVT BIT(31)
> #define DWC3_GUCTL1_TX_IPGAP_LINECHECK_DIS BIT(28)
> +#define DWC3_GUCTL1_DEV_FORCE_20_CLK_FOR_30_CLK BIT(26)
> #define DWC3_GUCTL1_DEV_L1_EXIT_BY_HW BIT(24)
> #define DWC3_GUCTL1_PARKMODE_DISABLE_SS BIT(17)
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-02-25 17:16 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 14:54 [PATCH v1 0/8] enable usb support on rk356x Peter Geis
2022-02-25 14:54 ` Peter Geis
2022-02-25 14:54 ` Peter Geis
2022-02-25 14:54 ` [PATCH v1 1/8] dt-bindings: soc: grf: add rk3566-pipe-grf compatible Peter Geis
2022-02-25 14:54 ` Peter Geis
2022-02-25 14:54 ` Peter Geis
2022-02-25 14:54 ` [PATCH v1 2/8] dt-bindings: usb: dwc3: add description for rk3568 Peter Geis
2022-02-25 14:54 ` Peter Geis
2022-02-25 14:54 ` Peter Geis
2022-02-25 16:07 ` Johan Jonker
2022-02-25 16:07 ` Johan Jonker
2022-02-25 16:07 ` Johan Jonker
2022-02-25 18:04 ` Peter Geis
2022-02-25 18:04 ` Peter Geis
2022-02-25 18:04 ` Peter Geis
2022-02-25 14:54 ` [PATCH v1 3/8] soc: rockchip: set dwc3 clock for rk3566 Peter Geis
2022-02-25 14:54 ` Peter Geis
2022-02-25 14:54 ` Peter Geis
2022-02-25 14:54 ` [PATCH v1 4/8] usb: dwc3: core: do not use 3.0 clock when operating in 2.0 mode Peter Geis
2022-02-25 17:16 ` Jack Pham [this message]
2022-02-25 17:55 ` Peter Geis
2022-02-25 14:54 ` [PATCH v1 5/8] usb: dwc3: reorder dwc-of-simple compatibles Peter Geis
2022-02-25 14:54 ` [PATCH v1 6/8] usb: dwc3: add rk3568 dwc3 support Peter Geis
2022-02-25 17:08 ` Michael Riesch
2022-02-25 17:55 ` Peter Geis
2022-02-25 14:54 ` [PATCH v1 7/8] arm64: dts: rockchip: add rk356x dwc3 usb3 nodes Peter Geis
2022-02-25 14:54 ` Peter Geis
2022-02-25 14:54 ` Peter Geis
2022-02-25 17:01 ` Michael Riesch
2022-02-25 17:01 ` Michael Riesch
2022-02-25 17:01 ` Michael Riesch
2022-02-25 17:59 ` Peter Geis
2022-02-25 17:59 ` Peter Geis
2022-02-25 17:59 ` Peter Geis
2022-02-25 18:25 ` Michael Riesch
2022-02-25 18:25 ` Michael Riesch
2022-02-25 18:25 ` Michael Riesch
2022-02-25 14:54 ` [PATCH v1 8/8] arm64: dts: rockchip: enable dwc3 on quartz64-a Peter Geis
2022-02-25 14:54 ` Peter Geis
2022-02-25 14:54 ` Peter Geis
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=20220225171601.GF13801@jackp-linux.qualcomm.com \
--to=quic_jackp@quicinc.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pgwipeout@gmail.com \
--cc=yangbin@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.