Commit a0a99835 authored by David Brownell's avatar David Brownell Committed by Linus Torvalds

gpio calls don't need i/o barriers

Clarify that drivers using the GPIO operations don't need to issue io
barrier instructions themselves.  Previously this wasn't clear, and at
least one platform assumed otherwise (and would thus break various
otherwise-portable drivers which don't issue barriers).
Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent e53252d9
...@@ -75,6 +75,9 @@ using the include file: ...@@ -75,6 +75,9 @@ using the include file:
If you stick to this convention then it'll be easier for other developers to If you stick to this convention then it'll be easier for other developers to
see what your code is doing, and help maintain it. see what your code is doing, and help maintain it.
Note that these operations include I/O barriers on platforms which need to
use them; drivers don't need to add them explicitly.
Identifying GPIOs Identifying GPIOs
----------------- -----------------
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment