From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Hans de Goede <hdegoede@redhat.com>, Stefan Roese <sr@denx.de>,
Lee Jones <lee.jones@linaro.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-acpi@vger.kernel.org, Jean Delvare <jdelvare@suse.de>,
linux-i2c@vger.kernel.org, Max Staudt <max@enpas.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH v3 0/3] Fix dependencies for ACPI drivers with OpRegion settings
Date: Mon, 18 May 2020 13:42:09 +0200 [thread overview]
Message-ID: <cover.1589801950.git.mchehab+huawei@kernel.org> (raw)
In order for drivers to work properly with OpRegion, there are some
requirements:
- The I2C core should be builtin;
- The I2C designware driver should be builtin;
- The driver itself should also be buildin;
- The I2C core should be build with support for ACPI OpRegion.
-
v3:
- Added Hans reviewed-by for the first two patches
- Added a third patch fixing dependencies for axp20x driver
Mauro Carvalho Chehab (3):
mfd: Kconfig: change INTEL_SOC_PMIC_CHTDC_TI to bool
mfd: Kconfig: fix help texts for drivers that depends on I2C=y
mfd: ensure that AXP20X_I2C will have the right deps on X86
drivers/acpi/Kconfig | 3 ++-
drivers/i2c/busses/Kconfig | 4 ++--
drivers/mfd/Kconfig | 40 +++++++++++++++++++++++++-------------
drivers/mfd/Makefile | 8 +++++---
4 files changed, 36 insertions(+), 19 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-18 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 11:42 Mauro Carvalho Chehab [this message]
2020-05-18 11:42 ` [PATCH v3 3/3] mfd: ensure that AXP20X_I2C will have the right deps on X86 Mauro Carvalho Chehab
2020-05-18 12:17 ` Hans de Goede
2020-05-18 12:53 ` Mauro Carvalho Chehab
2020-05-20 13:34 ` Wolfram Sang
2020-05-20 13:46 ` Jarkko Nikula
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=cover.1589801950.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=hdegoede@redhat.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.de \
--cc=krzk@kernel.org \
--cc=lee.jones@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=max@enpas.org \
--cc=rdunlap@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=sr@denx.de \
--cc=wsa+renesas@sang-engineering.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).