From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hans de Goede <hdegoede@redhat.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Wolfram Sang <wsa@the-dreams.de>,
Darren Hart <dvhart@infradead.org>
Subject: [v2,2/3] platform: x86: intel_cht_int33fe: Fix dependencies
Date: Mon, 28 May 2018 16:22:11 +0300 [thread overview]
Message-ID: <22ae6822d3b1f4b0b73ceb25fd069ed9dd64fdf5.camel@linux.intel.com> (raw)
On Wed, 2018-05-23 at 17:37 +0300, Heikki Krogerus wrote:
> The driver will not probe unless bq24190 is loaded, so
> making it a dependency.
>
Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
assuming it will go through some other tree.
> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> Cc: Wolfram Sang <wsa@the-dreams.de>
> Cc: Darren Hart <dvhart@infradead.org>
> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/i2c/busses/Kconfig | 3 +--
> drivers/platform/x86/Kconfig | 4 ++--
> 2 files changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
> index 99edffae27f6..4f8df2ec87b1 100644
> --- a/drivers/i2c/busses/Kconfig
> +++ b/drivers/i2c/busses/Kconfig
> @@ -202,8 +202,7 @@ config I2C_CHT_WC
>
> Note this controller is hooked up to a TI bq24292i charger-
> IC,
> combined with a FUSB302 Type-C port-controller as such it
> is advised
> - to also select CONFIG_CHARGER_BQ24190=m and
> CONFIG_TYPEC_FUSB302=m
> - (the fusb302 driver currently is in drivers/staging).
> + to also select CONFIG_TYPEC_FUSB302=m.
>
> config I2C_NFORCE2
> tristate "Nvidia nForce2, nForce3 and nForce4"
> diff --git a/drivers/platform/x86/Kconfig
> b/drivers/platform/x86/Kconfig
> index 566644bb496a..f27cb186437d 100644
> --- a/drivers/platform/x86/Kconfig
> +++ b/drivers/platform/x86/Kconfig
> @@ -866,6 +866,7 @@ config ACPI_CMPC
> config INTEL_CHT_INT33FE
> tristate "Intel Cherry Trail ACPI INT33FE Driver"
> depends on X86 && ACPI && I2C && REGULATOR
> + depends on CHARGER_BQ24190=y || (CHARGER_BQ24190=m && m)
> ---help---
> This driver add support for the INT33FE ACPI device found
> on
> some Intel Cherry Trail devices.
> @@ -877,8 +878,7 @@ config INTEL_CHT_INT33FE
> i2c drivers for these chips can bind to the them.
>
> If you enable this driver it is advised to also select
> - CONFIG_TYPEC_FUSB302=m, CONFIG_CHARGER_BQ24190=m and
> - CONFIG_BATTERY_MAX17042=m.
> + CONFIG_TYPEC_FUSB302=m and CONFIG_BATTERY_MAX17042=m.
>
> config INTEL_INT0002_VGPIO
> tristate "Intel ACPI INT0002 Virtual GPIO driver"
next reply other threads:[~2018-05-28 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 13:22 Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-23 14:37 [v2,2/3] platform: x86: intel_cht_int33fe: Fix dependencies Heikki Krogerus
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=22ae6822d3b1f4b0b73ceb25fd069ed9dd64fdf5.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wsa@the-dreams.de \
/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).