On 11/06/2014 04:12 PM, Rob Herring wrote:
> On Thu, Nov 6, 2014 at 12:37 AM, Alexandre Courbot <acourbot@xxxxxxxxxx> wrote:
>> On 10/30/2014 01:22 AM, Tomeu Vizoso wrote:
>>> #clock-cells = <1>;
>>> #reset-cells = <1>;
>>> };
>>> @@ -60,4 +83,23 @@ Example board file:
>>> &tegra_car {
>>> clocks = <&clk_32k> <&osc>;
>>> };
>>> +
>>> + clock@0,60006000 {
>>> + emc-timings@3 {
>>> + nvidia,ram-code = <3>;
>>> +
>>> + timing@12750000 {
>>> + clock-frequency = <12750000>;
>>> + nvidia,parent-clock-frequency =
>>> <408000000>;
>>> + clocks = <&tegra_car TEGRA124_CLK_PLL_P>;
>>> + clock-names = "emc-parent";
>
> Why do you need both clocks and hardcoded values? clock-frequency is
> the desired freq you want to set TEGRA124_CLK_PLL_P to?
For the EMC clock to run at 12.75 MHz, its parent should become
TEGRA124_CLK_PLL_P and it has to be running at 408 MHz.
> The clocks property really belongs as part of the memory controller
> node or a memory device node.
What would be the rationale for that? The clock provider needs to know
what clock should become the parent of the EMC clock when changing rates.
Thanks,
Tomeu
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
