linux-kernel - Re: [PATCH v4 2/4] clk: qcom: Add support for RCGs with shared branches

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:	Wed, 16 Sep 2015 15:07:22 -0700
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Georgi Djakov <georgi.djakov@...aro.org>
Cc:	mturquette@...libre.com, linux-clk@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v4 2/4] clk: qcom: Add support for RCGs with shared
 branches

On 09/16, Georgi Djakov wrote:
> +static int clk_rcg2_shared_enable(struct clk_hw *hw)
> +{
> +	struct clk_rcg2 *rcg = to_clk_rcg2(hw);
> +
> +	if (!rcg->current_freq) {
> +		struct clk_hw *parent = clk_hw_get_parent(hw);
> +		unsigned long parent_rate = clk_hw_get_rate(parent);
> +
> +		rcg->current_freq = clk_rcg2_recalc_rate(hw, parent_rate);

Hmm no. I meant adding a recal_rate implementation for this
specific type of clk_ops that assigns the current_freq value when
it's called. I assume we're not calling enable on this clock
before we register it with the framework.

-- 
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/