From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Tyler Hall <tylerwhall@gmail.com>,
Eduardo Valentin <edubezval@gmail.com>
Cc: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-pm@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH] thermal: armada: read stable temp on Armada XP
Date: Wed, 25 Feb 2015 17:10:14 +0100 [thread overview]
Message-ID: <54EDF3E6.6040409@free-electrons.com> (raw)
In-Reply-To: <CAOjnSCaH5NtcYGdfQ+=XY9ZJtjYEEgLWKCGUeFXBsM1f+va-LA@mail.gmail.com>
Hi Tyler, Eduardo,
On 24/02/2015 20:56, Tyler Hall wrote:
> Eduardo,
>
> On Tue, Feb 24, 2015 at 1:36 PM, Eduardo Valentin <edubezval@gmail.com> wrote:
>> The fix seams reasonable. Although, it remains the question what is
>> applicability to other Armada chips? Besides, shouldn't we simply use it
>> by default? Also, do you plan to send updates in the DTS files?
>
> As far as I can tell, Armada 370 is already using the equivalent of
> this register I'd like to use in Armada XP. I'm not sure about the
> other mvebu platforms. I couldn't just change the device tree for XP
> to instantiate the 370 sensor, however, as they have different
> initialization routines. Possibly Eziquiel can comment on the
> significance of the differences between armadaxp_init_sensor() and
> armada370_init_sensor().
>
> I would like to change the default going forward, but I don't think it
> can be changed on platforms using an older DTB.
Here you introduced a new kind of thermal sensor, at least from the point
of view of the device tree. You used a new compatible string associated to
a different register.
By using it by default do you mean removing marvell,armadaxp-thermal
and adding armadaxp-filtered-thermal instead ?
Does that new thermal sensors only improve the stability or does it
also modify the value?
In the second case it will more or less break the user space expectation.
>
> I had planned to submit the dts change separately. It's not clear to
> me how that's supposed to be handled if they might go through
> different trees.
For this, there is no problem be handled in a different tree. At the end
we will need both the a new dts and a new driver to use it, so the fact that
the dts or the driver patch is merged in mainline first is not important.
Thanks,
Gregory
>
> Thanks,
> Tyler
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2015-02-25 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 22:50 [PATCH] thermal: armada: read stable temp on Armada XP Tyler Hall
2015-02-24 18:36 ` Eduardo Valentin
2015-02-24 19:56 ` Tyler Hall
2015-02-25 16:10 ` Gregory CLEMENT [this message]
2015-02-25 18:39 ` Eduardo Valentin
2015-02-25 19:47 ` Tyler Hall
2015-02-25 22:39 ` Tyler Hall
2015-02-25 17:04 ` Gregory CLEMENT
2015-02-25 18:17 ` Ezequiel Garcia
2015-02-25 18:38 ` Gregory CLEMENT
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=54EDF3E6.6040409@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=tylerwhall@gmail.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