From: Heiko Stuebner <heiko@sntech.de>
To: Heiko Stuebner <heiko@sntech.de>
Cc: mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 0/3] Correctly implemet the usb480m clock on rk3036
Date: Thu, 8 May 2025 20:30:45 +0200 [thread overview]
Message-ID: <174672902827.1927548.11178117072822465092.b4-ty@sntech.de> (raw)
In-Reply-To: <20250503202532.992033-1-heiko@sntech.de>
On Sat, 03 May 2025 22:25:28 +0200, Heiko Stuebner wrote:
> In the original clock driver the usb480m clock was "stubbed" as a fixed
> factor clock, but instead it actually does have a mux-bit to switch
> between the 24MHz osciallator and the actual 480MHz clock supplied
> from the usb-phy.
>
> Both the register layout, as well as the implementation is very similar
> to the rk3128, which seems to be some sort of cousin to the rk3036.
>
> [...]
Applied, thanks!
[1/3] dt-bindings: clock: rk3036: add SCLK_USB480M clock-id
commit: 6e06b641ca96c232e0b13f9b44b118742986bcd5
[2/3] clk: rockchip: rk3036: fix implementation of usb480m clock mux
commit: 897adaf536ab01f130ce0b53a635a592733c0f24
[3/3] clk: rockchip: rk3036: mark ddrphy as critical
commit: 596a977b34a722c00245801a5774aa79cec4e81d
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
prev parent reply other threads:[~2025-05-08 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 20:25 [PATCH 0/3] Correctly implemet the usb480m clock on rk3036 Heiko Stuebner
2025-05-03 20:25 ` [PATCH 1/3] dt-bindings: clock: rk3036: add SCLK_USB480M clock-id Heiko Stuebner
2025-05-06 16:21 ` Conor Dooley
2025-05-03 20:25 ` [PATCH 2/3] clk: rockchip: rk3036: fix implementation of usb480m clock mux Heiko Stuebner
2025-05-03 20:25 ` [PATCH 3/3] clk: rockchip: rk3036: mark ddrphy as critical Heiko Stuebner
2025-05-08 18:30 ` Heiko Stuebner [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=174672902827.1927548.11178117072822465092.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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