From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Martin Townsend <mtownsend1973@gmail.com>
Cc: linux-spi <linux-spi@vger.kernel.org>
Subject: Re: SPI driver probe problem during boot
Date: Tue, 5 May 2020 14:38:31 +0300 [thread overview]
Message-ID: <CAHp75VeJPuEc9HUOZ3toe29pj62xu7SR3C_+rFuQe792D1atSg@mail.gmail.com> (raw)
In-Reply-To: <CABatt_wbC9sDu04FfG6NNi6P6NzhT6tmm=PHh3VXZhR_=1K03A@mail.gmail.com>
On Tue, May 5, 2020 at 12:47 PM Martin Townsend <mtownsend1973@gmail.com> wrote:
> On Tue, May 5, 2020 at 9:43 AM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> > On Tue, May 5, 2020 at 11:04 AM Martin Townsend <mtownsend1973@gmail.com> wrote:
...
> > > Now this is on a oldish kernel (4.12) and moving the kernel forward
> > > isn't trivial. I was just wondering if this has been fixed already so
> > > I could backport it, I couldn't see anything in the latest kernel but
> > > maybe it has been solved a different way. If not is there a better
> > > way of fixing this? Or is the OMAP SPI controller driver the problem,
> > > should it parse the child nodes first and set itself up accordingly?
> >
> > Can you confirm the issue on v5.7-rc4?
> >
>
> I will try but it's not always possible with these embedded SoC's
> without a lot of work.
I understand that, but if issue is fixed the proper (but might be
painful and long) way is to bisect to the fix and try to backport.
Otherwise it will need to be fixed in newest available kernel first.
So, in either case you should test on latest available.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2020-05-05 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 8:03 SPI driver probe problem during boot Martin Townsend
2020-05-05 8:43 ` Andy Shevchenko
2020-05-05 9:47 ` Martin Townsend
2020-05-05 11:38 ` Andy Shevchenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHp75VeJPuEc9HUOZ3toe29pj62xu7SR3C_+rFuQe792D1atSg@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=linux-spi@vger.kernel.org \
--cc=mtownsend1973@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).