From mboxrd@z Thu Jan 1 00:00:00 1970 From: Viresh Kumar Subject: Re: [PATCH] cpufreq: rockchip: add driver Date: Mon, 21 Mar 2016 15:28:55 +0530 Message-ID: <20160321095855.GE27778@vireshk-i7> References: <1458303004-26445-1-git-send-email-xf@rock-chips.com> <1787319.AFAWVqkdk0@diego> <20160321095049.GD27778@vireshk-i7> <1505152.fhSnu3pvDr@diego> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <1505152.fhSnu3pvDr@diego> Sender: linux-pm-owner@vger.kernel.org To: Heiko =?iso-8859-1?Q?St=FCbner?= Cc: Feng Xiao , linux@arm.linux.org.uk, rjw@rjwysocki.net, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, wxt@rock-chips.com, zyw@rock-chips.com, jay.xu@rock-chips.com, tim.chen@rock-chips.com, xxx@rock-chips.com, huangtao@rock-chips.com, Stephen Boyd , Michael Turquette List-Id: linux-rockchip.vger.kernel.org On 21-03-16, 10:54, Heiko St=FCbner wrote: > I hadn't seen that yet ... nice that cpufreq-dt now also supports clu= sters :-) >=20 > The other part still stands though, as we probably should register th= e=20 > platform-device somewhere else and not in some new special module. >=20 > When everything is using cpufreq-dt now, I guess we could just add it= to the=20 > core rockchip clk-code. Or was there some agreement where this should= be done=20 > (obviously not the devicetree itself)? Yeah, there was a discussion around creating a white or black list of p= latforms that want to create a platform device for cpufreq-dt. That can be done = in cpufreq-dt.c or a new file, but I haven't worked out on that yet. You can do it from clk-code or from the driver that was added in this t= hread. Just that you need to match your platform's compatible string before do= ing that. --=20 viresh