[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdVWxpZUQk6gUhSqA4K3gpDD8wUC6SHg6HAoiC1w=3+GLw@mail.gmail.com>
Date: Tue, 11 Aug 2015 12:11:05 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Maxime Coquelin <maxime.coquelin@...com>
Cc: Lee Jones <lee.jones@...aro.org>,
Michael Turquette <mturquette@...libre.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-clk@...r.kernel.org, Stephen Boyd <sboyd@...eaurora.org>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Sascha Hauer <s.hauer@...gutronix.de>
Subject: Re: [PATCH RFC RFT 3/3] clk: introduce CLK_ENABLE_HAND_OFF flag
Hi Maxime,
On Tue, Aug 11, 2015 at 12:02 PM, Maxime Coquelin
<maxime.coquelin@...com> wrote:
> How can we pass CLK_ENABLE_HAND_OFF flag to a specific clock on STi
> platform?
Add the flag to the relevant clocks in the C code, e.g. in
clk_register_flexgen():
if (!strcmp(name, "clk-icn-cpu"))
init.flags |= CLK_ENABLE_HAND_OFF;
> Could we imagine having a kind of "clocks-enable-hand-off" property we could
> use in our clock controller DT node?
You can imagine doing "flex_flags |= CLK_ENABLE_HAND_OFF" in
st_of_flexgen_setup(), depending on the presence of such a property.
However, not disabling clocks is a software policy, not a hardware description,
so IMHO it doesn't belong in DT.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
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