| 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: <5357D8CC.3080501@codeaurora.org> Date: Wed, 23 Apr 2014 10:14:20 -0500 From: Timur Tabi <timur@...eaurora.org> To: "Westerberg, Mika" <mika.westerberg@...el.com> CC: Mathias Nyman <mathias.nyman@...ux.intel.com>, Linus <linus.walleij@...aro.org>, Grant Likely <grant.likely@...retlab.ca>, lkml <linux-kernel@...r.kernel.org>, "Rafael J. Wysocki" <rafael.j.wysocki@...el.com> Subject: Re: [PATCH v3 1/1] pinctrl: add Intel BayTrail GPIO/pinctrl support Westerberg, Mika wrote: > It doesn't do any pin control nor muxing and I'm not sure if it is > required. Can you elaborate why you think pin muxing is required with > GpioIo/GpioInt resources? How are the pin muxes normally configured in ACPI? All of our GPIOs have a pinmux on them, and so if you want to use the pin for the non-default functionality, you need to configure the mux. Isn't that supposed to happen with the through the pinctrl driver? That is, when the kernel parses the ASL, and it seems a command to configure pin #3 to function #4, it calls the local pinctrl driver to do that? -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation. -- 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