devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Scott Branden <scott.branden@broadcom.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Srinath Mannam <srinath.mannam@broadcom.com>,
	daniel.lezcano@linaro.org, Zhang Rui <rui.zhang@intel.com>,
	Eduardo Valentin <edubezval@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	Pramod Kumar <pramod.kumar@broadcom.com>
Subject: Re: [PATCH v4 1/3] dt-bindings: thermal: Add binding document for SR thermal
Date: Thu, 27 Sep 2018 13:59:43 -0500	[thread overview]
Message-ID: <20180927185943.GA31385@bogus> (raw)
In-Reply-To: <f20afabc-e712-8f35-8dd6-d42b9a0131f0@broadcom.com>

On Thu, Sep 27, 2018 at 11:00:33AM -0700, Scott Branden wrote:
> 
> 
> On 18-09-27 10:31 AM, Florian Fainelli wrote:
> > On 09/27/2018 10:27 AM, Rob Herring wrote:
> > > On Thu, Sep 27, 2018 at 09:06:41PM +0530, Srinath Mannam wrote:
> > > > From: Pramod Kumar <pramod.kumar@broadcom.com>
> > > > 
> > > > Add binding document for supported thermal implementation
> > > > in Stingray.
> > > > 
> > > > Signed-off-by: Pramod Kumar <pramod.kumar@broadcom.com>
> > > > Signed-off-by: Srinath Mannam <srinath.mannam@broadcom.com>
> > > > Reviewed-by: Ray Jui <ray.jui@broadcom.com>
> > > > Reviewed-by: Scott Branden <scott.branden@broadcom.com>
> > > > ---
> > > >   .../bindings/thermal/brcm,sr-thermal.txt           | 25 ++++++++++++++++++++++
> > > >   1 file changed, 25 insertions(+)
> > > >   create mode 100644 Documentation/devicetree/bindings/thermal/brcm,sr-thermal.txt
> > > > 
> > > > diff --git a/Documentation/devicetree/bindings/thermal/brcm,sr-thermal.txt b/Documentation/devicetree/bindings/thermal/brcm,sr-thermal.txt
> > > > new file mode 100644
> > > > index 0000000..717617b
> > > > --- /dev/null
> > > > +++ b/Documentation/devicetree/bindings/thermal/brcm,sr-thermal.txt
> > > > @@ -0,0 +1,25 @@
> > > > +* Broadcom Stingray Thermal
> > > > +
> > > > +This binding describes thermal sensors that is part of Stingray SoCs.
> > > > +
> > > > +Required properties:
> > > > +- compatible : Must be "brcm,sr-thermal"
> > > > +- reg : memory where tmon data will be available.
> > > > +- brcm,tmon-mask: A one cell bit mask of valid TMON sources.
> > > > +                  Each bit represents single TMON source.
> > > > +- brcm,max-crit-temp: Maximum supported critical temperature.
> > > We already have a defined binding for setting trip points.
> > Indeed, and if you have multiple TMONs, they would in premise possibly
> > each have a different critical trip point.
> Which may be a good reason to go back to our original bindings which were
> generic and had each sensor in its own node?

Perhaps. I wouldn't call it going back to your original, but rather 
defining a complete binding. Of course, if you don't need different trip 
points, then again that is just unnecessary bloat. But I can't argue 
whether you do or don't.

Rob

  reply	other threads:[~2018-09-27 18:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 15:36 [PATCH v4 0/3] Stingray thermal driver support Srinath Mannam
2018-09-27 15:36 ` [PATCH v4 1/3] dt-bindings: thermal: Add binding document for SR thermal Srinath Mannam
2018-09-27 17:27   ` Rob Herring
2018-09-27 17:31     ` Florian Fainelli
2018-09-27 18:00       ` Scott Branden
2018-09-27 18:59         ` Rob Herring [this message]
2018-09-27 19:49           ` Scott Branden
2018-09-27 15:36 ` [PATCH v4 2/3] arm64: dts: stingray: Add Stingray Thermal DT support Srinath Mannam
2018-09-27 15:36 ` [PATCH v4 3/3] thermal: broadcom: Add Stingray thermal driver Srinath Mannam

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=20180927185943.GA31385@bogus \
    --to=robh@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pramod.kumar@broadcom.com \
    --cc=rui.zhang@intel.com \
    --cc=scott.branden@broadcom.com \
    --cc=srinath.mannam@broadcom.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).