On Tue, Aug 4, 2015 at 2:03 PM, Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> wrote: > There is a hardware issue in Intel Baytrail where concurrent GPIO register > access might result reads of 0xffffffff and writes might get dropped > completely. > > Prevent this from happening by taking the serializing lock in all places > where it is possible that more than one thread might be accessing the > hardware concurrently. > > Signed-off-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> Patch applied. Same comment here about the fastpath and the RT raw spinlocks. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2/2] pinctrl: baytrail: Serialize all register access
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 2/2] pinctrl: baytrail: Serialize all register access
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Thu, 13 Aug 2015 14:26:49 +0200
- In-reply-to: <1438689794-14355-2-git-send-email-mika.westerberg@linux.intel.com>
- References:
- [PATCH 1/2] pinctrl: baytrail: Drop FSF mailing address
- From: Mika Westerberg
- [PATCH 2/2] pinctrl: baytrail: Serialize all register access
- From: Mika Westerberg
- [PATCH 1/2] pinctrl: baytrail: Drop FSF mailing address
- Prev by Date: Re: [PATCH 1/2] pinctrl: baytrail: Drop FSF mailing address
- Next by Date: Re: [PATCH v2 0/6] ARM: shmobile: Move gpio ranges from C code to DT
- Previous by thread: [PATCH 2/2] pinctrl: baytrail: Serialize all register access
- Next by thread: Re: [PATCH 2/2] pinctrl: baytrail: Serialize all register access
- Index(es):
 |