| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1366965558-6619-1-git-send-email-linus.walleij@linaro.org> Date: Fri, 26 Apr 2013 10:39:18 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: linux-kernel@...r.kernel.org Cc: Linus Walleij <linus.walleij@...aro.org> Subject: [PATCH] pinctrl: generic: clarify output configuration This makes it more clear what this generic control means. Reported-by: Laurent Pinchart <laurent.pinchart@...asonboard.com> Signed-off-by: Linus Walleij <linus.walleij@...aro.org> --- include/linux/pinctrl/pinconf-generic.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/include/linux/pinctrl/pinconf-generic.h b/include/linux/pinctrl/pinconf-generic.h index 72474e1..babd4a4 100644 --- a/include/linux/pinctrl/pinconf-generic.h +++ b/include/linux/pinctrl/pinconf-generic.h @@ -70,7 +70,9 @@ * passed in the argument on a custom form, else just use argument 1 * to indicate low power mode, argument 0 turns low power mode off. * @PIN_CONFIG_OUTPUT: this will configure the pin in output, use argument - * 1 to indicate high level, argument 0 to indicate low level. + * 1 to indicate high level, argument 0 to indicate low level. This + * is used when the drive type is unknown or irrelevant, such as when + * connecting a pin to GND or VDD during sleep. * @PIN_CONFIG_END: this is the last enumerator for pin configurations, if * you need to pass in custom configurations to the pin controller, use * PIN_CONFIG_END+1 as the base offset. -- 1.8.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists