mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.cirrus.com,
	 linux-sound@vger.kernel.org
Subject: Re: [PATCH 00/12] firmware: cirrus: Add KUnit tests for cs_dsp
Date: Fri, 13 Dec 2024 18:27:01 +0000	[thread overview]
Message-ID: <173411442121.280424.13197221049139843918.b4-ty@kernel.org> (raw)
In-Reply-To: <20241212143725.1381013-1-rf@opensource.cirrus.com>

On Thu, 12 Dec 2024 14:37:13 +0000, Richard Fitzgerald wrote:
> This series adds KUnit tests for the cs_dsp module.
> 
> Most of the functionality in cs_dsp is for downloading firmware to
> DSP memory and interacting with "control" words defined in that
> memory. This doesn't require any emulation of running firmware,
> because it is only reading and writing registers. So the testing can
> be done using a dummy regmap. The way this is used to perform testing
> is described in more detail in the commit message for each test.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[01/12] firmware: cs_dsp: Add mock regmap for KUnit testing
        commit: d54a3fc6bf3db0db0e16cfdf7f48a8bbb803f6b0
[02/12] firmware: cs_dsp: Add mock DSP memory map for KUnit testing
        commit: 41e78c0f44f97c958afcda3f82b23f4f4a05b968
[03/12] firmware: cs_dsp: Add mock wmfw file generator for KUnit testing
        commit: 5cf1b7b471803f7cc654a29ee16cb085ad69c097
[04/12] firmware: cs_dsp: Add mock bin file generator for KUnit testing
        commit: 7c052c6615297ff32032105130cd5f02059f7ae4
[05/12] firmware: cs_dsp: Add KUnit testing of bin file download
        commit: dd0b6b1f29b92202d03a6d2dd7d65ecead27941a
[06/12] firmware: cs_dsp: Add KUnit testing of wmfw download
        commit: a2b2f2c1cd2a8b21c23bd1ec33131d2266c7568a
[07/12] firmware: cs_dsp: Add KUnit testing of control parsing
        commit: 83baecd92e7c2a44ac963fab8fd4476c71e19ddd
[08/12] firmware: cs_dsp: Add KUnit testing of control cache
        commit: 9b33a4fc500cedc1adc9c0ee01e30ffd50e5887a
[09/12] firmware: cs_dsp: Add KUnit testing of control read/write
        commit: fe54fd5474f746f07f2b587f2f5e3311bf611970
[10/12] firmware: cs_dsp: Add KUnit testing of bin error cases
        commit: cd8c058499b65e8605cd3c387bb1f76e2954870e
[11/12] firmware: cs_dsp: Add KUnit testing of wmfw error cases
        commit: feb5fb0615f321ab514f4fbbab777f3591f7e4b5
[12/12] firmware: cs_dsp: Add KUnit testing of client callbacks
        commit: 75a4a6ef615e2f4e9458051641f185498273ce02

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


      parent reply	other threads:[~2024-12-13 18:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 14:37 Richard Fitzgerald
2024-12-12 14:37 ` [PATCH 01/12] firmware: cs_dsp: Add mock regmap for KUnit testing Richard Fitzgerald
2024-12-12 14:37 ` [PATCH 02/12] firmware: cs_dsp: Add mock DSP memory map " Richard Fitzgerald
2024-12-12 14:37 ` [PATCH 03/12] firmware: cs_dsp: Add mock wmfw file generator " Richard Fitzgerald
2024-12-12 14:37 ` [PATCH 04/12] firmware: cs_dsp: Add mock bin " Richard Fitzgerald
2024-12-12 14:37 ` [PATCH 05/12] firmware: cs_dsp: Add KUnit testing of bin file download Richard Fitzgerald
2024-12-12 14:37 ` [PATCH 06/12] firmware: cs_dsp: Add KUnit testing of wmfw download Richard Fitzgerald
2024-12-12 14:37 ` [PATCH 07/12] firmware: cs_dsp: Add KUnit testing of control parsing Richard Fitzgerald
2024-12-12 14:37 ` [PATCH 08/12] firmware: cs_dsp: Add KUnit testing of control cache Richard Fitzgerald
2024-12-12 14:37 ` [PATCH 09/12] firmware: cs_dsp: Add KUnit testing of control read/write Richard Fitzgerald
2024-12-12 14:37 ` [PATCH 10/12] firmware: cs_dsp: Add KUnit testing of bin error cases Richard Fitzgerald
2024-12-12 14:37 ` [PATCH 11/12] firmware: cs_dsp: Add KUnit testing of wmfw " Richard Fitzgerald
2024-12-12 14:37 ` [PATCH 12/12] firmware: cs_dsp: Add KUnit testing of client callbacks Richard Fitzgerald
2024-12-13 18:27 ` Mark Brown [this message]

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=173411442121.280424.13197221049139843918.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.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

all inboxes | Powered by JetHome®