[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20150820151143.GC30520@lukather>
Date: Thu, 20 Aug 2015 17:11:43 +0200
From: Maxime Ripard <maxime.ripard@...e-electrons.com>
To: Michael Turquette <mturquette@...libre.com>
Cc: Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org,
linux-clk@...r.kernel.org, sboyd@...eaurora.org,
s.hauer@...gutronix.de, geert@...ux-m68k.org
Subject: Re: [PATCH RFC RFT 3/3] clk: introduce CLK_ENABLE_HAND_OFF flag
On Tue, Aug 18, 2015 at 09:33:56AM -0700, Michael Turquette wrote:
> Quoting Maxime Ripard (2015-08-18 08:52:03)
> > On Tue, Aug 11, 2015 at 11:58:27AM -0700, Michael Turquette wrote:
> > > For example the whole big messy fuss over the DT bindings for the
> > > simple-fb driver could have been avoided if this feature had existed
> > > then.
> >
> > Not really, there was additional issues that would have prevented to
> > use that in simplefb too. For example the fact that you wouldn't care
> > about the clock at all if simplefb was not enabled in the kernel. Or
> > that you would like to protect the pixel clock (or its parent) from
> > having its rate changed.
>
> You're right, there may be more issues involved here. But as I recall
> there was interest in using simplefb to "hand-off" to a loadable module
> later on, and that was really what I was referring to.
>
> In that case we could "skip" simplefb having to claim and enable clocks.
> The loadable module that is the "rich" driver could just claim them as
> usual and the reference counts would be handed over at that time.
Yep, but the issue would be broader but just the clocks, but yeah,
you're right :)
> But I don't mean to dig up past flamebait ;-)
Yep, it's probably better not to :)
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists