All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Russell King <linux@arm.linux.org.uk>,
	Pavel Machek <pavel@ucw.cz>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: omap3: Include missing bandgap data for ti-soc-thermal driver
Date: Tue, 5 Jan 2016 12:30:20 +0100	[thread overview]
Message-ID: <20160105113020.GK22661@pali> (raw)
In-Reply-To: <20151231173844.GD11863@localhost.localdomain>

On Thursday 31 December 2015 09:38:45 Eduardo Valentin wrote:
> > +
> > +		bandgap {
> > +			reg = <0x48002524 0x4>;
> > +			compatible = "ti,omap36xx-bandgap";
> 
> Can you please already add on both cases
> 
> #thermal-sensor-cells = <0>;
> ?
> 
> This way we can already use them to define thermal zones. Of course,
> that alone won't add the thermal zones. A separated patch would be
> needed to add the thermal zone for OMAP3.

Are you going to add thermal zone defines? If yes, then it would make
sense to add that #thermal line together with thermal zone defines...

-- 
Pali Rohár
pali.rohar@gmail.com

WARNING: multiple messages have this Message-ID (diff)
From: "Pali Rohár" <pali.rohar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Eduardo Valentin <edubezval-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Ian Campbell
	<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
	Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ARM: dts: omap3: Include missing bandgap data for ti-soc-thermal driver
Date: Tue, 5 Jan 2016 12:30:20 +0100	[thread overview]
Message-ID: <20160105113020.GK22661@pali> (raw)
In-Reply-To: <20151231173844.GD11863-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

On Thursday 31 December 2015 09:38:45 Eduardo Valentin wrote:
> > +
> > +		bandgap {
> > +			reg = <0x48002524 0x4>;
> > +			compatible = "ti,omap36xx-bandgap";
> 
> Can you please already add on both cases
> 
> #thermal-sensor-cells = <0>;
> ?
> 
> This way we can already use them to define thermal zones. Of course,
> that alone won't add the thermal zones. A separated patch would be
> needed to add the thermal zone for OMAP3.

Are you going to add thermal zone defines? If yes, then it would make
sense to add that #thermal line together with thermal zone defines...

-- 
Pali Rohár
pali.rohar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
--
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

WARNING: multiple messages have this Message-ID (diff)
From: pali.rohar@gmail.com (Pali Rohár)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: omap3: Include missing bandgap data for ti-soc-thermal driver
Date: Tue, 5 Jan 2016 12:30:20 +0100	[thread overview]
Message-ID: <20160105113020.GK22661@pali> (raw)
In-Reply-To: <20151231173844.GD11863@localhost.localdomain>

On Thursday 31 December 2015 09:38:45 Eduardo Valentin wrote:
> > +
> > +		bandgap {
> > +			reg = <0x48002524 0x4>;
> > +			compatible = "ti,omap36xx-bandgap";
> 
> Can you please already add on both cases
> 
> #thermal-sensor-cells = <0>;
> ?
> 
> This way we can already use them to define thermal zones. Of course,
> that alone won't add the thermal zones. A separated patch would be
> needed to add the thermal zone for OMAP3.

Are you going to add thermal zone defines? If yes, then it would make
sense to add that #thermal line together with thermal zone defines...

-- 
Pali Roh?r
pali.rohar at gmail.com

  reply	other threads:[~2016-01-05 11:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-25 23:32 [PATCH] ARM: dts: omap3: Include missing bandgap data for ti-soc-thermal driver Pali Rohár
2015-12-25 23:32 ` Pali Rohár
2015-12-26 18:50 ` Pavel Machek
2015-12-26 18:50   ` Pavel Machek
2015-12-31 17:38 ` Eduardo Valentin
2015-12-31 17:38   ` Eduardo Valentin
2015-12-31 17:38   ` Eduardo Valentin
2016-01-05 11:30   ` Pali Rohár [this message]
2016-01-05 11:30     ` Pali Rohár
2016-01-05 11:30     ` Pali Rohár
2016-01-21  9:47 ` Pali Rohár
2016-01-21  9:47   ` Pali Rohár
2016-01-21 17:15   ` Tony Lindgren
2016-01-21 17:15     ` Tony Lindgren
2016-01-21 17:15     ` Tony Lindgren
2016-01-27 10:04     ` Pali Rohár
2016-01-27 10:04       ` Pali Rohár
2016-01-27 16:09       ` Tony Lindgren
2016-01-27 16:09         ` Tony Lindgren
2016-01-27 16:09         ` Tony Lindgren
2016-01-27 18:19         ` Sebastian Reichel
2016-01-27 18:19           ` Sebastian Reichel
2016-01-27 18:19           ` Sebastian Reichel
2016-01-27 18:24           ` Tony Lindgren
2016-01-27 18:24             ` Tony Lindgren
2016-01-27 18:24             ` Tony Lindgren

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=20160105113020.GK22661@pali \
    --to=pali.rohar@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pavel@ucw.cz \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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 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.