[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqKUC47xB5O2Y6c3efVCjJY=V+XO3xyLTU9rNia40bdZkg@mail.gmail.com>
Date: Wed, 7 Mar 2018 19:20:00 -0600
From: Rob Herring <robh@...nel.org>
To: Jolly Shah <JOLLYS@...inx.com>
Cc: "mturquette@...libre.com" <mturquette@...libre.com>,
"sboyd@...eaurora.org" <sboyd@...eaurora.org>,
"michal.simek@...inx.com" <michal.simek@...inx.com>,
"mark.rutland@....com" <mark.rutland@....com>,
"linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Shubhrajyoti Datta <shubhraj@...inx.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Rajan Vaja <RAJANV@...inx.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 2/3] dt-bindings: clock: Add bindings for ZynqMP clock driver
On Wed, Mar 7, 2018 at 4:47 PM, Jolly Shah <JOLLYS@...inx.com> wrote:
> Hi Rob,
>
>
>> -----Original Message-----
>> From: Rob Herring [mailto:robh@...nel.org]
>> Sent: Monday, March 05, 2018 5:46 PM
>> To: Jolly Shah <JOLLYS@...inx.com>
>> Cc: mturquette@...libre.com; sboyd@...eaurora.org;
>> michal.simek@...inx.com; mark.rutland@....com; linux-clk@...r.kernel.org;
>> devicetree@...r.kernel.org; Shubhrajyoti Datta <shubhraj@...inx.com>; linux-
>> kernel@...r.kernel.org; Jolly Shah <JOLLYS@...inx.com>; Rajan Vaja
>> <RAJANV@...inx.com>; linux-arm-kernel@...ts.infradead.org
>> Subject: Re: [PATCH 2/3] dt-bindings: clock: Add bindings for ZynqMP clock
>> driver
>>
>> On Wed, Feb 28, 2018 at 02:27:40PM -0800, Jolly Shah wrote:
>> > Add documentation to describe Xilinx ZynqMP clock driver bindings.
>> >
>> > Signed-off-by: Jolly Shah <jollys@...inx.com>
>> > Signed-off-by: Rajan Vaja <rajanv@...inx.com>
>> > Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@...inx.com>
>> > ---
>> > +95 dpll_post_src
>> > +96 vpll_int
>> > +97 vpll_pre_src
>> > +98 vpll_half
>> > +99 vpll_int_mux
>> > +100 vpll_post_src
>> > +101 can0_mio
>> > +102 can1_mio
>> > +
>> > +Example:
>> > +
>> > +clk: clk {
>> > + #clock-cells = <1>;
>> > + compatible = "xlnx,zynqmp-clk";
>>
>> How do you control the clocks?
>
> Clocks are controlled by a dedicated platform management controller. Above clock ids are used to identify clocks between master and PMU.
What is the interface to the "platform management controller"? Because
you have no registers, I'm guessing a firmware interface? If so, then
just define the firmware node as a clock provider.
Rob
Powered by blists - more mailing lists