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: Tue, 10 May 2016 14:08:45 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: Christian Lamparter <chunkeey@...glemail.com> Cc: "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>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Álvaro Fernández Rojas <noltari@...il.com>, Kumar Gala <galak@...eaurora.org>, Alexander Shiyan <shc_work@...l.ru>, Ian Campbell <ijc+devicetree@...lion.org.uk>, Mark Rutland <mark.rutland@....com>, Pawel Moll <pawel.moll@....com>, Rob Herring <robh+dt@...nel.org>, Alexandre Courbot <gnurou@...il.com>, Andy Shevchenko <andy.shevchenko@...il.com> Subject: Re: [PATCH v8 2/3] gpio: mmio: add DT support for memory-mapped GPIOs On Sun, May 8, 2016 at 3:08 PM, Christian Lamparter <chunkeey@...glemail.com> wrote: > From: Álvaro Fernández Rojas <noltari@...il.com> > > This patch adds support for defining memory-mapped GPIOs which > are compatible with the existing gpio-mmio interface. Overall very nice, just waiting for the next version. > The first user for this binding is "wd,mbl-gpio". And that binding defines that we have a register named "dat". > + if (of_property_read_bool(dev->of_node, "no-output")) And then this too. Do we want these generic MMIO bindings (dat, no-output) in a special document like Documentation/devicetree/bindings/gpio/gpio-mmio.txt? Going forward? This patch set mainly deals with refactorings, but in the long run we want to slim things down a bit and use standard bindings I think. Yours, Linus Walleij
Powered by blists - more mailing lists