linux-kernel - Re: [PATCH v2 3/3] mfd: wm831x: Add device tree binding document

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170222160949.GC2742@localhost.localdomain>
Date:   Wed, 22 Feb 2017 16:09:49 +0000
From:   Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
To:     Rob Herring <robh@...nel.org>
CC:     <lee.jones@...aro.org>, <mark.rutland@....com>,
        <linus.walleij@...aro.org>, <gnurou@...il.com>,
        <devicetree@...r.kernel.org>, <linux-gpio@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>,
        <patches@...nsource.wolfsonmicro.com>
Subject: Re: [PATCH v2 3/3] mfd: wm831x: Add device tree binding document

On Wed, Feb 22, 2017 at 09:15:02AM -0600, Rob Herring wrote:
> On Mon, Feb 13, 2017 at 11:15:14AM +0000, Charles Keepax wrote:
> > This is just a very simple initial binding, supporting only registering
> > the chip and the GPIOs. More features will be added as support for
> > device tree in the driver is expanded.
> 
> Please make the binding as complete as you can. You don't have to have 
> driver side support in place. Doesn't have to be everything, but at 
> least everything you know you will need.
> 

I am happy to flush the binding out with a bit more detail,
although the GPIOs are actually all I need to use at the moment.
I will send a new revision with some more detail. Do we normally
do anything to mark the bits of the binding that are currently
un-implemented?

Thanks,
Charles