All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Rob Herring <robh@kernel.org>, Markus Mayer <markus.mayer@broadcom.com>
Cc: Jean Delvare <jdelvare@suse.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Mark Rutland <mark.rutland@arm.com>,
	Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
	Linux HWMON List <linux-hwmon@vger.kernel.org>,
	Device Tree List <devicetree@vger.kernel.org>,
	ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt/bindings: Add bindings for Broadcom STB DRAM Sensors
Date: Thu, 27 Apr 2017 15:00:56 -0700	[thread overview]
Message-ID: <90f011d6-9241-e860-7a0e-2fb52c2337ce@gmail.com> (raw)
In-Reply-To: <20170427215737.dmnj4u2e4tfc6vfv@rob-hp-laptop>

On 04/27/2017 02:57 PM, Rob Herring wrote:
>>>> +  - reg: must reference the start address and length of the DCPU register
>>>> +    space
>>>> +
>>>> +Optional properties:
>>>> +  - cell-index: the index of the DPFE instance; will default to 0 if not set
> 
> Don't use cell-index. It's not a valid property for FDT (only real 
> OpenFirmware).

My bad, I was advising Markus to use this property since it was largely
used throughout Documentation/devicetree/bindings/. What would be a more
appropriate way to have the same information? Aliases?
-- 
Florian

WARNING: multiple messages have this Message-ID (diff)
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] dt/bindings: Add bindings for Broadcom STB DRAM Sensors
Date: Thu, 27 Apr 2017 15:00:56 -0700	[thread overview]
Message-ID: <90f011d6-9241-e860-7a0e-2fb52c2337ce@gmail.com> (raw)
In-Reply-To: <20170427215737.dmnj4u2e4tfc6vfv@rob-hp-laptop>

On 04/27/2017 02:57 PM, Rob Herring wrote:
>>>> +  - reg: must reference the start address and length of the DCPU register
>>>> +    space
>>>> +
>>>> +Optional properties:
>>>> +  - cell-index: the index of the DPFE instance; will default to 0 if not set
> 
> Don't use cell-index. It's not a valid property for FDT (only real 
> OpenFirmware).

My bad, I was advising Markus to use this property since it was largely
used throughout Documentation/devicetree/bindings/. What would be a more
appropriate way to have the same information? Aliases?
-- 
Florian

  reply	other threads:[~2017-04-27 22:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 20:17 [PATCH 0/2] HWMON driver for Broadcom STB DPFE Markus Mayer
2017-04-18 20:17 ` Markus Mayer
2017-04-18 20:17 ` Markus Mayer
2017-04-18 20:17 ` [PATCH 1/2] dt/bindings: Add bindings for Broadcom STB DRAM Sensors Markus Mayer
2017-04-18 20:17   ` Markus Mayer
2017-04-25 19:29   ` Markus Mayer
2017-04-25 19:29     ` Markus Mayer
2017-04-27 18:28     ` Markus Mayer
2017-04-27 18:28       ` Markus Mayer
2017-04-27 18:28       ` Markus Mayer
2017-04-27 21:57       ` Rob Herring
2017-04-27 21:57         ` Rob Herring
2017-04-27 21:57         ` Rob Herring
2017-04-27 22:00         ` Florian Fainelli [this message]
2017-04-27 22:00           ` Florian Fainelli
2017-05-03 22:29           ` Markus Mayer
2017-05-03 22:29             ` Markus Mayer
2017-05-03 22:29             ` Markus Mayer
2017-04-18 20:17 ` [PATCH 2/2] hwmon: (brcmstb) Add driver for Broadcom STB DPFE Markus Mayer
2017-04-18 20:17   ` Markus Mayer
2017-04-18 20:58   ` Guenter Roeck
2017-04-18 20:58     ` Guenter Roeck
2017-04-18 22:29     ` Florian Fainelli
2017-04-18 22:29       ` Florian Fainelli
2017-04-18 22:47       ` Guenter Roeck
2017-04-18 22:47         ` Guenter Roeck
2017-04-18 22:47         ` Guenter Roeck
2017-04-19  0:15         ` Markus Mayer
2017-04-19  0:15           ` Markus Mayer
2017-04-19  0:15           ` Markus Mayer
2017-04-19  0:26           ` Florian Fainelli
2017-04-19  0:26             ` Florian Fainelli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=90f011d6-9241-e860-7a0e-2fb52c2337ce@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mark.rutland@arm.com \
    --cc=markus.mayer@broadcom.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.