Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752916AbdIHAqE (ORCPT ); Thu, 7 Sep 2017 20:46:04 -0400 Received: from mga02.intel.com ([134.134.136.20]:56712 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751774AbdIHAqC (ORCPT ); Thu, 7 Sep 2017 20:46:02 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,360,1500966000"; d="scan'208";a="898218466" From: "Mani, Rajmohan" To: "Rafael J. Wysocki" CC: "Rafael J. Wysocki" , Andy Shevchenko , "linux-kernel@vger.kernel.org" , "linux-gpio@vger.kernel.org" , "linux-acpi@vger.kernel.org" , Lee Jones , Linus Walleij , Alexandre Courbot , Len Brown , "sakari.ailus@linux.intel.com" Subject: RE: [PATCH v5 0/3] TPS68470 PMIC drivers Thread-Topic: [PATCH v5 0/3] TPS68470 PMIC drivers Thread-Index: AQHTAjEmBpYZO03MiEKheCBk2JA7n6Je2quAgABcawCAAVYhgIAAT/oAgC6/zTCAAIdngP//jJYAgBrA0IA= Date: Fri, 8 Sep 2017 00:45:59 +0000 Message-ID: <6F87890CF0F5204F892DEA1EF0D77A5972FBDA4A@FMSMSX114.amr.corp.intel.com> References: <1500648378-10294-1-git-send-email-rajmohan.mani@intel.com> <3425487.LgIRMVflim@aspire.rjw.lan> <2076994.J7nKrPWSDx@aspire.rjw.lan> <6F87890CF0F5204F892DEA1EF0D77A5972FA69A3@FMSMSX114.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.1.200.108] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id v880k9Ci012674 Content-Length: 2184 Lines: 66 Hi Rafael, > Subject: RE: [PATCH v5 0/3] TPS68470 PMIC drivers > > Hi Rafael, > > > >> > >> > This is the patch series for TPS68470 PMIC that works as a > > >> > >> > camera > > PMIC. > > >> > >> > > > >> > >> > The patch series provide the following 3 drivers, to help > > >> > >> > configure the > > >> voltage regulators, clocks and GPIOs provided by the TPS68470 PMIC, > > >> to be able to use the camera sensors connected to this PMIC. > > >> > >> > > > >> > >> > TPS68470 MFD driver: > > >> > >> > This is the multi function driver that initializes the > > >> > >> > TPS68470 PMIC and > > >> supports the GPIO and Op Region functions. > > >> > >> > > > >> > >> > TPS68470 GPIO driver: > > >> > >> > This is the PMIC GPIO driver that will be used by the OS > > >> > >> > GPIO layer, > > >> when the BIOS / firmware triggered GPIO access is done. > > >> > >> > > > >> > >> > TPS68470 Op Region driver: > > >> > >> > This is the driver that will be invoked, when the BIOS / > > >> > >> > firmware > > >> configures the voltage / clock for the sensors / vcm devices > > >> connected to the PMIC. > > >> > >> > > > >> > >> > > >> > >> All three patches are good to me (we did few rounds of > > >> > >> internal review before posting v4) > > >> > >> > > >> > >> Reviewed-by: Andy Shevchenko > > >> > > > > >> > > OK, so how should they be routed? > > >> > > > >> > Good question. I don't know how last time PMIC drivers were > > >> > merged, here I think is just sane to route vi MFD with immutable > > >> > branch created. > > >> > > >> OK > > >> > > >> I will assume that the series will go in through MFD then. > > >> > > > > > > Now that the MFD and GPIO patches of v6 of this series have been > > > applied > > on respective trees, can you advise the next steps for the ACPI / PMIC > > Opregion driver? > > > > Well, it would have been better to route the whole series through one tree. > > Now it's better to wait until the two other trees get merged and then > > apply the opregion patch. > > > > Ack. > Let me get back once the other 2 trees are merged. > Both MFD and GPIO patches of this series got merged upstream as of today. Thanks Raj