Re: [PATCH v2] regulator: arizona-ldo1: Use correct device to get enable GPIO

2018-06-29 Thread Linus Walleij
On Tue, Jun 19, 2018 at 5:10 PM Charles Keepax wrote: > Currently the enable GPIO is being looked up on the regulator > device itself but that does not have its own DT node, this causes > the lookup to fail and the regulator not to get its GPIO. The DT > node is shared across the whole MFD and as

Re: [PATCH v2] regulator: arizona-ldo1: Use correct device to get enable GPIO

2018-06-20 Thread Charles Keepax
On Tue, Jun 19, 2018 at 11:46:36PM +0300, Andy Shevchenko wrote: > On Tue, Jun 19, 2018 at 6:10 PM, Charles Keepax > wrote: > > Currently the enable GPIO is being looked up on the regulator > > device itself but that does not have its own DT node, this causes > > the lookup to fail and the regulat

Re: [PATCH v2] regulator: arizona-ldo1: Use correct device to get enable GPIO

2018-06-19 Thread Andy Shevchenko
On Tue, Jun 19, 2018 at 6:10 PM, Charles Keepax wrote: > Currently the enable GPIO is being looked up on the regulator > device itself but that does not have its own DT node, this causes > the lookup to fail and the regulator not to get its GPIO. The DT > node is shared across the whole MFD and as

[PATCH v2] regulator: arizona-ldo1: Use correct device to get enable GPIO

2018-06-19 Thread Charles Keepax
Currently the enable GPIO is being looked up on the regulator device itself but that does not have its own DT node, this causes the lookup to fail and the regulator not to get its GPIO. The DT node is shared across the whole MFD and as such the lookup needs to happen on that parent device. Moving t