public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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:54:43 +0200	[thread overview]
Message-ID: <87c2d498-60fe-4339-83c8-f6d6bc256ea7@linux.intel.com> (raw)
In-Reply-To: <9f1d5b88-e638-4b87-bee0-fc963231d20e@opensource.cirrus.com>



On 17/12/2025 15:16, Richard Fitzgerald wrote:
> On 17/12/2025 1:01 pm, Péter Ujfalusi wrote:
>>
>>
>> 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
>>
>>>
>>
> The kunit tests can run on the computer you use to build the kernel. It
> takes a couple of minutes to run.
> 
> On my desktop box with vanilla 6.19-rc1:
> 
> rf@debianbox:~/work/kernel/linux$ make mrproper
> rf@debianbox:~/work/kernel/linux$ time ./tools/testing/kunit/kunit.py
> run --alltests

well, I don't have kunit test setup, so it fails, but I can build the
kernel and install on DUT and load the module:
[  159.843361]         ok 97 single volsw_sx: 0,0 -> range: 15->4(0), sign: 0, inv: 0 -> 0xf,0x0
[  159.843499]     # soc_ops_test_access: EXPECTATION FAILED at sound/soc/soc-ops-test.c:520
                   Expected result->value.integer.value[0] == param->lctl, but
                       result->value.integer.value[0] == 0 (0x0)
                       param->lctl == 1 (0x1)
[  159.843641]         not ok 98 single volsw_sx: 1,1 -> range: 15->4(0), sign: 0, inv: 0 -> 0x0,0x0

I guess, this implies that this patch is indeed does not work.

Tested the other patch and that works, sent my tested-by for it.

> 
> <SNIP>
> 
> [13:12:31] Testing complete. Ran 7154 tests: passed: 7082, failed: 36,
> skipped: 36
> [13:12:31] Elapsed time: 110.250s total, 3.072s configuring, 55.003s
> building, 52.119s running
> 
> real    1m50.314s
> user    15m52.878s
> sys    1m18.186s
> 

-- 
Péter


  reply	other threads:[~2025-12-17 13:54 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
2025-12-17 13:16             ` Richard Fitzgerald
2025-12-17 13:54               ` Péter Ujfalusi [this message]
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=87c2d498-60fe-4339-83c8-f6d6bc256ea7@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