[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55C9C82F.6060401@st.com>
Date: Tue, 11 Aug 2015 12:02:23 +0200
From: Maxime Coquelin <maxime.coquelin@...com>
To: Lee Jones <lee.jones@...aro.org>,
Michael Turquette <mturquette@...libre.com>
CC: <linux-kernel@...r.kernel.org>, <linux-clk@...r.kernel.org>,
<sboyd@...eaurora.org>, <maxime.ripard@...e-electrons.com>,
<s.hauer@...gutronix.de>, <geert@...ux-m68k.org>
Subject: Re: [PATCH RFC RFT 3/3] clk: introduce CLK_ENABLE_HAND_OFF flag
Hi Mike,
On 08/11/2015 10:43 AM, Lee Jones wrote:
> On Mon, 10 Aug 2015, Michael Turquette wrote:
>
>>
>>
>> ST's driver is an unfortunate case. All of the clock data was shoved
>> into DT before we had a clue that doing so is a terrible idea.
I tend to agree, and wouldn't do it this way if we could rewrite the
history.
But now, we have to support it.
How can we pass CLK_ENABLE_HAND_OFF flag to a specific clock on STi
platform?
Could we imagine having a kind of "clocks-enable-hand-off" property we
could use in our clock controller DT node?
Regards,
Maxime
--
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