Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751501AbaKKCEu (ORCPT ); Mon, 10 Nov 2014 21:04:50 -0500 Received: from mga09.intel.com ([134.134.136.24]:43203 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750993AbaKKCEr (ORCPT ); Mon, 10 Nov 2014 21:04:47 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.07,357,1413270000"; d="scan'208";a="605663168" Message-ID: <54616E55.80204@intel.com> Date: Tue, 11 Nov 2014 10:03:01 +0800 From: Aaron Lu MIME-Version: 1.0 To: "Rafael J. Wysocki" , Lee Jones CC: linux-acpi@vger.kernel.org, linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org, Jacob Pan Subject: Re: [PATCH 0/3] Support PMIC operation region for CrystalCove and XPower References: <1414735705-18366-1-git-send-email-aaron.lu@intel.com> In-Reply-To: <1414735705-18366-1-git-send-email-aaron.lu@intel.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? Thanks, Aaron > > 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 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/