Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: "Alexey Klimov" <alexey.klimov@linaro.org>
To: "Mark Brown" <broonie@kernel.org>
Cc: <srinivas.kandagatla@linaro.org>, <lgirdwood@gmail.com>,
	<krzysztof.kozlowski@linaro.org>, <perex@perex.cz>,
	<tiwai@suse.com>, <jdelvare@suse.com>, <linux@roeck-us.net>,
	<linux-sound@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-hwmon@vger.kernel.org>
Subject: Re: [PATCH] ASoC: codecs: wsa883x: Implement temperature reading and hwmon
Date: Thu, 27 Mar 2025 12:41:48 +0000	[thread overview]
Message-ID: <D8R21NO1IN43.1E4FD7KG9Z4KI@linaro.org> (raw)
In-Reply-To: <3e08b501-f8d0-4e68-874e-b578e7c82c47@sirena.org.uk>

Hi Mark,

On Sun Mar 16, 2025 at 11:33 PM GMT, Mark Brown wrote:
> On Tue, Jan 07, 2025 at 11:45:06AM +0000, Alexey Klimov wrote:
>> Read temperature of the amplifier and expose it via hwmon interface, which
>> will be later used during calibration of speaker protection algorithms.
>> The method is the same as for wsa884x and therefore this is based on
>> Krzysztof Kozlowski's approach implemented in commit 6b99dc62d940 ("ASoC:
>> codecs: wsa884x: Implement temperature reading and hwmon").
>
> This doesn't apply against current code, please check and resend.

Just for reference and for future, what should be the base for patches?
linux-next or specific repo/branch in audio asoc?

Thanks,
Alexey

  reply	other threads:[~2025-03-27 12:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 11:45 [PATCH] ASoC: codecs: wsa883x: Implement temperature reading and hwmon Alexey Klimov
2025-01-07 22:25 ` Steev Klimaszewski
2025-02-21  0:47   ` Alexey Klimov
2025-03-16 23:33 ` Mark Brown
2025-03-27 12:41   ` Alexey Klimov [this message]
2025-03-27 13:01     ` Mark Brown

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=D8R21NO1IN43.1E4FD7KG9Z4KI@linaro.org \
    --to=alexey.klimov@linaro.org \
    --cc=broonie@kernel.org \
    --cc=jdelvare@suse.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=perex@perex.cz \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=tiwai@suse.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