From: Lee Jones <lee.jones@linaro.org>
To: Aaron Lu <aaron.lu@intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-acpi@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: Re: [PATCH 0/3] Support PMIC operation region for CrystalCove and XPower
Date: Tue, 11 Nov 2014 11:11:52 +0000 [thread overview]
Message-ID: <20141111111152.GX24004@x1> (raw)
In-Reply-To: <54616E55.80204@intel.com>
On Tue, 11 Nov 2014, Aaron Lu wrote:
> On 10/31/2014 02:08 PM, Aaron Lu wrote:
> > On Intel Baytrail-T and Baytrail-T-CR platforms, there are two customized
> > ACPI operation regions defined for the Power Management Integrated Circuit
> > device, one is for power resource handling and one is for thermal: sensor
> > temperature reporting, trip point setting, etc. There are different PMIC
> > chips used on those platforms and though each has the same two operation
> > regions and functionality, their implementation is different so every PMIC
> > will need a driver. But since their functionality is similar, some common
> > code is abstracted into the intel_soc_pmic_opregion.c.
> >
> > The last version is posted here:
> > https://lkml.org/lkml/2014/9/8/801
> >
> > Changes since then:
> > 1 Move to drivers/acpi as discussed on the above thread;
> > 2 Added support for XPower AXP288 PMIC operation region support;
> > 3 Since operation region handler can not be removed(at the moment at least),
> > use bool for the two operation region driver configs instead of tristate;
> > Another reason to do this is that, with Mika's MFD ACPI support patch, all
> > those MFD cell devices created will have the same modalias as their parent's
> > so it doesn't make much sense to compile these drivers into modules.
> >
> > Patch 1 applies on top of Rafael's pm-next branch, and then patch 2 and
> > patch 3 needs merge of Lee's mfd/ib-mfd-iio-3.19 branch where the PMIC
> > driver XPower AXP288 and iio driver axp288_adc is located.
>
> Since patch 2-3 are based on top of the mfd/ib-mfd-iio-3.19 branch, it
> would be easy to go through the mfd/ib-mfd-iio-3.19 branch.
>
> Rafael,
> Can I get your ACK for the three patches?
>
> Lee,
> Can you please take the series if Rafael gives it ack?
Yes, no problem.
> > Aaron Lu (3):
> > ACPI / pmic_opregion: support PMIC operation region for CrystalCove
> > ACPI / pmic_opregion: support PMIC operation region for XPower AXP288
> > ACPI / pmic_opregion: AXP288: support virtual GPIO in ACPI table
> >
>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-11-11 11:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 6:08 [PATCH 0/3] Support PMIC operation region for CrystalCove and XPower Aaron Lu
2014-10-31 6:08 ` [PATCH 1/3] ACPI / pmic_opregion: support PMIC operation region for CrystalCove Aaron Lu
2014-10-31 6:08 ` [PATCH 2/3] ACPI / pmic_opregion: support PMIC operation region for XPower AXP288 Aaron Lu
[not found] ` <1414735705-18366-1-git-send-email-aaron.lu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-10-31 6:08 ` [PATCH 3/3] ACPI / pmic_opregion: AXP288: support virtual GPIO in ACPI table Aaron Lu
2014-11-11 2:03 ` [PATCH 0/3] Support PMIC operation region for CrystalCove and XPower Aaron Lu
2014-11-11 11:11 ` Lee Jones [this message]
2014-11-11 23:35 ` Rafael J. Wysocki
2014-11-12 1:48 ` Aaron Lu
[not found] ` <5462BC5A.7070407-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-11-13 0:51 ` Rafael J. Wysocki
[not found] ` <1834078.D8VLOj1LAI-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2014-11-13 8:39 ` Aaron Lu
[not found] ` <3052882.EdcZmghHR3-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2014-11-12 9:44 ` Lee Jones
2014-11-13 0:53 ` Rafael J. Wysocki
[not found] ` <1668657.Fqph6NyFNz-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2014-11-13 10:41 ` Lee Jones
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=20141111111152.GX24004@x1 \
--to=lee.jones@linaro.org \
--cc=aaron.lu@intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-iio@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).