From: <Claudiu.Beznea@microchip.com>
To: <michael@walle.cc>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] ARM: dts: lan966x: add clock gating register
Date: Mon, 11 Jul 2022 07:15:11 +0000 [thread overview]
Message-ID: <7ee463db-3cb5-c340-ac1d-1dfcd2b87dcd@microchip.com> (raw)
In-Reply-To: <20220707132500.1708020-1-michael@walle.cc>
On 07.07.2022 16:24, Michael Walle wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> The clock controller supports an optional clock gating register. This is
> necessary to expose the USB device clock, for example. Add it.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
Applied to at91-dt, thanks!
> ---
> changes since v1:
> - none
>
> arch/arm/boot/dts/lan966x.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/lan966x.dtsi b/arch/arm/boot/dts/lan966x.dtsi
> index 57cb67a180ec..bc102677ff91 100644
> --- a/arch/arm/boot/dts/lan966x.dtsi
> +++ b/arch/arm/boot/dts/lan966x.dtsi
> @@ -65,7 +65,7 @@ clks: clock-controller@e00c00a8 {
> #clock-cells = <1>;
> clocks = <&cpu_clk>, <&ddr_clk>, <&sys_clk>;
> clock-names = "cpu", "ddr", "sys";
> - reg = <0xe00c00a8 0x38>;
> + reg = <0xe00c00a8 0x38>, <0xe00c02cc 0x4>;
> };
>
> timer {
> --
> 2.30.2
>
next prev parent reply other threads:[~2022-07-11 7:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 13:24 [PATCH v2 1/2] ARM: dts: lan966x: add clock gating register Michael Walle
2022-07-07 13:25 ` [PATCH v2 2/2] ARM: dts: kswitch-d10: enable the USB device port Michael Walle
2022-07-11 7:15 ` Claudiu.Beznea
2022-07-11 7:15 ` Claudiu.Beznea [this message]
2022-07-12 7:22 ` [PATCH v2 1/2] ARM: dts: lan966x: add clock gating register Claudiu.Beznea
2022-07-19 13:24 ` Michael Walle
2022-07-20 6:52 ` Claudiu.Beznea
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=7ee463db-3cb5-c340-ac1d-1dfcd2b87dcd@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--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).