[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c259e5166d9f6c2e1db3bcbec6dc943e578ebef2.camel@suse.de>
Date: Tue, 21 May 2019 13:40:47 +0200
From: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
To: Stefan Wahren <stefan.wahren@...e.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Florian Fainelli <f.fainelli@...il.com>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
bcm-kernel-feedback-list@...adcom.com
Cc: mbrugger@...e.de, viresh.kumar@...aro.org, rjw@...ysocki.net,
sboyd@...nel.org, eric@...olt.net, ptesarik@...e.com,
linux-rpi-kernel@...ts.infradead.org, ssuloev@...altech.com,
linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
mturquette@...libre.com, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC v2 4/5] dts: bcm2837: add per-cpu clock devices
On Mon, 2019-05-20 at 14:19 +0200, Stefan Wahren wrote:
> Hi Nicolas,
>
> On 20.05.19 12:47, Nicolas Saenz Julienne wrote:
> > The four CPUs share a same clock source called pllb_arm. The clock can
> > be scaled through the raspberrypi firmware interface.
> do you see a problem with applying this also to bcm2835.dtsi and
> bcm2836.dtsi?
Not at all. I just need to test it first.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists