public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Bjorn Andersson <quic_bjorande@quicinc.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: qcom: sc8280xp: Introduce additional tsens instances
Date: Fri, 26 Jan 2024 18:00:54 +0100	[thread overview]
Message-ID: <ZbPlRsx3czAHRBew@hovoldconsulting.com> (raw)
In-Reply-To: <20240126165113.GS2936378@hu-bjorande-lv.qualcomm.com>

On Fri, Jan 26, 2024 at 08:51:13AM -0800, Bjorn Andersson wrote:
> On Fri, Jan 26, 2024 at 05:36:10PM +0100, Johan Hovold wrote:

> > Shall you submit a follow-on patch to set the polling delays to zero
> > for the other thermal zones (cpu, cluster, mem) so that we don't poll
> > for those?
> 
> I optimistically interpreted Konrad's response as a promise by him to do
> so ;)
> 
> I do like his patch which remove the poll-properties for non-polling
> mode. Would be nice to not first change the values to 0 and then remove
> the properties...

No, that should not be an issue as it allows us to get rid of the
polling without waiting for a binding update which may or may not
materialise in 6.9-rc1.

But whoever updates those properties need to do some proper testing to
make sure that those interrupts really work.

Johan

  reply	other threads:[~2024-01-26 17:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 15:12 [PATCH v2] arm64: dts: qcom: sc8280xp: Introduce additional tsens instances Bjorn Andersson
2024-01-26 16:36 ` Johan Hovold
2024-01-26 16:51   ` Bjorn Andersson
2024-01-26 17:00     ` Johan Hovold [this message]
2024-01-26 21:23       ` Konrad Dybcio
2024-01-29  9:38         ` Johan Hovold
2024-01-26 21:20 ` Konrad Dybcio

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=ZbPlRsx3czAHRBew@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_bjorande@quicinc.com \
    --cc=robh+dt@kernel.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