From: Aaron Lu <aaron.lu@intel.com>
To: Bin Gao <bin.gao@linux.intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, ysiyer <yegnesh.s.iyer@intel.com>,
Ajay Thomas <ajay.thomas.david.rajamanickam@intel.com>,
Bin Gao <bin.gao@intel.com>
Subject: Re: [PATCH v4 0/3] acpi/pmic: add opregion driver for Intel BXT WhiskeyCove PMIC
Date: Fri, 24 Jun 2016 10:25:21 +0800 [thread overview]
Message-ID: <6e25fae9-99a8-bc6b-258d-6cfd08f2b0e1@intel.com> (raw)
In-Reply-To: <20160624004305.GC83592@worksta>
On 06/24/2016 08:43 AM, Bin Gao wrote:
> This series modifies the pen function signature to take bit field
> and adds a new opregion driver for Intel BXT WhiskeyCove PMIC. It
> also adds support for PMIC regs operation region.
Reviewed-by: Aaron Lu <aaron.lu@intel.com>
Thanks,
Aaron
>
> Yegnesh Iyer (1):
> acpi: pmic: Modifying the pen function signature to take bit field
>
> Ajay Thomas (1):
> acpi: pmic: Add opregion driver for Intel BXT WhiskeyCove PMIC
>
> Chandra Sekhar Anagani (1):
> acpi: pmic: Add support for Intel BXT PMIC regs operation region
>
> drivers/acpi/pmic/intel_pmic.c | 87 +++++++------
> drivers/acpi/pmic/intel_pmic.h | 11 ++--
> drivers/acpi/pmic/intel_pmic_crc.c | 5 +++--
> drivers/acpi/Kconfig | 6 +
> drivers/acpi/Makefile | 1 +
> drivers/acpi/pmic/intel_pmic_bxtwc.c |449 +++++++++++++++++++++++++++++++++++
> 6 files changed, 559 insertions(+), 10 deletions(-)
> create mode 100644 drivers/acpi/pmic/intel_pmic_bxtwc.c
> --
> 1.9.1
>
next prev parent reply other threads:[~2016-06-24 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 0:43 [PATCH v4 0/3] acpi/pmic: add opregion driver for Intel BXT WhiskeyCove PMIC Bin Gao
2016-06-24 2:25 ` Aaron Lu [this message]
2016-06-25 0:24 ` 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=6e25fae9-99a8-bc6b-258d-6cfd08f2b0e1@intel.com \
--to=aaron.lu@intel.com \
--cc=ajay.thomas.david.rajamanickam@intel.com \
--cc=bin.gao@intel.com \
--cc=bin.gao@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--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).