mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wei Ni <wni@nvidia.com>
To: <edubezval@gmail.com>, <thierry.reding@gmail.com>,
	<robh+dt@kernel.org>, <rui.zhang@intel.com>
Cc: <MLongnecker@nvidia.com>, <swarren@wwwdotorg.org>,
	<mikko.perttunen@kapsi.fi>, <linux-tegra@vger.kernel.org>,
	<linux-pm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, Wei Ni <wni@nvidia.com>
Subject: [PATCH 0/9] Add HW throttle for Tegra soctherm
Date: Thu, 31 Mar 2016 16:43:59 +0800	[thread overview]
Message-ID: <1459413848-5405-1-git-send-email-wni@nvidia.com> (raw)

This series add following functions for Tegra soctherm:
1. add Tegra132 support.
2. add HW throttle function.
3. set hot trip temperatures which can trigger the HW throttle.

Wei Ni (9):
  thermal: tegra: add Tegra132 specific SOC_THERM driver
  arm64: tegra: use tegra132-soctherm for Tegra132
  arm64: tegra: set critical trips for Tegra132
  of: Add bindings of hw throttle for soctherm
  thermal: tegra: add hw-throttle function
  thermal: tegra: add hw-throttle for Tegra132
  arm64: tegra: set hot trips for Tegra210
  arm64: tegra: set hot trips for Tegra132
  arm: tegra: set hot trips for Tegra124

 .../devicetree/bindings/thermal/tegra-soctherm.txt |  89 ++-
 arch/arm/boot/dts/tegra124.dtsi                    |  39 +-
 arch/arm64/boot/dts/nvidia/tegra132.dtsi           | 119 ++-
 arch/arm64/boot/dts/nvidia/tegra210.dtsi           |  41 +-
 drivers/thermal/tegra/Makefile                     |   1 +
 drivers/thermal/tegra/soctherm.c                   | 834 ++++++++++++++++++++-
 drivers/thermal/tegra/soctherm.h                   |  14 +
 drivers/thermal/tegra/tegra124-soctherm.c          |  18 +
 drivers/thermal/tegra/tegra132-soctherm.c          | 214 ++++++
 drivers/thermal/tegra/tegra210-soctherm.c          |  18 +
 include/dt-bindings/thermal/tegra124-soctherm.h    |   5 +
 11 files changed, 1355 insertions(+), 37 deletions(-)
 create mode 100644 drivers/thermal/tegra/tegra132-soctherm.c

-- 
1.9.1

             reply	other threads:[~2016-03-31  8:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31  8:43 Wei Ni [this message]
2016-03-31  8:44 ` [PATCH 1/9] thermal: tegra: add Tegra132 specific SOC_THERM driver Wei Ni
2016-03-31  8:44 ` [PATCH 2/9] arm64: tegra: use tegra132-soctherm for Tegra132 Wei Ni
2016-03-31  8:44 ` [PATCH 3/9] arm64: tegra: set critical trips " Wei Ni
2016-03-31  8:44 ` [PATCH 4/9] of: Add bindings of hw throttle for soctherm Wei Ni
2016-03-31  8:44 ` [PATCH 5/9] thermal: tegra: add hw-throttle function Wei Ni
2016-03-31  8:44 ` [PATCH 6/9] thermal: tegra: add hw-throttle for Tegra132 Wei Ni
2016-03-31  8:44 ` [PATCH 7/9] arm64: tegra: set hot trips for Tegra210 Wei Ni
2016-03-31  8:44 ` [PATCH 8/9] arm64: tegra: set hot trips for Tegra132 Wei Ni
2016-03-31  8:44 ` [PATCH 9/9] arm: tegra: set hot trips for Tegra124 Wei Ni
2016-03-31  8:50 ` [PATCH 0/9] Add HW throttle for Tegra soctherm Wei Ni

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=1459413848-5405-1-git-send-email-wni@nvidia.com \
    --to=wni@nvidia.com \
    --cc=MLongnecker@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.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 \
    /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

all inboxes | Powered by JetHome®