From: Rob Herring <firstname.lastname@example.org>
To: Daniel Lezcano <email@example.com>
Cc: Amit Kucheria <firstname.lastname@example.org>,
Lukasz Luba <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>,
Stephen Boyd <email@example.com>,
Matthias Kaehlcke <firstname.lastname@example.org>,
Zhang Rui <email@example.com>,
Linux PM list <firstname.lastname@example.org>,
Subject: Re: [PATCH v3 3/3] dt-bindings: thermal: Add yaml bindings for thermal zones
Date: Tue, 31 Mar 2020 15:13:49 -0600 [thread overview]
Message-ID: <20200331211349.GA18149@bogus> (raw)
On Mon, Mar 30, 2020 at 03:07:53PM +0200, Daniel Lezcano wrote:
> Hi Amit,
> On 30/03/2020 12:34, Amit Kucheria wrote:
> [ ... ]
> >>> I don't know why it's not consistent with the actual code in
> >>> of-thermal.c, where there is even a comment stated: /* For now,
> >>> thermal framework supports only 1 sensor per zone */
> >>> I think this is the place where developers should be informed
> >>> about the limitation and not even try to put more sensors into
> >>> the list.
> >> That is a good point. I'm currently "porting" the existing
> >> binding as described in thermal.txt to yaml. If you look at some
> >> of the example (c) in there, the bindings allow many sensors to a
> >> zone mapping but the thermal core doesn't implement that
> >> functionality.
> >> So should we fix the core code or change the bindings? Thoughts -
> >> Rob, Daniel, Rui?
> > Rob, Daniel: Any comments? We don't have any concerns for Linux
> > backward compatibility since multiple sensors per zone isn't used
> > anywhere. But asking since bindings are supposed to be
> > OS-agnostic.
> IMO, we should remove it as it is not used anywhere.
> We still have to decide how we aggregate multiple sensors.
The schema only needs to pass what currently exists (assuming no
errors), so extending it later is fine with me.
next prev parent reply other threads:[~2020-03-31 21:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 6:34 [PATCH v3 0/3] Convert thermal bindings to yaml Amit Kucheria
2020-03-25 6:34 ` [PATCH v3 1/3] dt-bindings: thermal: Add yaml bindings for thermal sensors Amit Kucheria
2020-03-31 21:14 ` Rob Herring
2020-03-25 6:34 ` [PATCH v3 2/3] dt-bindings: thermal: Add yaml bindings for thermal cooling-devices Amit Kucheria
2020-03-25 10:21 ` Lukasz Luba
2020-03-25 15:28 ` Amit Kucheria
2020-03-31 21:16 ` Rob Herring
2020-03-25 6:34 ` [PATCH v3 3/3] dt-bindings: thermal: Add yaml bindings for thermal zones Amit Kucheria
2020-03-25 11:06 ` Lukasz Luba
2020-03-25 15:42 ` Amit Kucheria
2020-03-30 10:34 ` Amit Kucheria
2020-03-30 13:07 ` Daniel Lezcano
2020-03-31 21:13 ` Rob Herring [this message]
2020-03-31 21:20 ` Rob Herring
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.