From: David Brownell Date: Thu, 19 Jul 2007 08:47:52 +0000 (-0700) Subject: gpio calls don't need i/o barriers X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=a0a9983509f45b2225ca87fdcf7b40ea916834ed;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git 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: David Brownell Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds --- diff --git a/Documentation/gpio.txt b/Documentation/gpio.txt index 36af58eba136..218a8650f48d 100644 --- a/Documentation/gpio.txt +++ b/Documentation/gpio.txt @@ -75,6 +75,9 @@ using the include file: 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. +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 -----------------