Re: [PATCH v2] iio: adc: sun4i-gpadc-iio: fix parent device being used in devm function

On Sun, 21 May 2017 21:06:32 +0200 Corentin Labbe wrote: > On Thu, May 18, 2017 at 08:36:07AM +0200, Quentin Schulz wrote: > > For the sake of DT binding stability, this IIO driver is a child of an > > MFD driver for Allwinner A10, A13 and A31 because there already

Re: [PATCH v2] iio: adc: sun4i-gpadc-iio: fix parent device being used in devm function

On Sun, 21 May 2017 21:06:32 +0200 Corentin Labbe wrote: > On Thu, May 18, 2017 at 08:36:07AM +0200, Quentin Schulz wrote: > > For the sake of DT binding stability, this IIO driver is a child of an > > MFD driver for Allwinner A10, A13 and A31 because there already exists a > > DT binding for

Re: [PATCH v2] iio: adc: sun4i-gpadc-iio: fix parent device being used in devm function

On Thu, May 18, 2017 at 08:36:07AM +0200, Quentin Schulz wrote: > For the sake of DT binding stability, this IIO driver is a child of an > MFD driver for Allwinner A10, A13 and A31 because there already exists a > DT binding for this IP. The MFD driver has a DT node but the IIO driver > does not.

Re: [PATCH v2] iio: adc: sun4i-gpadc-iio: fix parent device being used in devm function

On Thu, May 18, 2017 at 08:36:07AM +0200, Quentin Schulz wrote: > For the sake of DT binding stability, this IIO driver is a child of an > MFD driver for Allwinner A10, A13 and A31 because there already exists a > DT binding for this IP. The MFD driver has a DT node but the IIO driver > does not.

Re: [PATCH v2] iio: adc: sun4i-gpadc-iio: fix parent device being used in devm function

On 18/05/17 07:51, Maxime Ripard wrote: On Thu, May 18, 2017 at 08:36:07AM +0200, Quentin Schulz wrote: For the sake of DT binding stability, this IIO driver is a child of an MFD driver for Allwinner A10, A13 and A31 because there already exists a DT binding for this IP. The MFD driver has a DT

Re: [PATCH v2] iio: adc: sun4i-gpadc-iio: fix parent device being used in devm function

On 18/05/17 07:51, Maxime Ripard wrote: On Thu, May 18, 2017 at 08:36:07AM +0200, Quentin Schulz wrote: For the sake of DT binding stability, this IIO driver is a child of an MFD driver for Allwinner A10, A13 and A31 because there already exists a DT binding for this IP. The MFD driver has a DT

Re: [PATCH v2] iio: adc: sun4i-gpadc-iio: fix parent device being used in devm function

On Thu, May 18, 2017 at 08:36:07AM +0200, Quentin Schulz wrote: > For the sake of DT binding stability, this IIO driver is a child of an > MFD driver for Allwinner A10, A13 and A31 because there already exists a > DT binding for this IP. The MFD driver has a DT node but the IIO driver > does not.

Re: [PATCH v2] iio: adc: sun4i-gpadc-iio: fix parent device being used in devm function

On Thu, May 18, 2017 at 08:36:07AM +0200, Quentin Schulz wrote: > For the sake of DT binding stability, this IIO driver is a child of an > MFD driver for Allwinner A10, A13 and A31 because there already exists a > DT binding for this IP. The MFD driver has a DT node but the IIO driver > does not.

[PATCH v2] iio: adc: sun4i-gpadc-iio: fix parent device being used in devm function

For the sake of DT binding stability, this IIO driver is a child of an MFD driver for Allwinner A10, A13 and A31 because there already exists a DT binding for this IP. The MFD driver has a DT node but the IIO driver does not. The IIO device registers the temperature sensor in the thermal

[PATCH v2] iio: adc: sun4i-gpadc-iio: fix parent device being used in devm function

For the sake of DT binding stability, this IIO driver is a child of an MFD driver for Allwinner A10, A13 and A31 because there already exists a DT binding for this IP. The MFD driver has a DT node but the IIO driver does not. The IIO device registers the temperature sensor in the thermal