Re: [PATCH] i2c: designware: Fix functionality in !CONFIG_ACPI case

2020-06-23 Thread Andy Shevchenko
On Tue, Jun 23, 2020 at 10:59:40AM +0300, Jarkko Nikula wrote: > Hi > > On 6/23/20 5:51 AM, John Stultz wrote: > > On the HiKey board, where CONFIG_ACPI is not set, we started > > to see a graphics regression where the adv7511 HDMI bridge driver > > wasn't probing. This was due to the i2c bus

Re: [PATCH] i2c: designware: Fix functionality in !CONFIG_ACPI case

2020-06-23 Thread Jarkko Nikula
On 6/23/20 10:59 AM, Jarkko Nikula wrote: Hi On 6/23/20 5:51 AM, John Stultz wrote: On the HiKey board, where CONFIG_ACPI is not set, we started to see a graphics regression where the adv7511 HDMI bridge driver wasn't probing. This was due to the i2c bus failing to start up. I bisected the

Re: [PATCH] i2c: designware: Fix functionality in !CONFIG_ACPI case

2020-06-23 Thread Jarkko Nikula
Hi On 6/23/20 5:51 AM, John Stultz wrote: On the HiKey board, where CONFIG_ACPI is not set, we started to see a graphics regression where the adv7511 HDMI bridge driver wasn't probing. This was due to the i2c bus failing to start up. I bisected the problem down to commit f9288fcc5c615 ("i2c:

[PATCH] i2c: designware: Fix functionality in !CONFIG_ACPI case

2020-06-22 Thread John Stultz
On the HiKey board, where CONFIG_ACPI is not set, we started to see a graphics regression where the adv7511 HDMI bridge driver wasn't probing. This was due to the i2c bus failing to start up. I bisected the problem down to commit f9288fcc5c615 ("i2c: designware: Move ACPI parts into common