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 <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. > >> > > > > 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. Thanks Raj ��.n��������+%������w��{.n�����{�����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f