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
| ||
|
Date: Wed, 29 Mar 2017 09:35:17 +0200 From: Geert Uytterhoeven <geert@...ux-m68k.org> To: Linus Walleij <linus.walleij@...aro.org> Cc: jacopo <jacopo@...ndi.org>, Jacopo Mondi <jacopo+renesas@...ndi.org>, Geert Uytterhoeven <geert+renesas@...der.be>, Laurent Pinchart <laurent.pinchart@...asonboard.com>, Chris Brandt <chris.brandt@...esas.com>, Rob Herring <robh+dt@...nel.org>, Mark Rutland <mark.rutland@....com>, Russell King <linux@...linux.org.uk>, Linux-Renesas <linux-renesas-soc@...r.kernel.org>, "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v2 2/7] dt-bindings: pinctrl: Add RZ/A1 bindings doc Hi Linus, On Wed, Mar 29, 2017 at 4:30 AM, Linus Walleij <linus.walleij@...aro.org> wrote: > On Tue, Mar 28, 2017 at 4:38 PM, <jacopo@...ndi.org> wrote: >>> The fact that historically all the early adopters of pinctrl in device >>> tree >>> have these funky custom bindings is unfortunate but just something >>> that we need to live with. >> >> To avoid any confusion, please bear with me and clarify this once and for >> all, >> since I'm not certain I fully got you here. >> >> Are you suggesting: >> >> 1) Use "pins" property with the currently implemented ABI (which slightly >> differs >> from the standard documented one as explained above. Not sure it is fine >> overriding >> it or not) > > Correction: you should be using the property "pinmux", because you > are setting group and function at the same time. OK. > See for example: > include/dt-bindings/pinctrl/mt65xx.h > > And how that is used in: > arch/arm/boot/dts/mt2701-pinfunc.h > arch/arm/boot/dts/mt2701-evb.dts > > The docs are here: > Documentation/devicetree/bindings/pinctrl/pinctrl-mt65xx.txt All of the above pack the information for a pin into a single 32-bit integer. Is that what you want us to use, too? Currently we use two integers: 1) pin index, and 2) function/flags combo. > I'm sorry that "pinmux" is not part of the generic documentation, it'd be > great if you would like to add it with a patch. That would mean pinmux could be an array of single values, or tuples. Is that OK? Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
Powered by blists - more mailing lists