From: gregory.clement@bootlin.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: dts: marvell: armada-cp110: Add registers clock for sata node
Date: Tue, 27 Feb 2018 17:48:17 +0100 [thread overview]
Message-ID: <87muzujs4u.fsf@bootlin.com> (raw)
In-Reply-To: <20180215134423.11800-1-gregory.clement@bootlin.com> (Gregory CLEMENT's message of "Thu, 15 Feb 2018 14:44:23 +0100")
Hi,
On jeu., f?vr. 15 2018, Gregory CLEMENT <gregory.clement@bootlin.com> wrote:
> This extra clock is needed to access the registers of the AHCI SATA
> controller used on the Armada 7K/8K SoCs.
>
> The ahci drivers was already designed to support up to 5 clocks so there
> is only need to update the device tree to use it. It was not noticed
> until now because of wrong assumption in the clock drivers, but as this
> IP really needs 2 clocks, we had to declare both of them.
>
Applied on mvebu/dt64
Gregory
> Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
> ---
> arch/arm64/boot/dts/marvell/armada-cp110.dtsi | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/marvell/armada-cp110.dtsi b/arch/arm64/boot/dts/marvell/armada-cp110.dtsi
> index 50038434dd53..b8cf1497dc22 100644
> --- a/arch/arm64/boot/dts/marvell/armada-cp110.dtsi
> +++ b/arch/arm64/boot/dts/marvell/armada-cp110.dtsi
> @@ -236,7 +236,8 @@
> "generic-ahci";
> reg = <0x540000 0x30000>;
> interrupts = <ICU_GRP_NSR 107 IRQ_TYPE_LEVEL_HIGH>;
> - clocks = <&CP110_LABEL(clk) 1 15>;
> + clocks = <&CP110_LABEL(clk) 1 15>,
> + <&CP110_LABEL(clk) 1 16>;
> status = "disabled";
> };
>
> --
> 2.15.1
>
--
Gregory Clement, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-02-27 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 13:44 [PATCH] ARM64: dts: marvell: armada-cp110: Add registers clock for sata node Gregory CLEMENT
2018-02-27 16:48 ` Gregory CLEMENT [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=87muzujs4u.fsf@bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.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).