From: Aaron Lu <aaron.lu@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Lee Jones <lee.jones@linaro.org>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Yegnesh Iyer <yegnesh.s.iyer@intel.com>,
linux-acpi@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/3] Support PMIC operation region for CrystalCove and XPower
Date: Fri, 21 Nov 2014 15:11:48 +0800 [thread overview]
Message-ID: <1416553911-22990-1-git-send-email-aaron.lu@intel.com> (raw)
v3:
Only some function/variable name changes, no functiona changes:
- Replace the dptf/DPTF word originate from the BIOS ACPI table with more
meaningful word thermal/THERMAL in all places;
- Eliminate the soc part in various structure and function names to make
them shorter:
intel_soc_pmic_opregion -> intel_pmic_opregion
intel_soc_pmic_pmop_handler -> intel_pmic_pmop_handler
intel_soc_pmic_install_opregion_handler -> intel_pmic_install_opregion_handler
etc.
v2:
Place PMIC operation files under drivers/acpi/pmic instead of
drivers/acpi/pmic_opregion as suggested by Rafael;
Rename PMIC operation files to make them shorter as suggested by Rafael.
v1:
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.
Aaron Lu (3):
ACPI / PMIC: support PMIC operation region for CrystalCove
ACPI / PMIC: support PMIC operation region for XPower AXP288
ACPI / PMIC: AXP288: support virtual GPIO in ACPI table
next reply other threads:[~2014-11-21 7:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 7:11 Aaron Lu [this message]
2014-11-21 7:11 ` [PATCH v3 1/3] ACPI / PMIC: support PMIC operation region for CrystalCove Aaron Lu
2014-11-24 0:59 ` Rafael J. Wysocki
2014-11-24 5:55 ` Aaron Lu
2014-11-24 9:21 ` [PATCH v3 1/3 updated] " Aaron Lu
2014-11-21 7:11 ` [PATCH v3 2/3] ACPI / PMIC: support PMIC operation region for XPower AXP288 Aaron Lu
2014-11-24 1:04 ` Rafael J. Wysocki
2014-11-24 9:24 ` [PATCH v3 updated " Aaron Lu
2014-11-21 7:11 ` [PATCH v3 3/3] ACPI / PMIC: AXP288: support virtual GPIO in ACPI table Aaron Lu
2014-11-24 1:06 ` Rafael J. Wysocki
2014-11-24 6:01 ` Aaron Lu
2014-11-24 9:32 ` [PATCH v3 updated " Aaron Lu
2014-11-24 15:19 ` Rafael J. Wysocki
2014-11-25 1:44 ` Zheng, Lv
2014-11-25 12:01 ` Aaron Lu
2014-11-25 20:34 ` Rafael J. Wysocki
2014-11-25 1:47 ` [PATCH v3 0/3] Support PMIC operation region for CrystalCove and XPower Rafael J. Wysocki
2014-11-25 11:52 ` Aaron Lu
2014-11-25 20:41 ` Rafael J. Wysocki
2014-11-26 2:35 ` Aaron Lu
2014-11-26 2:44 ` Aaron Lu
2014-11-26 23:02 ` Rafael J. Wysocki
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=1416553911-22990-1-git-send-email-aaron.lu@intel.com \
--to=aaron.lu@intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=yegnesh.s.iyer@intel.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).