Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751081AbdFSR0w (ORCPT ); Mon, 19 Jun 2017 13:26:52 -0400 Received: from mail-ua0-f194.google.com ([209.85.217.194]:33074 "EHLO mail-ua0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750979AbdFSR0v (ORCPT ); Mon, 19 Jun 2017 13:26:51 -0400 MIME-Version: 1.0 In-Reply-To: <20170618140529.wtqffjuilrkarzvd@rob-hp-laptop> References: <20170613223710.31719-1-code@mmayer.net> <20170613223710.31719-2-code@mmayer.net> <20170618140529.wtqffjuilrkarzvd@rob-hp-laptop> From: Markus Mayer Date: Mon, 19 Jun 2017 10:26:49 -0700 X-Google-Sender-Auth: cLw-u9AM6kahN5L2HoeC0khZLHo Message-ID: Subject: Re: [PATCH v2 1/2] dt/bindings: Add bindings for Broadcom STB DRAM Sensors To: Rob Herring Cc: Markus Mayer , Mark Rutland , Florian Fainelli , Gregory Fong , Markus Mayer , Broadcom Kernel List , Device Tree List , ARM Kernel List , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1030 Lines: 27 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? Thanks, -Markus