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:	Thu, 15 Oct 2015 11:28:40 -0700
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
Cc:	Simon <horms@...ge.net.au>,
	Michael Turquette <mturquette@...libre.com>,
	Magnus <magnus.damm@...il.com>,
	Linux-SH <linux-sh@...r.kernel.org>,
	Linux-Kernel <linux-kernel@...r.kernel.org>,
	linux-clk@...r.kernel.org
Subject: Re: [PATCH v4] clk: add CS2000 Fractional-N driver

On 10/15, Kuninori Morimoto wrote:
> 
> I understand. If my understanding is correct, user driver
> setups/enables this clock.
> If so, I still want this "clock-frequency" feature.
> because this clock requests other clock on my board.
> And requested clock requests this clock too.
> Thus, these clocks have dead lock on probe time
> 
> 	cs2000: clk_multiplier@4f {
> 		...
> 		clocks = <&rcar_sound 0>, ...
> 		...
> 	};
> 
> 	&rcar_sound {
> 		...
> 		assigned-clocks = <&cs2000>;
> 	        assigned-clock-rates = <24576000>;
> 		...
> 	};
> 

I think you're saying that the clock provider itself can't set
the rate with assigned-clock-rates? That isn't true, we should be
able to set the rate of the clock from within the provider node.

	cs2000: clk_multiplier@4f {
		assigned-clocks = <&cs2000>;
		assigned-clock-rates = <24576000>;
	};

The above should work.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ