All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Nicolas Chauvet <kwizart@gmail.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Zhang Rui <rui.zhang@intel.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: <linux-tegra@vger.kernel.org>, <linux-pm@vger.kernel.org>,
	<stable@vger.kernel.org>
Subject: Re: [PATCH v2 6/6] thermal: tegra: Avoid setting edp_irq when not relevant
Date: Thu, 19 Nov 2020 19:15:32 +0000	[thread overview]
Message-ID: <1ddb2245-fde0-644c-e89a-5f94015fc682@nvidia.com> (raw)
In-Reply-To: <20200927150956.34609-7-kwizart@gmail.com>



On 27/09/2020 16:09, Nicolas Chauvet wrote:
> According to the binding, the edp_irq is not available on tegra124/132

It appears that the binding doc is not update to date or missing the
relevant information. Looking at the Tegra124 TRM I see that there is a
SOCTHERM EDP IRQ (51) and so maybe the correct fix is to add this.

Cheers
Jon

-- 
nvpublic

  reply	other threads:[~2020-11-19 19:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-27 15:09 [PATCH v2 0/6] thermal: tegra: soctherm bugfixes Nicolas Chauvet
2020-09-27 15:09 ` [PATCH v2 1/6] ARM: tegra: Add missing gpu-throt-level to tegra124 soctherm Nicolas Chauvet
2020-09-27 15:09 ` [PATCH v2 2/6] ARM: tegra: Add missing hot temperatures to tegra124 thermal-zones Nicolas Chauvet
2020-09-27 15:09 ` [PATCH v2 3/6] arm64: tegra: Add missing hot temperatures to tegra132 thermal-zones Nicolas Chauvet
2020-09-27 15:09 ` [PATCH v2 4/6] arm64: tegra: Add missing gpu-throt-level to tegra210 soctherm Nicolas Chauvet
2020-09-27 15:09 ` [PATCH v2 5/6] arm64: tegra: Add missing hot temperatures to tegra210 thermal-zones Nicolas Chauvet
2020-09-27 15:09 ` [PATCH v2 6/6] thermal: tegra: Avoid setting edp_irq when not relevant Nicolas Chauvet
2020-11-19 19:15   ` Jon Hunter [this message]
2020-11-19 11:00 ` [PATCH v2 0/6] thermal: tegra: soctherm bugfixes Nicolas Chauvet
2020-11-19 11:04   ` Daniel Lezcano
2020-11-20 15:07     ` Thierry Reding
2020-11-20 16:14 ` Thierry Reding

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=1ddb2245-fde0-644c-e89a-5f94015fc682@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=kwizart@gmail.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.