[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180212071034.GP28462@vireshk-i7>
Date: Mon, 12 Feb 2018 12:40:34 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Rob Herring <robh+dt@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
Stephen Boyd <sboyd@...eaurora.org>,
Rajendra Nayak <rnayak@...eaurora.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
Rob Clark <robdclark@...il.com>,
Sascha Hauer <s.hauer@...gutronix.de>,
Lucas Stach <l.stach@...gutronix.de>,
Shawn Guo <shawnguo@...nel.org>,
Fabio Estevam <fabio.estevam@....com>,
Nishanth Menon <nm@...com>, Wei Xu <xuwei5@...ilicon.com>
Subject: Re: [PATCH V6 Resend 00/13] drivers: Boot Constraint core
On 25-01-18, 16:31, Viresh Kumar wrote:
> So AFAICT the basic problem I was trying to solve still exists with simple-fb
> as well. And the problem is that nothing prevents another driver to get probed
> before the display driver (or simple-fb) and reconfigure the resources. Even if
> we let simple-fb come up really early, the resources like clk/regulator may not
> be available. And so the ordering thing is still unsolved for me.
Ping !!
I understand your concerns Rob, they are surely genuine and I can't
deny that. But I don't see a cleaner "way" (Or "Hack", if you want to
call it that way), to solve these ugly problems.
--
viresh
Powered by blists - more mailing lists