Re: [PATCH v2 5/6] gpio-exar/8250-exar: Make set of exported GPIOs configurable

2017-05-22 Thread Jan Kiszka
On 2017-05-22 18:33, Andy Shevchenko wrote: > On Sun, May 21, 2017 at 2:43 PM, Jan Kiszka wrote: >> On 2017-05-18 19:43, Andy Shevchenko wrote: >>> On Thu, May 18, 2017 at 5:59 PM, Jan Kiszka wrote: On the SIMATIC, IOT2040 only a single pin is exportable as GPIO, the > + pdata.fi

Re: [PATCH v2 5/6] gpio-exar/8250-exar: Make set of exported GPIOs configurable

2017-05-22 Thread Andy Shevchenko
On Sun, May 21, 2017 at 2:43 PM, Jan Kiszka wrote: > On 2017-05-18 19:43, Andy Shevchenko wrote: >> On Thu, May 18, 2017 at 5:59 PM, Jan Kiszka wrote: >>> On the SIMATIC, IOT2040 only a single pin is exportable as GPIO, the >>> + pdata.first_gpio = first_gpio; >>> + pdata.ngpio = ngp

Re: [PATCH v2 5/6] gpio-exar/8250-exar: Make set of exported GPIOs configurable

2017-05-22 Thread Linus Walleij
On Thu, May 18, 2017 at 4:59 PM, Jan Kiszka wrote: > On the SIMATIC, IOT2040 only a single pin is exportable as GPIO, the > rest is required to operate the UART. To allow modeling this case, > expand the platform device data structure to specify a (consecutive) pin > subset for exporting by the g

Re: [PATCH v2 5/6] gpio-exar/8250-exar: Make set of exported GPIOs configurable

2017-05-21 Thread Jan Kiszka
On 2017-05-18 19:43, Andy Shevchenko wrote: > On Thu, May 18, 2017 at 5:59 PM, Jan Kiszka wrote: >> On the SIMATIC, IOT2040 only a single pin is exportable as GPIO, the >> rest is required to operate the UART. To allow modeling this case, >> expand the platform device data structure to specify a (

Re: [PATCH v2 5/6] gpio-exar/8250-exar: Make set of exported GPIOs configurable

2017-05-18 Thread Andy Shevchenko
On Thu, May 18, 2017 at 5:59 PM, Jan Kiszka wrote: > On the SIMATIC, IOT2040 only a single pin is exportable as GPIO, the > rest is required to operate the UART. To allow modeling this case, > expand the platform device data structure to specify a (consecutive) pin > subset for exporting by the gp