From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: John Stultz <john.stultz@linaro.org>
Cc: Wolfram Sang <wsa@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-i2c <linux-i2c@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Rosin <peda@axentia.se>,
Bartosz Golaszewski <brgl@bgdev.pl>,
YongQin Liu <yongqin.liu@linaro.org>,
Tom Gall <tom.gall@linaro.org>
Subject: Re: [PULL REQUEST] i2c for 5.8
Date: Tue, 23 Jun 2020 10:25:00 +0300 [thread overview]
Message-ID: <CAHp75Vfa_X-KR_v0bHG+mgy1q2i-_e_3Q2Akq12juviqR91PAw@mail.gmail.com> (raw)
In-Reply-To: <CANcMJZDT0oc8m1jjthVANGz6iZ+J4gv5YOqnXMLWbHtZgeQ_eA@mail.gmail.com>
On Tue, Jun 23, 2020 at 5:05 AM John Stultz <john.stultz@linaro.org> wrote:
> On Sat, Jun 13, 2020 at 4:36 AM Wolfram Sang <wsa@kernel.org> wrote:
...
> > Andy Shevchenko (17):
> ...
> > i2c: designware: Move ACPI parts into common module
>
> Just as a heads up. I'm seeing a regression from this merge that I
> bisected down to the patch above (f9288fcc5c615), with the HiKey
> board. It seems the adv7511 (HDMI bridge) driver isn't probing, which
> causes graphics to fail.
>
> I've just bisected it down and haven't managed to do much debugging,
> but I wanted to raise a flag on this. Let me know if there is anything
> you'd like me to try right off.
Thank you for the report!
The above change was purely clean up / refactoring to get PCI
enumerated devices used to ACPI additional data. I bet your patch is
correct, but I will look closer and see what is the real root cause of
such behaviour. I'll comment on your patch separately.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-06-23 7:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 11:33 [PULL REQUEST] i2c for 5.8 Wolfram Sang
2020-06-13 20:25 ` pr-tracker-bot
2020-06-23 0:50 ` John Stultz
2020-06-23 7:25 ` Andy Shevchenko [this message]
2020-06-20 17:16 Wolfram Sang
2020-06-21 2:30 ` pr-tracker-bot
2020-06-27 18:20 Wolfram Sang
2020-06-27 22:45 ` pr-tracker-bot
2020-07-05 6:56 Wolfram Sang
2020-07-05 18:00 ` pr-tracker-bot
2020-07-31 19:16 Wolfram Sang
2020-07-31 20:20 ` pr-tracker-bot
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=CAHp75Vfa_X-KR_v0bHG+mgy1q2i-_e_3Q2Akq12juviqR91PAw@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=jarkko.nikula@linux.intel.com \
--cc=john.stultz@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=tom.gall@linaro.org \
--cc=torvalds@linux-foundation.org \
--cc=wsa@kernel.org \
--cc=yongqin.liu@linaro.org \
/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).