From: Hans de Goede <hdegoede@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Lee Jones <lee@kernel.org>, Mark Brown <broonie@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Backlight for v6.1
Date: Sat, 8 Oct 2022 21:59:14 +0200 [thread overview]
Message-ID: <d66fa3ea-1efe-e7da-be80-89507067e2a9@redhat.com> (raw)
In-Reply-To: <CAHk-=wixtjmiENLbc1=Hds3mMSjVRA3ZiwXN7yg8mw_1MCg_QQ@mail.gmail.com>
Hi Linus,
On 10/8/22 21:02, Linus Torvalds wrote:
> On Sat, Oct 8, 2022 at 11:31 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
>>
>> The Intel PMICs are the beasts when we want to run the code on the real
>> hardware.
>
> Yeah, I don't expect he driver to work on real hardware,
I'm not sure what you mean here. I guess you mean that you
do not expect to be able to test the driver on real hw
yourself?
I have several x86 tablets with this PMIC and the driver
does actually work on real hw, I test it regularly.
As for the admittedly weird:
depends on I2C_DESIGNWARE_PLATFORM=y
dependency, as Andy mentioned on most of these devices
the ACPI tables (often the _PS0 / _PS3 power on/off methods)
poke at the PMIC through ACPI Opregions which are registered
through the MFD driver. This all needs to be available early
on which is why I2C_DESIGNWARE_PLATFORM needs to be builtin
(the PMIC is connected to the system through a designware
I2C controller).
When built as a module we get a whole bunch of ACPI subsys
errors about OpRegion calls to a non registered OpRegion in
dmesg and this can also results in real bugs like e.g.
a touchscreen not working because it was not powered on.
After several bug reports about this I decided to add this
dependency to force distros to built I2C_DESIGNWARE_PLATFORM
into the main vmlinuz image if they want to enable these
drivers.
<snip>
> depends on I2C_DESIGNWARE_PLATFORM=y
>
> might be better with a "|| COMPILE_TEST" to at least find the build
> issues, even if actual runtime testing is a different anumal entirely.
Adding "|| COMPILE_TEST" sounds like a good idea to me. Note that as
I tried to explain the:
depends on I2C_DESIGNWARE_PLATFORM=y
is actually there to avoid known runtime issues with having that
built as a module in combination with this (and a few other similar)
PMIC drivers.
Regards,
Hans
next prev parent reply other threads:[~2022-10-08 19:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 12:44 Lee Jones
2022-10-05 17:59 ` Linus Torvalds
2022-10-07 13:16 ` Lee Jones
2022-10-07 18:45 ` Linus Torvalds
2022-10-08 18:30 ` Andy Shevchenko
2022-10-08 19:02 ` Linus Torvalds
2022-10-08 19:59 ` Hans de Goede [this message]
2022-10-08 23:23 ` Linus Torvalds
2022-10-09 12:58 ` Hans de Goede
2022-10-20 3:31 ` Randy Dunlap
2022-10-20 13:48 ` Andy Shevchenko
2022-10-20 13:53 ` Hans de Goede
2022-10-10 7:42 ` Lee Jones
2022-10-05 18:40 ` 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=d66fa3ea-1efe-e7da-be80-89507067e2a9@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome