From: Zhang Rui <rui.zhang@intel.com>
To: Florian Fainelli <florian.fainelli@broadcom.com>,
Srinath Mannam <srinath.mannam@broadcom.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Eduardo Valentin <edubezval@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH v5 0/3] Stingray thermal driver support
Date: Tue, 01 Jan 2019 22:04:39 +0800 [thread overview]
Message-ID: <1546351479.2077.1.camel@intel.com> (raw)
In-Reply-To: <3c05a1f1-5041-ebb7-27e5-0a2321314b0a@broadcom.com>
On 一, 2018-12-31 at 14:15 -0800, Florian Fainelli wrote:
>
> On 04/12/2018 19:17, Srinath Mannam wrote:
> >
> > Hi,
> >
> > Could you please provide your feedback to this patch series?
> Rui or Eduardo can we get either one of you to review the thermal
> driver
> parts of this patch series? Why do we constantly have to chase people
> to
> respond in this specific subsystem?
>
Eduardo, can you please take a look at this patch series?
thanks,
rui
> >
> >
> > Regards,
> > Srinath.
> > On Thu, Nov 8, 2018 at 3:45 AM Florian Fainelli <f.fainelli@gmail.c
> > om> wrote:
> > >
> > >
> > >
> > >
> > > On 10/16/2018 8:11 AM, Srinath Mannam wrote:
> > > >
> > > > These patches adds the stingray thermal driver and its
> > > > corresponding DT nodes with documentation.
> > > Can we get feedback from the thermal maintains whether this is
> > > acceptable or not?
> > >
> > > >
> > > >
> > > > Changes from v4
> > > > - Addressed Rob Herring comments on DT parameters and
> > > > thermal driver architecture.
> > > > - Removed brcm,max-crit-temp DT parameter
> > > > - Changed driver to thermal sensor registration model.
> > > > - Added trip DT properties.
> > > >
> > > > Changes from v3
> > > > - Addressed Daniel lezcano comments.
> > > > - Elaborated commit description of thermal driver patch.
> > > > - Added brcm,max-crit-temp DT parameter.
> > > >
> > > > Changes from v2:
> > > > - All stingray TMON DT nodes are combine together into
> > > > single.
> > > > Temperature registers are combined into one mem resource.
> > > > brcm,tmon-mask parameter has available TMONs mask value.
> > > > - All available TMONs are initialized together in single
> > > > instance of driver probe call.
> > > >
> > > > Changes from v1:
> > > > - Fixed auto build sparce warning.
> > > >
> > > > Pramod Kumar (3):
> > > > dt-bindings: thermal: Add binding document for SR thermal
> > > > thermal: broadcom: Add Stingray thermal driver
> > > > arm64: dts: stingray: Add Stingray Thermal DT support.
> > > >
> > > > .../bindings/thermal/brcm,sr-thermal.txt | 105
> > > > ++++++++++++++++
> > > > .../arm64/boot/dts/broadcom/stingray/stingray.dtsi | 89
> > > > +++++++++++++
> > > > drivers/thermal/Kconfig | 3 +-
> > > > drivers/thermal/broadcom/Kconfig | 9 ++
> > > > drivers/thermal/broadcom/Makefile | 1 +
> > > > drivers/thermal/broadcom/sr-thermal.c | 138
> > > > +++++++++++++++++++++
> > > > 6 files changed, 344 insertions(+), 1 deletion(-)
> > > > create mode 100644
> > > > Documentation/devicetree/bindings/thermal/brcm,sr-thermal.txt
> > > > create mode 100644 drivers/thermal/broadcom/sr-thermal.c
> > > >
> > > --
> > > Florian
next prev parent reply other threads:[~2019-01-01 14:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 15:11 [PATCH v5 0/3] Stingray thermal driver support Srinath Mannam
2018-10-16 15:11 ` [PATCH v5 1/3] dt-bindings: thermal: Add binding document for SR thermal Srinath Mannam
2018-10-18 14:36 ` Rob Herring
2018-10-16 15:11 ` [PATCH v5 2/3] thermal: broadcom: Add Stingray thermal driver Srinath Mannam
2019-01-02 20:03 ` Eduardo Valentin
2019-01-03 6:28 ` Srinath Mannam
2018-10-16 15:11 ` [PATCH v5 3/3] arm64: dts: stingray: Add Stingray Thermal DT support Srinath Mannam
2018-10-18 19:10 ` [PATCH v5 0/3] Stingray thermal driver support Scott Branden
2018-11-07 22:15 ` Florian Fainelli
2018-12-05 3:17 ` Srinath Mannam
2018-12-31 22:15 ` Florian Fainelli
2019-01-01 14:04 ` Zhang Rui [this message]
2019-01-01 16:07 ` Eduardo Valentin
2019-01-02 4:32 ` Srinath Mannam
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=1546351479.2077.1.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=srinath.mannam@broadcom.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;
as well as URLs for NNTP newsgroup(s).