[PATCH] ARM: OMAP2+: omap_device: fix idling of devices during probe

[Andreas Kemnade]

Hi,

On Fri, 8 Jan 2021 13:17:06 -0600
Adam Ford <aford173 at gmail.com> wrote:

> On Mon, Dec 7, 2020 at 8:01 AM Tony Lindgren <tony at atomide.com> wrote:
> >
> > * Doug Anderson <dianders at chromium.org> [201204 16:43]:  
> > > Hi,
> > >
> > > On Fri, Dec 4, 2020 at 8:14 AM Andreas Kemnade <andreas at kemnade.info> wrote:  
> > > >  
> > > > > > Fixes: 21b2cec61c04 ("mmc: Set PROBE_PREFER_ASYNCHRONOUS for drivers that existed in v4.4")  
> > > > >
> > > > > From the description it sounds like this problem has always existed
> > > > > but the async probe just tickled it reliably.  Seems like it'd make
> > > > > sense to tag the "Fixes" as some earlier commit so you make sure your
> > > > > fix gets picked to kernels even if they don't have the async probe
> > > > > patch?
> > > > >  
> > > >
> > > > Hmm, maybe
> > > > Fixes: 04abaf07f6d5 ("ARM: OMAP2+: omap_device: Sync omap_device and
> > > > pm_runtime after probe defer")
> > > >
> > > > But on the other hand to stable branches only such patches are applied
> > > > which solve pratical problems not only theoretical problems. But maybe
> > > > it solves several random issues where nobody took care to debug them.
> > > >
> > > > That would be since v4.11.  
> > >
> > > I guess maybe best is to include both.  Then if someone is debugging
> > > why their async probe is failing they will notice this commit, but
> > > they also might decide to pick it earlier just to be safe...  
> >
> > OK I'll add the above fixes tag too and apply this into fixes.
> >  
> 
> It might be too late, but...
> 
> Tested-by: Adam Ford <aford173 at gmail.com>  #logicpd-torpedo-37xx-devkit
> 
hmm, when will it arrive in mainline? 

Regards,
Andreas