From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: devicetree@vger.kernel.org, "Jason Cooper" <jason@lakedaemon.net>,
"Andrew Lunn" <andrew@lunn.ch>,
"Antoine Tenart" <antoine.tenart@bootlin.com>,
"Mike Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Miquèl Raynal" <miquel.raynal@bootlin.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH v3 0/6] Add CPU clock support for Armada 7K/8K
Date: Wed, 13 Feb 2019 09:57:04 +0100 [thread overview]
Message-ID: <871s4c5an3.fsf@FE-laptop> (raw)
In-Reply-To: <875zuwo4fi.fsf@FE-laptop>
Hi Stephen,
On jeu., janv. 10 2019, Gregory CLEMENT <gregory.clement@bootlin.com> wrote:
> Hi Stephen,
>
> On jeu., janv. 10 2019, Stephen Boyd <sboyd@kernel.org> wrote:
>
>> Quoting Gregory CLEMENT (2019-01-10 08:16:22)
>>> Hi Stephen,
>>>
>>> On dim., déc. 16 2018, Gregory CLEMENT <gregory.clement@bootlin.com> wrote:
>>>
>>> > Hello,
>>> >
>>> > This is the third version of a series allowing to manage the cpu
>>> > clock for Armada 7K/8K. For these SoCs, the CPUs share the same clock
>>> > by cluster, so actually the clock management is done at cluster level.
>>> >
>>> > As for the other Armada 7K/8K clocks it is possible to have multiple
>>> > AP so here again we need to have unique name: the purpose of the second
>>> > patch is to share a common code which will be used in 3 drivers.
>>> >
>>> > The last 2 patch enable the driver at dt and platform level and will
>>> > be applied through the mvebu subsystem.
>>>
>>> What is the status of this series?
>>>
>>> The only comments I had was from Rob about the binding and I answered
>>> them 3 weeks ago. Do you have any other comments? Do you expect a rebase
>>> of this series on v5.0-rc1?
>>>
>>
>> I'm waiting for Rob. I think the binding is not proper so presumably you
>> will figure out what Rob wants and then change the code accordingly and
>> resend?
>
> Actually the binding describes properly the hardware we have and that
> what I answered to Rob.
I pinged you about this series more than one month ago, and answered Rob
concerned 2 months ago! He didn't said anything about my comments so I
really think that the binding is OK and described the hardware we have.
So could you consider to apply this series?
Thanks,
Gregory
>
> Gregory
>
> --
> Gregory Clement, Bootlin
> Embedded Linux and Kernel engineering
> http://bootlin.com
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-02-13 8:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 9:41 [PATCH v3 0/6] Add CPU clock support for Armada 7K/8K Gregory CLEMENT
2018-12-16 9:41 ` [PATCH v3 1/6] dt-bindings: ap806: add the cluster clock node in the syscon file Gregory CLEMENT
2018-12-17 22:50 ` Rob Herring
2018-12-18 15:46 ` Gregory CLEMENT
2018-12-16 9:41 ` [PATCH v3 2/6] clk: mvebu: add helper file for Armada AP and CP clocks Gregory CLEMENT
2018-12-16 9:41 ` [PATCH v3 3/6] clk: mvebu: add CPU clock driver for Armada 7K/8K Gregory CLEMENT
2018-12-16 9:41 ` [PATCH v3 4/6] clk: mvebu: ap806: Fix clock name for the cluster Gregory CLEMENT
2018-12-16 9:41 ` [PATCH v3 5/6] arm64: marvell: enable the Armada 7K/8K CPU clk driver Gregory CLEMENT
2018-12-16 9:41 ` [PATCH v3 6/6] arm64: dts: marvell: Add cpu clock node on Armada 7K/8K Gregory CLEMENT
2019-01-10 16:16 ` [PATCH v3 0/6] Add CPU clock support for " Gregory CLEMENT
2019-01-10 16:27 ` Stephen Boyd
2019-01-10 16:36 ` Gregory CLEMENT
2019-02-13 8:57 ` 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=871s4c5an3.fsf@FE-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=antoine.tenart@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=miquel.raynal@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sboyd@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@bootlin.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 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).