Re: [PATCH v2 1/6] staging: fbtft: convert fbtft_reset() to be non-atomic

Den 02.01.2017 12:35, skrev Andy Shevchenko: First of all, fbtft in current state doesn't allow to override GPIOs to be optional, like "reset" one. It might be a bug somewhere, but rather out of scope of this fix. Second, not all GPIOs available on the board would be SoC based, some of them

Re: [PATCH v2 1/6] staging: fbtft: convert fbtft_reset() to be non-atomic

Den 02.01.2017 12:35, skrev Andy Shevchenko: First of all, fbtft in current state doesn't allow to override GPIOs to be optional, like "reset" one. It might be a bug somewhere, but rather out of scope of this fix. Second, not all GPIOs available on the board would be SoC based, some of them

[PATCH v2 1/6] staging: fbtft: convert fbtft_reset() to be non-atomic

First of all, fbtft in current state doesn't allow to override GPIOs to be optional, like "reset" one. It might be a bug somewhere, but rather out of scope of this fix. Second, not all GPIOs available on the board would be SoC based, some of them might sit on I2C GPIO expanders, for example, on

[PATCH v2 1/6] staging: fbtft: convert fbtft_reset() to be non-atomic

First of all, fbtft in current state doesn't allow to override GPIOs to be optional, like "reset" one. It might be a bug somewhere, but rather out of scope of this fix. Second, not all GPIOs available on the board would be SoC based, some of them might sit on I2C GPIO expanders, for example, on