linux-kernel - Re: [PATCH] cpufreq: rockchip: add driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 21 Mar 2016 15:28:55 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Heiko Stübner <heiko@...ech.de>
Cc:	Feng Xiao <xf@...k-chips.com>, linux@....linux.org.uk,
	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, Stephen Boyd <sboyd@...eaurora.org>,
	Michael Turquette <mturquette@...libre.com>
Subject: Re: [PATCH] cpufreq: rockchip: add driver

On 21-03-16, 10:54, Heiko Stübner wrote:
> I hadn't seen that yet ... nice that cpufreq-dt now also supports clusters :-)
> 
> The other part still stands though, as we probably should register the 
> platform-device somewhere else and not in some new special module.
> 
> When everything is using cpufreq-dt now, I guess we could just add it to the 
> core rockchip clk-code. Or was there some agreement where this should be done 
> (obviously not the devicetree itself)?

Yeah, there was a discussion around creating a white or black list of platforms
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 thread.
Just that you need to match your platform's compatible string before doing that.

-- 
viresh