From: Guenter Roeck <linux@roeck-us.net>
To: Eduardo Valentin <edubezval@gmail.com>,
Linux PM <linux-pm@vger.kernel.org>
Cc: Caesar Wang <caesar.wang@rock-chips.com>, Wei Ni <wni@nvidia.com>,
Lukasz Majewski <l.majewski@samsung.com>,
Mikko Perttunen <mikko.perttunen@kapsi.fi>,
Alexandre Courbot <gnurou@gmail.com>,
devicetree@vger.kernel.org,
Grant Likely <grant.likely@linaro.org>,
Jean Delvare <jdelvare@suse.de>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
lm-sensors@lm-sensors.org, Rob Herring <robh+dt@kernel.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCHv5 1/1] thermal: of: improve of-thermal sensor registration API
Date: Thu, 20 Nov 2014 06:23:29 -0800 [thread overview]
Message-ID: <546DF961.3050509@roeck-us.net> (raw)
In-Reply-To: <20141120141806.GA1746@developer>
On 11/20/2014 06:18 AM, Eduardo Valentin wrote:
> Hi Guenter,
>
> On Thu, Nov 20, 2014 at 10:12:13AM -0400, Eduardo Valentin wrote:
>> Different drivers request API extensions in of-thermal. For this reason,
>> additional callbacks are required to fit the new drivers needs.
>>
>> The current API implementation expects the registering sensor driver
>> to provide a get_temp and get_trend callbacks as function parameters.
>> As the amount of callbacks is growing, this patch changes the existing
>> implementation to use a .ops field to hold all the of thermal callbacks
>> to sensor drivers.
>>
>> This patch also changes the existing of-thermal users to fit the new
>> API design. No functional change is introduced in this patch.
>>
>> Cc: Alexandre Courbot <gnurou@gmail.com>
>> Cc: devicetree@vger.kernel.org
>> Cc: Grant Likely <grant.likely@linaro.org>
>> Cc: Guenter Roeck <linux@roeck-us.net>
>> Cc: Jean Delvare <jdelvare@suse.de>
>> Cc: linux-kernel@vger.kernel.org
>> Cc: linux-pm@vger.kernel.org
>> Cc: linux-tegra@vger.kernel.org
>> Cc: lm-sensors@lm-sensors.org
>> Cc: Rob Herring <robh+dt@kernel.org>
>> Cc: Stephen Warren <swarren@wwwdotorg.org>
>> Cc: Thierry Reding <thierry.reding@gmail.com>
>> Cc: Zhang Rui <rui.zhang@intel.com>
>> Tested-by: Mikko Perttunen <mikko.perttunen@kapsi.fi>
>> Reviewed-by: Mikko Perttunen <mikko.perttunen@kapsi.fi>
>> Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
>> Reviewed-by: Lukasz Majewski <l.majewski@samsung.com>
>> Signed-off-by: Eduardo Valentin <edubezval@gmail.com>
>> ---
>> drivers/hwmon/lm75.c | 9 +++--
>> drivers/hwmon/ntc_thermistor.c | 6 +++-
>> drivers/hwmon/tmp102.c | 6 +++-
>
> Do you have objections if I queue this one for 3.19?
>
No.
Guenter
next prev parent reply other threads:[~2014-11-20 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1416492733-1624-1-git-send-email-edubezval@gmail.com>
2014-11-20 14:12 ` Eduardo Valentin
2014-11-20 14:18 ` Eduardo Valentin
2014-11-20 14:23 ` Guenter Roeck [this message]
2014-11-20 14:23 ` 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=546DF961.3050509@roeck-us.net \
--to=linux@roeck-us.net \
--cc=caesar.wang@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=gnurou@gmail.com \
--cc=grant.likely@linaro.org \
--cc=jdelvare@suse.de \
--cc=l.majewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mikko.perttunen@kapsi.fi \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=wni@nvidia.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
Powered by JetHome