summaryrefslogtreecommitdiff
path: root/scripts/Makefile.modinst
diff options
context:
space:
mode:
authorLinus Walleij <linus.walleij@linaro.org>2013-03-15 12:01:20 +0100
committerLinus Walleij <linus.walleij@linaro.org>2013-03-18 11:03:29 +0100
commitfdba2d065cb2891b3006424b50fbc6406ce66672 (patch)
treec39f081800ad2d650deada201a6e89d1f1b419a4 /scripts/Makefile.modinst
parent9cca1173594dccc67c50f0530dc5743fa395da67 (diff)
downloadlinux-exynos-fdba2d065cb2891b3006424b50fbc6406ce66672.tar.gz
linux-exynos-fdba2d065cb2891b3006424b50fbc6406ce66672.tar.bz2
linux-exynos-fdba2d065cb2891b3006424b50fbc6406ce66672.zip
pinctrl: document the "GPIO mode" pitfall
Recently as adoption of the pinctrl framework is reaching niches where the pins are reconfigured during system sleep and datasheets often talk about something called "GPIO mode", some engineers become confused by this, thinking that since it is named "GPIO (something something)" it must be modeled in the kernel using <linux/gpio.h>. To clarify things, let's put in this piece of documentation, or just start off the discussion here. Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Cc: Pankaj Dev <pankaj.dev@st.com> Reviewed-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'scripts/Makefile.modinst')
0 files changed, 0 insertions, 0 deletions