Re: [PATCH v2 0/3] i2c-mux-gpio: Split plat- and dt-specific code up

2019-05-07 Thread Serge Semin
Hello Peter On Tue, May 07, 2019 at 09:17:38AM +, Peter Rosin wrote: > On 2019-05-07 11:02, Serge Semin wrote: > > Hello folks, > > > > Any updates on this patchset status? I haven't got any comment on v2, but > > instead a notification about the status change was sent to me: > > > >> *

Re: [PATCH v2 0/3] i2c-mux-gpio: Split plat- and dt-specific code up

2019-05-07 Thread Peter Rosin
On 2019-05-07 11:02, Serge Semin wrote: > Hello folks, > > Any updates on this patchset status? I haven't got any comment on v2, but > instead a notification about the status change was sent to me: > >> * linux-i2c: [v2,1/3] i2c-mux-gpio: Unpin a platform-based device >> initialization >> -

Re: [PATCH v2 0/3] i2c-mux-gpio: Split plat- and dt-specific code up

2019-05-07 Thread Serge Semin
Hello folks, Any updates on this patchset status? I haven't got any comment on v2, but instead a notification about the status change was sent to me: > * linux-i2c: [v2,1/3] i2c-mux-gpio: Unpin a platform-based device > initialization > - http://patchwork.ozlabs.org/patch/1091120/ > -

[PATCH v2 0/3] i2c-mux-gpio: Split plat- and dt-specific code up

2019-04-25 Thread Serge Semin
The main idea of this patchset was to add the full dt GPIOs specifier support in i2c-mux-gpio driver. In particular we needed to have the full GPIOs specifier being handled including the flags like GPIO_ACTIVE_HIGH, GPIO_ACTIVE_LOW, GPIO_PUSH_PULL, GPIO_OPEN_DRAIN or GPIO_OPEN_SOURCE. Due to using