| 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: <74CDBE0F657A3D45AFBB94109FB122FF1740D74BC4@HQMAIL01.nvidia.com> Date: Thu, 17 Nov 2011 09:17:11 -0800 From: Stephen Warren <swarren@...dia.com> To: Linus Walleij <linus.walleij@...ricsson.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> CC: Grant Likely <grant.likely@...retlab.ca>, Barry Song <21cnbao@...il.com>, Shawn Guo <shawn.guo@...escale.com>, Thomas Abraham <thomas.abraham@...aro.org>, Dong Aisheng <dong.aisheng@...aro.org>, Rajendra Nayak <rajendra.nayak@...aro.org>, Linus Walleij <linus.walleij@...aro.org> Subject: RE: [PATCH v2] pinctrl: indicate GPIO direction on single GPIO request Linus Walleij wrote at Thursday, November 17, 2011 6:46 AM: > When requesting a single GPIO pin to be muxed in, some controllers > will need to poke a different value into the control register > depending on whether the pin will be used for GPIO output or GPIO > input. So pass this info along for the gpio_request_enable() > function, we assume this is not needed for the gpio_free_disable() > function for the time being. My most recent comments in the thread following the previous patch re: the need to expand the set of required pinctrl GPIO-related functions apply to this patch. -- nvpublic -- 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