From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Richard Fitzgerald <rf@opensource.cirrus.com>,
Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, linux-sound@vger.kernel.org,
kai.vehmanen@linux.intel.com, seppo.ingalsuo@linux.intel.com,
stable@vger.kernel.org, niranjan.hy@ti.com,
ckeepax@opensource.cirrus.com, sbinding@opensource.cirrus.com
Subject: Re: [PATCH] ASoC: soc-ops: Correct the max value for clamp in soc_mixer_reg_to_ctl()
Date: Wed, 17 Dec 2025 15:01:32 +0200 [thread overview]
Message-ID: <e98a78fc-0b30-4af1-b6f5-2bc5cacc8115@linux.intel.com> (raw)
In-Reply-To: <bc6f3e66-ca9b-4ba3-bbe1-5ef31c373e6d@opensource.cirrus.com>
On 17/12/2025 14:40, Richard Fitzgerald wrote:
>>
>> It passes my manual tests on cs42l43, not sure how to run the unit-test
>> for SX, can you by chance test this?
>>
> The easiest option is to run them from your kernel build tree like this:
It is in my to-do list to get kunit working on my setups (Artix Linux on
dev and DUTs), so it is really something that will take rest of the year
easily ;)
>
> make mrproper
> ./tools/testing/kunit/kunit.py run --kunitconfig=tools/testing/kunit/
> configs/all_tests.config
>
--
Péter
next prev parent reply other threads:[~2025-12-17 13:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 12:06 [PATCH] ASoC: soc-ops: Correct the max value for clamp in soc_mixer_reg_to_ctl() Peter Ujfalusi
2025-12-17 12:16 ` Mark Brown
2025-12-17 12:20 ` Péter Ujfalusi
2025-12-17 12:36 ` Richard Fitzgerald
2025-12-17 12:38 ` Péter Ujfalusi
2025-12-17 12:40 ` Richard Fitzgerald
2025-12-17 12:44 ` Mark Brown
2025-12-17 13:01 ` Péter Ujfalusi [this message]
2025-12-17 13:16 ` Richard Fitzgerald
2025-12-17 13:54 ` Péter Ujfalusi
2025-12-17 13:56 ` Mark Brown
2025-12-17 13:59 ` Péter Ujfalusi
2025-12-17 14:00 ` Mark Brown
2025-12-17 14:19 ` Péter Ujfalusi
2025-12-17 14:22 ` Mark Brown
2025-12-17 13:18 ` Mark Brown
2025-12-17 12:17 ` Péter Ujfalusi
2025-12-17 12:47 ` Charles Keepax
2025-12-17 13:13 ` Péter Ujfalusi
2025-12-17 13:42 ` Charles Keepax
2025-12-17 14:31 ` Péter Ujfalusi
2025-12-17 15:00 ` Charles Keepax
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=e98a78fc-0b30-4af1-b6f5-2bc5cacc8115@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=niranjan.hy@ti.com \
--cc=rf@opensource.cirrus.com \
--cc=sbinding@opensource.cirrus.com \
--cc=seppo.ingalsuo@linux.intel.com \
--cc=stable@vger.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