devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Wendy Ng" <wendy.ng@broadcom.com>
To: Matt Porter <matt.porter@linaro.org>
Cc: Rob Herring <rob.herring@calxeda.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, Christian Daudt <bcm@fixthebug.org>,
	Markus Mayer <mmayer@broadcom.com>
Subject: Re: [PATCH 1/3] thermal: bcm281xx: Add thermal driver
Date: Fri, 27 Sep 2013 15:49:52 -0700	[thread overview]
Message-ID: <52460B90.5060907@broadcom.com> (raw)
In-Reply-To: <20130925192609.GB25191@ohporter.com>


On 9/25/2013 12:26 PM, Matt Porter wrote:
> On Mon, Sep 23, 2013 at 10:51:36AM -0700, Wendy Ng wrote:
>> This adds the support for reading out temperature from Broadcom bcm281xx
>> SoCs.
>>
>> Signed-off-by: Wendy Ng <wendy.ng@broadcom.com>
>> Reviewed-by: Markus Mayer <mmayer@broadcom.com>
>> Reviewed-by: Christian Daudt <csd@broadcom.com>
>> ---
>>   .../bindings/thermal/bcm-kona-thermal.txt          |   18 +++
>>   drivers/thermal/Kconfig                            |   10 ++
>>   drivers/thermal/Makefile                           |    1 +
>>   drivers/thermal/bcm_thermal.c                      |  170 ++++++++++++++++++++
>>   4 files changed, 199 insertions(+)
>>   create mode 100644 Documentation/devicetree/bindings/thermal/bcm-kona-thermal.txt
>>   create mode 100644 drivers/thermal/bcm_thermal.c
>>
>> diff --git a/Documentation/devicetree/bindings/thermal/bcm-kona-thermal.txt b/Documentation/devicetree/bindings/thermal/bcm-kona-thermal.txt
>> new file mode 100644
>> index 0000000..acca99e
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/thermal/bcm-kona-thermal.txt
>> @@ -0,0 +1,18 @@
>> +* Broadcom Kona Thermal Management Unit
>> +
>> +This version is for the BCM281xx family of SoCs.
>> +
>> +Required properties:
>> +- compatible : "brcm,bcm11351-thermal", "brcm,kona-thermal"
>> +- reg : Address range of the thermal register
>> +- thermal-name: this entry must be specified and it will be passed into
>> +thermal_zone_device_register().  This name will also be reported under Hwmon
>> +sysfs 'name' attribute.
>> +
>> +Example:
>> +	thermal@34008000 {
>> +		compatible = "brcm,bcm11351-thermal", "brcm,kona-thermal";
>> +		reg = <0x34008000 0x0024>;
>> +		thermal-name = "bcm_kona_therm";
>> +		status = "disabled";
>> +	};
>> diff --git a/drivers/thermal/Kconfig b/drivers/thermal/Kconfig
>> index dbfc390..7f823f0 100644
>> --- a/drivers/thermal/Kconfig
>> +++ b/drivers/thermal/Kconfig
>> @@ -134,6 +134,16 @@ config KIRKWOOD_THERMAL
>>   	  Support for the Kirkwood thermal sensor driver into the Linux thermal
>>   	  framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
>>   
>> +config BCM_THERMAL
>> +	tristate "Temperature sensor on Broadcom BCM281xx family of SoCs"
>> +	depends on ARCH_BCM
> Hi Wendy,
>
> I just noticed that, depending on acceptance, this could collide with
> Christian's ARCH_BCM->ARCH_BCM_MOBILE rename that is expected to go into
> 3.13. I'm not sure if this series is targeted for 3.13 (due to the discussion
> about Eduardo's subsystem changes that impact it). If it is, you might
> want to rebase on Christian's rename series
> http://www.spinics.net/lists/arm-kernel/msg274963.html and use
> ARCH_BCM_MOBILE here.
>
> -Matt
Hi Matt,

I have uploaded v2 of this thermal driver patch series to make it 
compatible with Christian's
ARCH_BCM->ARCH_BCM_MOBILE changes.

Thanks for pointing this out!

>> +	default y
>> +	help
>> +	  If you say yes here you get support for TMU (Thermal Management
>> +	  Unit) on Broadcom BCM281xx family of SoCs. This provides thermal
>> +	  monitoring of CPU clusters, graphics, and SoC glue, but does not
>> +	  include monitoring of charger temperature.
>

-- 
Best regards,
-Wendy



  reply	other threads:[~2013-09-27 22:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23 17:51 [PATCH 0/3] thermal: bcm281xx: Add thermal driver Wendy Ng
2013-09-23 17:51 ` [PATCH 1/3] " Wendy Ng
2013-09-23 18:19   ` Eduardo Valentin
     [not found]     ` <52408648.7040301-l0cyMroinI0@public.gmane.org>
2013-09-23 22:43       ` Wendy Ng
     [not found]         ` <5240C42A.3030705-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2013-09-23 23:46           ` Eduardo Valentin
2013-10-04 22:17             ` Wendy Ng
2013-10-07 14:52               ` Eduardo Valentin
2013-10-07 16:12                 ` Eduardo Valentin
2013-10-07 17:52                   ` Wendy Ng
2013-10-07 22:32                     ` Eduardo Valentin
     [not found]                       ` <52533692.5090703-l0cyMroinI0@public.gmane.org>
2013-10-07 23:11                         ` Wendy Ng
2013-09-25 19:26   ` Matt Porter
2013-09-27 22:49     ` Wendy Ng [this message]
2013-09-23 17:51 ` [PATCH 2/3] ARM: bcm281xx: Turn on Thermal and HWMON drivers Wendy Ng
     [not found] ` <1379958698-7554-1-git-send-email-wendy.ng-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2013-09-23 17:51   ` [PATCH 3/3] ARM: bcm281xx: Add thermal driver to device tree Wendy Ng

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=52460B90.5060907@broadcom.com \
    --to=wendy.ng@broadcom.com \
    --cc=bcm@fixthebug.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=matt.porter@linaro.org \
    --cc=mmayer@broadcom.com \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).