From: Tony Lindgren <tony@atomide.com>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
linux-mmc@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: Linux 5.18.x: sdhci issue
Date: Thu, 16 Jun 2022 10:18:05 +0300 [thread overview]
Message-ID: <YqrZLWp4Nyhd5v1d@atomide.com> (raw)
In-Reply-To: <CAGm1_kvM0p=T4L4vDpXj2quMCPqoBidztsLaAsKYCYCGpvVnng@mail.gmail.com>
* Yegor Yefremov <yegorslists@googlemail.com> [220615 08:54]:
> Hi Tony,
>
> On Wed, Jun 15, 2022 at 10:08 AM Tony Lindgren <tony@atomide.com> wrote:
> >
> > * Yegor Yefremov <yegorslists@googlemail.com> [220615 09:40]:
> > > Hi Tony, Ulf,
> > >
> > > On Thu, May 5, 2022 at 7:03 AM Tony Lindgren <tony@atomide.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > * Yegor Yefremov <yegorslists@googlemail.com> [220504 09:12]:
> > > > > Hi Tony, all,
> > > > >
> > > > > During the kernel boot I see the following error. The device is still
> > > > > working afterwards. 5.17.5 shows the same behavior. Is this a known
> > > > > issue?
> > > >
> > > > Thanks for reporting it, I was not aware of this one. Might be worth
> > > > bisecting. Adding linux-mmc and Ulf.
> > >
> > > This is my bisect result:
> > >
> > > f433e8aac6b94218394c6e7b80bb89e4e79c9549 is the first bad commit
> > > commit f433e8aac6b94218394c6e7b80bb89e4e79c9549
> > > Author: Tony Lindgren <tony@atomide.com>
> > > Date: Fri Oct 15 13:47:18 2021 +0300
> > >
> > > mmc: sdhci-omap: Implement PM runtime functions
> > >
> > > Implement PM runtime functions and enable autosuspend.
> > >
> > > Note that we save context in probe to avoid restoring invalid context
> > > on the first resume. For system suspend, we have the new PM runtime
> > > functions do most of the work.
> > >
> > > Signed-off-by: Tony Lindgren <tony@atomide.com>
> > > Link: https://lore.kernel.org/r/20211015104720.52240-5-tony@atomide.com
> > > Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
> >
> > OK thanks this makes sense based on what Arnd replied a few days ago.
> >
> > Regards,
>
> Your patch did the trick: all warnings/errors are gone. Thanks
> everyone for the help.
OK thanks for testing, will send out a proper patch today for this.
Regards,
Tony
prev parent reply other threads:[~2022-06-16 7:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 9:12 Linux 5.18.x: sdhci issue Yegor Yefremov
2022-05-05 5:02 ` Tony Lindgren
2022-05-31 8:28 ` Yegor Yefremov
2022-05-31 9:23 ` Arnd Bergmann
2022-06-01 6:08 ` Yegor Yefremov
2022-06-01 6:45 ` Arnd Bergmann
2022-06-01 6:49 ` Yegor Yefremov
2022-06-01 13:10 ` Arnd Bergmann
2022-05-31 8:42 ` Arnd Bergmann
2022-06-15 8:06 ` Tony Lindgren
2022-06-15 6:45 ` Yegor Yefremov
2022-06-15 8:07 ` Tony Lindgren
2022-06-15 8:58 ` Yegor Yefremov
2022-06-16 7:18 ` Tony Lindgren [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=YqrZLWp4Nyhd5v1d@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=yegorslists@googlemail.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