Re: [PATCH] gpio: mxs: Use set and clear capabilities of the gpio controller

2013-05-20 Thread Linus Walleij
On Mon, Apr 29, 2013 at 4:07 PM, Maxime Ripard wrote: > The current driver doesn't use the set and clear registers found on the > mxs gpio controller. > > This leads the generic gpio controller to be using some internal value > to avoid looking up the value stored in the registers, making it beha

Re: [PATCH] gpio: mxs: Use set and clear capabilities of the gpio controller

2013-05-16 Thread Maxime Ripard
Hi Linus, Le 02/05/2013 04:44, Shawn Guo a écrit : > On Mon, Apr 29, 2013 at 04:07:18PM +0200, Maxime Ripard wrote: >> The current driver doesn't use the set and clear registers found on the >> mxs gpio controller. >> >> This leads the generic gpio controller to be using some internal value >> to

Re: [PATCH] gpio: mxs: Use set and clear capabilities of the gpio controller

2013-05-01 Thread Shawn Guo
On Mon, Apr 29, 2013 at 04:07:18PM +0200, Maxime Ripard wrote: > The current driver doesn't use the set and clear registers found on the > mxs gpio controller. > > This leads the generic gpio controller to be using some internal value > to avoid looking up the value stored in the registers, making

[PATCH] gpio: mxs: Use set and clear capabilities of the gpio controller

2013-04-29 Thread Maxime Ripard
The current driver doesn't use the set and clear registers found on the mxs gpio controller. This leads the generic gpio controller to be using some internal value to avoid looking up the value stored in the registers, making it behave pretty much like a cache. This raises some coherency problem