public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
* Re: twl: not initialized and twl6030_uv_to_vsel problems
       [not found] ` <20191230174010.GO35479@atomide.com>
@ 2022-11-14 11:38   ` Andreas Kemnade
  0 siblings, 0 replies; only message in thread
From: Andreas Kemnade @ 2022-11-14 11:38 UTC (permalink / raw)
  To: Tony Lindgren; +Cc: deffo, linux-omap, aford173

Hi,

as am taming the Epson Moverio BT-200 containing
an omap 4660, I came across that this issue. The kernel hangs somewhere
after this, I am still debugging.

What is the impact of all this? Just not working cpufreq modifications?

On Mon, 30 Dec 2019 09:40:10 -0800
Tony Lindgren <tony@atomide.com> wrote:

> * deffo@gmx.de <deffo@gmx.de> [191213 10:42]:
> > Thanks for the link Adam, I fixed this on my local branch.
> > 
so, it did not went into mainline kernel? Can/did you
publish the fix?

> > Concerning the
> > 
> > [    2.318054] twl: not initialized
> > 
seen this also

> > error, this is due to the fact, that the twl itself is probed later:
> > 
> > [    3.042114] twl_probe() called
> > 
and the kernel hangs before that (probably still some other problem, still investigating)

> > So it cannot be available at this point. Might be a fundamental problem in the chronological order of init calls?  
> 
> Hmm maybe the related omap_*_initcall() needs to use *_initcall_sync()?
> 
so there is no fix yet?

Regards
Andreas

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-11-14 11:38 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <trinity-8c439dd8-69cc-4bbc-812f-a063b15a9369-1576233714035@3c-app-gmx-bs17>
     [not found] ` <20191230174010.GO35479@atomide.com>
2022-11-14 11:38   ` twl: not initialized and twl6030_uv_to_vsel problems Andreas Kemnade

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox