From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
hminas@synopsys.com, gregkh@linuxfoundation.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
alexandre.torgue@foss.st.com
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
amelie.delaunay@foss.st.com
Subject: Re: [PATCH v2 2/4] dt-bindings: usb: dwc2: add utmi optional clock
Date: Fri, 14 Apr 2023 23:15:28 +0200 [thread overview]
Message-ID: <add2ccfa-d811-d76b-342f-a2204f7e87b0@linaro.org> (raw)
In-Reply-To: <20230414084137.1050487-3-fabrice.gasnier@foss.st.com>
On 14/04/2023 10:41, Fabrice Gasnier wrote:
> utmi clock is typically provided by PHY output. Add this optional clock,
> as the core could use other clocks depending on the SoC where it's used.
> This is needed on stm32mp15, when using the integrated full-speed PHY.
>
> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-04-14 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 8:41 [PATCH v2 0/4] usb: dwc2: add optional clock used on stm32mp15 Fabrice Gasnier
2023-04-14 8:41 ` [PATCH v2 1/4] usb: dwc2: improve error handling in __dwc2_lowlevel_hw_enable Fabrice Gasnier
2023-04-18 5:05 ` Minas Harutyunyan
2023-04-14 8:41 ` [PATCH v2 2/4] dt-bindings: usb: dwc2: add utmi optional clock Fabrice Gasnier
2023-04-14 21:15 ` Krzysztof Kozlowski [this message]
2023-04-14 8:41 ` [PATCH v2 3/4] usb: dwc2: platform: add support for " Fabrice Gasnier
2023-04-18 5:06 ` Minas Harutyunyan
2023-04-14 8:41 ` [PATCH v2 4/4] ARM: dts: stm32: add USB OTG UTMI clock on stm32mp151 Fabrice Gasnier
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=add2ccfa-d811-d76b-342f-a2204f7e87b0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--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).