From: Eduardo Valentin <edubezval-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Javi Merino <javi.merino-5wv7dgnIgG8@public.gmane.org>
Cc: Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rui.zang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
Zhang Rui <rui.zhang-ral2JQCrhuEAvxtiuMwx3w@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>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3 2/4] devicetree: bindings: let thermal-sensor point to other thermal zones
Date: Tue, 22 Mar 2016 08:13:34 -0700 [thread overview]
Message-ID: <20160322151333.GA2977@localhost.localdomain> (raw)
In-Reply-To: <20160321115511.GA6590@e104805>
On Mon, Mar 21, 2016 at 11:55:11AM +0000, Javi Merino wrote:
> On Wed, Mar 02, 2016 at 07:21:53PM -0800, Eduardo Valentin wrote:
> > On Mon, Jan 04, 2016 at 03:17:09PM +0100, Sascha Hauer wrote:
> > > On Wed, Nov 25, 2015 at 03:09:44PM +0000, Javi Merino wrote:
> > > > The thermal-sensor property of the thermal zone node accepts phandles to
> > > > thermal sensors. However, thermal zones can be created as an
> > > > +
> > > > + thermal-sensors = <&cpu_thermal &gpu_thermal &lcd_thermal>
> > >
> > > This seems inconsistent. Why can a thermal zone only have multiple
> > > thermal sensors when they are thermal zones themselves? Either we assume
> > > that one thermal zone has a single sensor or we assume that it can have
> > > multiple sensors, but this should not depend on the zone being a sub zone
> > > or not.
> > >
> > > I think the thermal-sensors property should always point to one or
> > > multiple sensors. I see no point in "This property either points to
> > > exactly one sensor or multiple other thermal zones (from which we only
> > > use the temperature)"
> >
> >
> > Agreed here. In fact, if we are going to allow thermal zones to be
> > treated as sensors, it means there should be no limits on what you put
> > of there, as long as all items have #thermal-sensor-cells. So, mixing
> > one (or more) regular sensors, with other thermal zones shall be
> > allowed, if we agree in this semantics.
>
> Eduardo, thanks for the review. There doesn't seem to be much
> interest in this and I currently have no time to work on it so I am
> dropping this series for the time being. I'm happy for this to be
> picked up by somebody else (or who knows, maybe I will be able to work
> on it again in the future).
Ok Javi, as this was one of the topics agreed for a change, I will take it over.
Thanks for your help.
>
> Javi
--
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: Eduardo Valentin <edubezval@gmail.com>
To: Javi Merino <javi.merino@arm.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
rui.zang@intel.com, Zhang Rui <rui.zhang@intel.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>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/4] devicetree: bindings: let thermal-sensor point to other thermal zones
Date: Tue, 22 Mar 2016 08:13:34 -0700 [thread overview]
Message-ID: <20160322151333.GA2977@localhost.localdomain> (raw)
In-Reply-To: <20160321115511.GA6590@e104805>
On Mon, Mar 21, 2016 at 11:55:11AM +0000, Javi Merino wrote:
> On Wed, Mar 02, 2016 at 07:21:53PM -0800, Eduardo Valentin wrote:
> > On Mon, Jan 04, 2016 at 03:17:09PM +0100, Sascha Hauer wrote:
> > > On Wed, Nov 25, 2015 at 03:09:44PM +0000, Javi Merino wrote:
> > > > The thermal-sensor property of the thermal zone node accepts phandles to
> > > > thermal sensors. However, thermal zones can be created as an
> > > > +
> > > > + thermal-sensors = <&cpu_thermal &gpu_thermal &lcd_thermal>
> > >
> > > This seems inconsistent. Why can a thermal zone only have multiple
> > > thermal sensors when they are thermal zones themselves? Either we assume
> > > that one thermal zone has a single sensor or we assume that it can have
> > > multiple sensors, but this should not depend on the zone being a sub zone
> > > or not.
> > >
> > > I think the thermal-sensors property should always point to one or
> > > multiple sensors. I see no point in "This property either points to
> > > exactly one sensor or multiple other thermal zones (from which we only
> > > use the temperature)"
> >
> >
> > Agreed here. In fact, if we are going to allow thermal zones to be
> > treated as sensors, it means there should be no limits on what you put
> > of there, as long as all items have #thermal-sensor-cells. So, mixing
> > one (or more) regular sensors, with other thermal zones shall be
> > allowed, if we agree in this semantics.
>
> Eduardo, thanks for the review. There doesn't seem to be much
> interest in this and I currently have no time to work on it so I am
> dropping this series for the time being. I'm happy for this to be
> picked up by somebody else (or who knows, maybe I will be able to work
> on it again in the future).
Ok Javi, as this was one of the topics agreed for a change, I will take it over.
Thanks for your help.
>
> Javi
next prev parent reply other threads:[~2016-03-22 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 15:09 [PATCH v3 0/4] Hierarchical thermal zones Javi Merino
2015-11-25 15:09 ` [PATCH v3 1/4] thermal: Add support for hierarchical " Javi Merino
2016-03-03 3:12 ` Eduardo Valentin
2016-03-03 3:23 ` Eduardo Valentin
2015-11-25 15:09 ` [PATCH v3 2/4] devicetree: bindings: let thermal-sensor point to other " Javi Merino
2015-11-25 17:54 ` Mark Rutland
2015-11-25 18:41 ` Javi Merino
2015-11-25 18:41 ` Javi Merino
2016-01-04 14:17 ` Sascha Hauer
2016-03-03 3:21 ` Eduardo Valentin
2016-03-21 11:55 ` Javi Merino
2016-03-22 15:13 ` Eduardo Valentin [this message]
2016-03-22 15:13 ` Eduardo Valentin
2016-03-03 3:19 ` Eduardo Valentin
2015-11-25 15:09 ` [PATCH v3 3/4] thermal: of: parse stacked thermal zones from device tree Javi Merino
2015-11-25 15:09 ` [PATCH v3 4/4] thermal: show the sub thermal zones in sysfs Javi Merino
2016-03-03 3:17 ` Eduardo Valentin
2016-03-16 22:06 ` Eduardo Valentin
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=20160322151333.GA2977@localhost.localdomain \
--to=edubezval-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=javi.merino-5wv7dgnIgG8@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=rui.zang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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.