[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <509782f4ece936f5ac7d0abffbd555fc@risingedge.co.za>
Date: Fri, 26 Jul 2019 11:14:44 +0200
From: Justin Swartz <justin.swartz@...ingedge.co.za>
To: Heiko Stuebner <heiko@...ech.de>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org
Subject: Re: [PATCH] ARM: dts: add device tree for Mecer Xtreme Mini S6
Hi Heiko,
On 2019-07-26 00:19, Heiko Stuebner wrote:
> please add an entry to
> Documentation/devicetree/bindings/arm/rockchip.yaml
> for your board and if necessary also a vendor-prefix to
> Documentation/devicetree/bindings/vendor-prefixes.(yaml?)
OK
> please sort the &node-references alphabetically.
OK
>> +&cpu0 {
>> + clock-frequency = <1464000000>;
>
> not sure I understand the reasoning here.
> There seems to be a regulator defined, so the cpu cores should
> have operating points defined to allow them to switch between
> different frequencies as needed.
I added the clock-frequency property to quell the following messages:
[ 0.003273] /cpus/cpu@f00 missing clock-frequency property
[ 0.003323] /cpus/cpu@f01 missing clock-frequency property
[ 0.003352] /cpus/cpu@f02 missing clock-frequency property
[ 0.003382] /cpus/cpu@f03 missing clock-frequency property
I think they are from parse_dt_topology() in arch/arm/kernel/topology.c
What do you suggest?
Regards
Justin
Powered by blists - more mailing lists