On Saturday, July 22, 2017 08:15:33 PM Andy Shevchenko wrote: > On Fri, Jul 21, 2017 at 11:51 PM, Rafael J. Wysocki <rjw@xxxxxxxxxxxxx> wrote: > > On Friday, July 21, 2017 06:20:15 PM Andy Shevchenko wrote: > >> On Fri, Jul 21, 2017 at 5:46 PM, Rajmohan Mani <rajmohan.mani@xxxxxxxxx> wrote: > >> > 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 <andy.shevchenko@xxxxxxxxx> > > > > 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. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
