linux-kernel - Re: [PATCH v2 1/2] dt/bindings: Add bindings for Broadcom STB DRAM Sensors

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 for Android: free password hash cracker in your pocket

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

Date:   Mon, 19 Jun 2017 10:26:49 -0700
From:   Markus Mayer <code@...yer.net>
To:     Rob Herring <robh@...nel.org>
Cc:     Markus Mayer <code@...yer.net>,
        Mark Rutland <mark.rutland@....com>,
        Florian Fainelli <f.fainelli@...il.com>,
        Gregory Fong <gregory.0xf0@...il.com>,
        Markus Mayer <mmayer@...adcom.com>,
        Broadcom Kernel List <bcm-kernel-feedback-list@...adcom.com>,
        Device Tree List <devicetree@...r.kernel.org>,
        ARM Kernel List <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] dt/bindings: Add bindings for Broadcom STB DRAM Sensors

On 18 June 2017 at 07:05, Rob Herring <robh@...nel.org> wrote:
> On Tue, Jun 13, 2017 at 03:37:09PM -0700, Markus Mayer wrote:
>> From: Markus Mayer <mmayer@...adcom.com>
>>
>> Provide bindings for the Broadcom STB DDR PHY Front End (DPFE).
>>
>> Signed-off-by: Markus Mayer <mmayer@...adcom.com>
>> ---
>>  .../devicetree/bindings/soc/bcm/brcm,dpfe-cpu.txt  | 27 ++++++++++++++++++++++
>>  1 file changed, 27 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,dpfe-cpu.txt
>
> Acked-by: Rob Herring <robh@...nel.org>

Thanks, Rob.

To bring up the previous discussion regarding enumerating multiple
nodes (so far we need two dpfe nodes for some platforms), how should
we go about this? We were originally proposing to use "cell-index",
but you said this was OpenFirmware only and couldn't be used in device
tree. See https://lkml.org/lkml/2017/4/27/574.

We do need to use something, because the driver needs to know if it
should be accessing dpfe0 or dpfe1. What should we use?

Thanks,
-Markus