[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160324064324.GG22062@vireshk-i7>
Date: Thu, 24 Mar 2016 12:13:24 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Feng Xiao <xf@...k-chips.com>
Cc: linux@....linux.org.uk, heiko@...ech.de, rjw@...ysocki.net,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, wxt@...k-chips.com, zyw@...k-chips.com,
jay.xu@...k-chips.com, tim.chen@...k-chips.com, xxx@...k-chips.com,
huangtao@...k-chips.com
Subject: Re: [PATCH v2] cpufreq: rockchip: add driver
On 24-03-16, 11:01, Feng Xiao wrote:
> hi all,
> I found that it could match the cpufreq-dt driver succesfully only with
> the following changes.
> --- a/arch/arm64/boot/dts/rockchip/rk3366.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3366.dtsi
> @@ -139,6 +139,10 @@
> };
> };
>
> + cpufreq-dt { //the node name must be cpufreq-dt
> + compatible = "rockchip,cpufreq"; // the compatible name is
> insignificant
> + };
> +
Its not allowed to create a DT node for a dummy device and so we never
followed this way.
I have just sent a patchset and cc'd you:
"[PATCH 0/3] cpufreq: dt: Create platform device from generic code"
and so this patch shall get replaced now.
--
viresh
Powered by blists - more mailing lists