Re: [PATCH 1/2] mtd: maps: physmap: Store gpio_values correctly

2019-03-28 Thread Chris Packham
On 28/03/19 9:32 PM, Boris Brezillon wrote: > On Thu, 28 Mar 2019 17:02:15 +1300 > Chris Packham wrote: > >> When the gpio-addr-flash.c driver was merged with physmap-core.c the >> code to store the current gpio_values was lost. This meant that once a >> gpio was asserted it was never

Re: [PATCH 1/2] mtd: maps: physmap: Store gpio_values correctly

2019-03-28 Thread Boris Brezillon
On Thu, 28 Mar 2019 17:02:15 +1300 Chris Packham wrote: > When the gpio-addr-flash.c driver was merged with physmap-core.c the > code to store the current gpio_values was lost. This meant that once a > gpio was asserted it was never de-asserted. Fix this by storing the > current offset in

[PATCH 1/2] mtd: maps: physmap: Store gpio_values correctly

2019-03-27 Thread Chris Packham
When the gpio-addr-flash.c driver was merged with physmap-core.c the code to store the current gpio_values was lost. This meant that once a gpio was asserted it was never de-asserted. Fix this by storing the current offset in gpio_values like the old driver used to. Fixes: commit ba32ce95cbd9