From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Fainelli Subject: Re: [PATCH v2 1/2] dt/bindings: Add bindings for Broadcom STB DRAM Sensors Date: Wed, 21 Jun 2017 13:44:53 -0700 Message-ID: <7128c063-1b3d-9cfb-71c6-f4590dac5e09@gmail.com> References: <20170613223710.31719-1-code@mmayer.net> <20170613223710.31719-2-code@mmayer.net> <20170618140529.wtqffjuilrkarzvd@rob-hp-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-US Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Markus Mayer , Rob Herring Cc: Mark Rutland , Florian Fainelli , Gregory Fong , Markus Mayer , Broadcom Kernel List , Device Tree List , ARM Kernel List , Linux Kernel Mailing List List-Id: devicetree@vger.kernel.org On 06/19/2017 10:26 AM, Markus Mayer wrote: > On 18 June 2017 at 07:05, Rob Herring wrote: >> On Tue, Jun 13, 2017 at 03:37:09PM -0700, Markus Mayer wrote: >>> From: Markus Mayer >>> >>> Provide bindings for the Broadcom STB DDR PHY Front End (DPFE). >>> >>> Signed-off-by: Markus Mayer >>> --- >>> .../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 > > 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? Would aliases work for instance for that purpose? -- Florian -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html