From: rui.zhang@intel.com (Zhang Rui)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] thermal: add brcmstb AVS TMON driver
Date: Fri, 11 Aug 2017 13:35:56 +0800 [thread overview]
Message-ID: <1502429756.2470.9.camel@intel.com> (raw)
In-Reply-To: <20170809220257.4234-1-code@mmayer.net>
On Wed, 2017-08-09 at 15:02 -0700, Markus Mayer wrote:
> From: Markus Mayer <mmayer@broadcom.com>
>
> This series adds the brcmstb AVS TMON driver.
>
> The driver was originally written by Brian Norris.
>
> This series is also available at
> https://github.com/mmayer/linux/tree/brcmstb-thermal-4.13-v4.
>
> v1 of this series can be found at https://lkml.org/lkml/2017/6/5/921
> v2 of this series can be found at https://lkml.org/lkml/2017/7/21/585
> v3 of this series can be found at https://lkml.org/lkml/2017/7/31/710
>
> Changes since v3:
> - Rebased on v4.13-rc3 to resolve conflicts in the MAINTAINERS file
>
thanks, will apply this if we have ACK for patch 3 and 4.
thanks,
rui
> Changes since v2:
> - replaced calls to pr_debug() with calls to dev_dbg() [PATCH 2/4
> only]
> - all other patches are unchanged from v2
>
> Changes since v1:
> - Fixed wording in binding document
> - Fixed lincensing to consistently mention GPL v2
> - Use thermal_zone_get_slope() and thermal_zone_get_offset()
> - Some minor clean-ups
>
> Brian Norris (2):
> ? Documentation: devicetree: add binding for Broadcom STB AVS TMON
> ? thermal: add brcmstb AVS TMON driver
>
> Markus Mayer (2):
> ? ARM: multi_v7_defconfig: add CONFIG_BRCMSTB_THERMAL
> ? arm64: defconfig: add CONFIG_BRCMSTB_THERMAL
>
> ?.../devicetree/bindings/thermal/brcm,avs-tmon.txt??|??20 ++
> ?MAINTAINERS????????????????????????????????????????|???8 +
> ?arch/arm/configs/multi_v7_defconfig????????????????|???1 +
> ?arch/arm64/configs/defconfig???????????????????????|???1 +
> ?drivers/thermal/Kconfig????????????????????????????|???2 +-
> ?drivers/thermal/broadcom/Kconfig???????????????????|???7 +
> ?drivers/thermal/broadcom/Makefile??????????????????|???1 +
> ?drivers/thermal/broadcom/brcmstb_thermal.c?????????| 386
> +++++++++++++++++++++
> ?8 files changed, 425 insertions(+), 1 deletion(-)
> ?create mode 100644
> Documentation/devicetree/bindings/thermal/brcm,avs-tmon.txt
> ?create mode 100644 drivers/thermal/broadcom/brcmstb_thermal.c
>
next prev parent reply other threads:[~2017-08-11 5:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 22:02 [PATCH v4 0/4] thermal: add brcmstb AVS TMON driver Markus Mayer
2017-08-09 22:02 ` [PATCH v4 1/4] Documentation: devicetree: add binding for Broadcom STB AVS TMON Markus Mayer
2017-08-17 15:10 ` Rob Herring
2017-08-09 22:02 ` [PATCH v4 2/4] thermal: add brcmstb AVS TMON driver Markus Mayer
2017-08-15 6:08 ` Zhang Rui
2017-08-15 6:42 ` Rafał Miłecki
2017-08-15 6:48 ` Zhang Rui
2017-09-24 21:11 ` Florian Fainelli
2017-09-26 3:02 ` Zhang, Rui
2017-09-26 4:13 ` Florian Fainelli
2017-09-26 6:17 ` Zhang, Rui
2017-09-26 21:36 ` Markus Mayer
2017-08-09 22:02 ` [PATCH v4 3/4] ARM: multi_v7_defconfig: add CONFIG_BRCMSTB_THERMAL Markus Mayer
2017-08-15 17:23 ` Florian Fainelli
2017-08-09 22:02 ` [PATCH v4 4/4] arm64: defconfig: " Markus Mayer
2017-08-15 17:24 ` Florian Fainelli
2017-08-11 5:35 ` Zhang Rui [this message]
2017-08-13 4:57 ` [PATCH v4 0/4] thermal: add brcmstb AVS TMON driver Florian Fainelli
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=1502429756.2470.9.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=linux-arm-kernel@lists.infradead.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).