linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Lee Jones <lee.jones@linaro.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] mfd: intel_soc_pmic: Select designware i2c-bus driver
Date: Thu, 23 Mar 2017 23:31:31 +0100	[thread overview]
Message-ID: <16efec42-64cf-88e8-8ebb-cf9fdfc383c3@redhat.com> (raw)
In-Reply-To: <20170323164647.tyyqoziiy4jwg5vc@dell>

Hi,

On 23-03-17 17:46, Lee Jones wrote:
> On Wed, 22 Mar 2017, Andy Shevchenko wrote:
>
>> On Wed, 2017-03-22 at 12:29 +0100, Hans de Goede wrote:
>>> The Crystal Cove PMIC provides an ACPI OPRegion handler, which must be
>>> available before other drivers using it are loaded, which is why
>>> INTEL_SOC_PMIC is a bool.
>>>
>>> Just having the driver is not enough, the driver for the i2c-bus must
>>> also be built in, to ensure this, this patch adds a select for it.
>>>
>>
>>> While at it this patch also changes the human readable name of the
>>> Kconfig
>>> option to make clear the INTEL_SOC_PMIC option selects support for the
>>> Intel Crystal Cove PMIC and documents why this is a bool.
>>
>> The above is what my patch does, I'm okay if the change is going with
>> this series as long as Lee is on the same side. Otherwise I would prefer
>> to go my changes first.
>
> I think this set is going to need to be rebase on top of MFD.

This patch (2/5) and 3/5 should apply cleanly as they only
touch drivers/mfd/Kconfig and mfd-for-next has only 1 commit
touching Kconfig which is no where near the areas these 2
patches are making changes. So I believe they can be applied as is.

As for the other patches, patch 1/5 is for the ACPI subsys, since
you've requested changes to the Cherry Trail Whiskey Cove MFD driver
I will squash 4/5 into the new version of that and 5/5 again is an
ACPI patch.

Regards,

Hans



>
>>> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>>> ---
>>> Note this patch will partially conflicts with (contains the same
>>> changes as)
>>> a patch in Andy Shevchenko's tree.
>>> ---
>>>  drivers/mfd/Kconfig | 7 +++++--
>>>  1 file changed, 5 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
>>> index d427a10..0c6a967 100644
>>> --- a/drivers/mfd/Kconfig
>>> +++ b/drivers/mfd/Kconfig
>>> @@ -425,14 +425,17 @@ config LPC_SCH
>>>  	  System Management Bus and General Purpose I/O.
>>>
>>>  config INTEL_SOC_PMIC
>>> -	bool "Support for Intel Atom SoC PMIC"
>>> +	# This is a bool as it provides an ACPI Opregion which must
>>> be
>>> +	# available as soon as possible
>>> +	bool "Support for Intel Crystal Cove PMIC"
>>>  	depends on GPIOLIB
>>>  	depends on I2C=y
>>>  	select MFD_CORE
>>>  	select REGMAP_I2C
>>>  	select REGMAP_IRQ
>>> +	select I2C_DESIGNWARE_PLATFORM
>>>  	help
>>> -	  Select this option to enable support for the PMIC device
>>> +	  Select this option to enable support for the Crystal Cove
>>> PMIC
>>>  	  on some Intel SoC systems. The PMIC provides ADC, GPIO,
>>>  	  thermal, charger and related power management functions
>>>  	  on these systems.
>>
>

  reply	other threads:[~2017-03-23 22:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 11:29 [PATCH 0/5] Intel PMIC: Intel PMIC mfd and OPRegion drivers must be built in Hans de Goede
2017-03-22 11:29 ` [PATCH 1/5] ACPI / PMIC: Stop xpower OPRegion handler relying on IIO Hans de Goede
2017-03-22 11:29 ` [PATCH 2/5] mfd: intel_soc_pmic: Select designware i2c-bus driver Hans de Goede
2017-03-22 12:53   ` Andy Shevchenko
2017-03-23 16:46     ` Lee Jones
2017-03-23 22:31       ` Hans de Goede [this message]
2017-03-22 11:29 ` [PATCH 3/5] mfd: axp20c-i2c: Select designware i2c-bus driver on x86 Hans de Goede
2017-03-22 11:29 ` [PATCH 4/5] mfd: intel_soc_pmic_chtwc: This driver must always be builtin when enabled Hans de Goede
2017-03-22 11:29 ` [PATCH 5/5] ACPI / PMIC: mfd: intel_pmic_chtwc: This driver must always be builtin Hans de Goede

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=16efec42-64cf-88e8-8ebb-cf9fdfc383c3@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=lee.jones@linaro.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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).