linux-kernel - Re: [PATCH 1/2] clk: qcom: common: Add API to register board clocks backwards compatibly

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 27 Oct 2015 16:01:55 -0700
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Mike Turquette <mturquette@...libre.com>
Cc:	linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
	linux-arm-msm@...r.kernel.org,
	Georgi Djakov <georgi.djakov@...aro.org>
Subject: Re: [PATCH 1/2] clk: qcom: common: Add API to register board clocks
 backwards compatibly

On 10/26, Stephen Boyd wrote:
> We want to put the XO board clocks into the dt files. Add an API
> to do this generically. This also makes a place for us to handle
> the case where the RPM driver is enabled or disabled.
> 
> Cc: Georgi Djakov <georgi.djakov@...aro.org>
> Signed-off-by: Stephen Boyd <sboyd@...eaurora.org>
> ---
> 
> I'm also thinking that maybe we should register the board clock if it
> isn't there in DT and then we'll either register the pass through or
> we'll skip it depending on if the RPM driver is enabled. That
> way the RPM driver doesn't need to know anything, just register the
> clock with parent as the board clock.

That seems like a better idea. v2 coming with that change and a
sleep_clk specific API, plus all the armv7 platforms converted.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/