[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZlhFsGw7PaseT_08@apocalypse>
Date: Thu, 30 May 2024 11:24:00 +0200
From: Andrea della Porta <andrea.porta@...e.com>
To: Stefan Wahren <wahrenst@....net>
Cc: Andrea della Porta <andrea.porta@...e.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Florian Fainelli <florian.fainelli@...adcom.com>,
Ray Jui <rjui@...adcom.com>, Scott Branden <sbranden@...adcom.com>,
Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Kamal Dasu <kamal.dasu@...adcom.com>,
Al Cooper <alcooperx@...il.com>, devicetree@...r.kernel.org,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mmc@...r.kernel.org
Subject: Re: [PATCH v4 4/4] arm64: dts: broadcom: Add support for BCM2712
Hi Stefan,
On 08:11 Thu 30 May , Stefan Wahren wrote:
[cut...]
> > + clocks {
> > + /* The oscillator is the root of the clock tree. */
> > + clk_osc: clk-osc {
> > + compatible = "fixed-clock";
> > + #clock-cells = <0>;
> > + clock-output-names = "osc";
> > + clock-frequency = <54000000>;
> > + };
> > +
> > + clk_vpu: clk-vpu {
> > + #clock-cells = <0>;
> > + compatible = "fixed-clock";
> > + clock-frequency = <750000000>;
> > + clock-output-names = "vpu-clock";
> > + };
> Is the VPU clock really fixed or is it just a workaround for minimal
> boot support?
Unfortunately I don't have enough insight on this due to lack of documentation.
I had to take it by faith from downstream dts.
Many thanks,
Andrea
Powered by blists - more mailing lists