Re: [PATCH] pinctrl: cherryview: Serialize all register access

2015-08-13 Thread Mika Westerberg
On Thu, Aug 13, 2015 at 01:24:13PM +0200, Linus Walleij wrote: > On Mon, Aug 3, 2015 at 11:46 AM, Mika Westerberg > wrote: > > > There is a hardware issue in Intel Braswell/Cherryview where concurrent > > GPIO register access might results reads of 0x and writes might get > > dropped. >

Re: [PATCH] pinctrl: cherryview: Serialize all register access

2015-08-13 Thread Linus Walleij
On Mon, Aug 3, 2015 at 11:46 AM, Mika Westerberg wrote: > There is a hardware issue in Intel Braswell/Cherryview where concurrent > GPIO register access might results reads of 0x and writes might get > dropped. > > Prevent this from happening by taking the serializing lock for all places

Re: [PATCH] pinctrl: cherryview: Serialize all register access

2015-08-13 Thread Linus Walleij
On Mon, Aug 3, 2015 at 11:46 AM, Mika Westerberg mika.westerb...@linux.intel.com wrote: There is a hardware issue in Intel Braswell/Cherryview where concurrent GPIO register access might results reads of 0x and writes might get dropped. Prevent this from happening by taking the

Re: [PATCH] pinctrl: cherryview: Serialize all register access

2015-08-13 Thread Mika Westerberg
On Thu, Aug 13, 2015 at 01:24:13PM +0200, Linus Walleij wrote: On Mon, Aug 3, 2015 at 11:46 AM, Mika Westerberg mika.westerb...@linux.intel.com wrote: There is a hardware issue in Intel Braswell/Cherryview where concurrent GPIO register access might results reads of 0x and writes

[PATCH] pinctrl: cherryview: Serialize all register access

2015-08-03 Thread Mika Westerberg
There is a hardware issue in Intel Braswell/Cherryview where concurrent GPIO register access might results reads of 0x and writes might get dropped. Prevent this from happening by taking the serializing lock for all places where it is possible that more than one thread might be accessing

[PATCH] pinctrl: cherryview: Serialize all register access

2015-08-03 Thread Mika Westerberg
There is a hardware issue in Intel Braswell/Cherryview where concurrent GPIO register access might results reads of 0x and writes might get dropped. Prevent this from happening by taking the serializing lock for all places where it is possible that more than one thread might be accessing