devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: jdelvare@suse.com, robh+dt@kernel.org, mark.rutland@arm.com,
	linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: hwmon: tmp108: add optional interrupts and #thermal-sensor-cells
Date: Wed, 7 Nov 2018 13:38:32 -0800	[thread overview]
Message-ID: <20181107213831.GA14140@roeck-us.net> (raw)
In-Reply-To: <5910167.PXNgySJWA7@diego>

On Wed, Nov 07, 2018 at 10:33:12PM +0100, Heiko Stübner wrote:
> Hi Guenter,
> 
> Am Mittwoch, 7. November 2018, 19:39:58 CET schrieb Guenter Roeck:
> > On Wed, Nov 07, 2018 at 04:47:08PM +0100, Heiko Stuebner wrote:
> > > From: Heiko Stuebner <heiko.stuebner@bq.com>
> > > 
> > > The tmp108 does have an alert output that can be used as interrupt source
> > > and can of course also be used as part of a thermal sensor setup for
> > > things
> > > like thermal-based cpu frequencies, so document the necessary properties.
> > > 
> > > Signed-off-by: Heiko Stuebner <heiko.stuebner@bq.com>
> > 
> > Do you also plan to actually implement interrupt support in the driver ?
> 
> Not right now but I'm hoping down the road.
> 
> The main argument for including this standard property is that
> the dt-binding is of course a description of the hardware and not the
> state of the linux driver and the tmp108 obviously has that alert output
> pin, hence I'd really like to already have it in the new board-dts I'm
> currently working on so it simply magically works once the driver can
> use it :-) .
> 
NP, just asking. Let's wait for Rob's review, then I'll apply the patch
unless he has issues.

Thanks,
Guenter

> 
> Heiko
> 
> > > ---
> > > 
> > >  Documentation/devicetree/bindings/hwmon/tmp108.txt | 4 ++++
> > >  1 file changed, 4 insertions(+)
> > > 
> > > diff --git a/Documentation/devicetree/bindings/hwmon/tmp108.txt
> > > b/Documentation/devicetree/bindings/hwmon/tmp108.txt index
> > > 8c4b10df86d9..54d4beed4ee5 100644
> > > --- a/Documentation/devicetree/bindings/hwmon/tmp108.txt
> > > +++ b/Documentation/devicetree/bindings/hwmon/tmp108.txt
> > > 
> > > @@ -7,6 +7,10 @@ Requires node properties:
> > >  - compatible : "ti,tmp108"
> > >  - reg : the I2C address of the device. This is 0x48, 0x49, 0x4a, or 0x4b.
> > > 
> > > +Optional properties:
> > > +- interrupts: Reference to the TMP108 alert interrupt.
> > > +- #thermal-sensor-cells: should be set to 0.
> > > +
> > > 
> > >  Example:
> > >  	tmp108@48 {
> > >  	
> > >  		compatible = "ti,tmp108";
> 
> 
> 
> 

  reply	other threads:[~2018-11-07 21:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 15:47 [PATCH] dt-bindings: hwmon: tmp108: add optional interrupts and #thermal-sensor-cells Heiko Stuebner
2018-11-07 18:39 ` Guenter Roeck
2018-11-07 21:33   ` Heiko Stübner
2018-11-07 21:38     ` Guenter Roeck [this message]
     [not found] ` <5bea0ecc.1c69fb81.e2af6.29c7@mx.google.com>
2018-11-13 17:32   ` Guenter Roeck

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=20181107213831.GA14140@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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 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).