linux-kernel - Re: [PATCH 1/2] dt-bindings: nvmem: Add binding for RAVE SP EEPROM driver

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: <CAHQ1cqFegg3K6rQ6m0KC1Ns_bL+CMv1gSUne8bKDuirA-dw1ow@mail.gmail.com>
Date:   Tue, 10 Apr 2018 17:12:40 -0700
From:   Andrey Smirnov <andrew.smirnov@...il.com>
To:     Rob Herring <robh@...nel.org>
Cc:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Chris Healy <cphealy@...il.com>,
        Lucas Stach <l.stach@...gutronix.de>,
        Aleksander Morgado <aleksander@...ksander.es>,
        Mark Rutland <mark.rutland@....com>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: nvmem: Add binding for RAVE SP EEPROM driver

On Mon, Mar 26, 2018 at 3:24 PM, Rob Herring <robh@...nel.org> wrote:
> On Wed, Mar 21, 2018 at 06:47:09AM -0700, Andrey Smirnov wrote:
>> Add Device Tree bindings for RAVE SP EEPROM driver - an MFD cell of
>> parent RAVE SP driver (documented in
>> Documentation/devicetree/bindings/mfd/zii,rave-sp.txt).
>
> I'd prefer to get all the child nodes at once rather than as you
> upstream the drivers. IOW, please completely describe the device. Then I
> may have opinions on whether you need these child nodes or not.
>

OK, I currently don't have any other child drivers that can be
submitted (no code or bindings exist) that haven't already been
submitted/accepted. However I'll make sure to bundle all of the
remaining bindings in a single set and send it for review once I
finish them.

>
>> Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
>> Cc: linux-kernel@...r.kernel.org
>> Cc: Chris Healy <cphealy@...il.com>
>> Cc: Lucas Stach <l.stach@...gutronix.de>
>> Cc: Aleksander Morgado <aleksander@...ksander.es>
>> Cc: Rob Herring <robh+dt@...nel.org>
>> Cc: Mark Rutland <mark.rutland@....com>
>> Cc: devicetree@...r.kernel.org
>> Signed-off-by: Andrey Smirnov <andrew.smirnov@...il.com>
>> ---
>>  .../bindings/nvmem/zii,rave-sp-eeprom.txt          | 23 ++++++++++++++++++++++
>>  1 file changed, 23 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/nvmem/zii,rave-sp-eeprom.txt
>>
>> diff --git a/Documentation/devicetree/bindings/nvmem/zii,rave-sp-eeprom.txt b/Documentation/devicetree/bindings/nvmem/zii,rave-sp-eeprom.txt
>> new file mode 100644
>> index 000000000000..556abfa70524
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/nvmem/zii,rave-sp-eeprom.txt
>> @@ -0,0 +1,23 @@
>> +Zodiac Inflight Innovations RAVE EEPROM Bindings
>> +
>> +RAVE SP EEPROM device is a "MFD cell" device exposing physical EEPROM
>> +attached to RAVE Supervisory Processor. It is expected that its Device
>> +Tree node is specified as a child of the node corresponding to the
>> +parent RAVE SP device (as documented in
>> +Documentation/devicetree/bindings/mfd/zii,rave-sp.txt)
>> +
>> +Required properties:
>> +
>> +- compatible: Should be "zii,rave-sp-eeprom"
>> +
>> +Example:
>> +
>> +     rave-sp {
>> +             compatible = "zii,rave-sp-rdu1";
>> +             current-speed = <38400>;
>> +
>> +             dds-eeprom {
>> +                     compatible = "zii,rave-sp-eeprom";
>> +                     reg = <0xA3 0x2000>;
>
> Child nodes? #nvmem-cells? I assume you have some data in this you need.
> If not, you don't really need a child node here.
>

Yes, good point. Sorry about that, I should've included a better
example. Will fix in v2.

Thanks,
Andrey Smirnov