[<prev] [next>] [day] [month] [year] [list]
Message-ID: <87h8fdke35.fsf@bootlin.com>
Date: Sun, 16 Dec 2018 10:36:46 +0100
From: Gregory CLEMENT <gregory.clement@...tlin.com>
To: Stephen Boyd <sboyd@...nel.org>
Cc: Mike Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
devicetree@...r.kernel.org, Jason Cooper <jason@...edaemon.net>,
Andrew Lunn <andrew@...n.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
linux-arm-kernel@...ts.infradead.org,
Antoine Tenart <antoine.tenart@...tlin.com>,
Miquèl Raynal <miquel.raynal@...tlin.com>,
Maxime Chevallier <maxime.chevallier@...tlin.com>
Subject: Re: [PATCH v2 0/5] Add CPU clock support for Armada 7K/8K
Hi Stephen,
On ven., déc. 14 2018, Stephen Boyd <sboyd@...nel.org> wrote:
> Quoting Gregory CLEMENT (2018-12-06 09:15:11)
>> Hello,
>>
>> This is the second 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.
>
> The binding "marvell,ap806-cpu-clock" is not documented. It was in the
> previous series but then got dropped from this one? Why?
I made a mistake and start my git-format on the wrong commit, I am
sending a new series right now with this missing patch.
Gregory
>
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
Powered by blists - more mailing lists