Changes in Makefile

1260ed77798502de9c98020040d2995008de10cc - Merge drm/drm-fixes into drm-misc-fixes

Tue, 08 Apr 2025 10:15:47 +0200

Merge drm/drm-fixes into drm-misc-fixesBackmerging to get updates from v6.15-rc1.Signed-off-by: Thomas Zimmermann List of files: /linux/drivers/firmware/cirrus/test/Makefile

946661e3bef8efa11ba8079d4ebafe6fc3b0aaad - Merge branch 'next' into for-linus

Sat, 05 Apr 2025 08:04:35 +0200

Merge branch 'next' into for-linusPrepare input updates for 6.15 merge window. List of files: /linux/drivers/firmware/cirrus/test/Makefile

0b119045b79a672bc6d8f18641c60fc8ce1b4585 - Merge tag 'v6.14-rc4' into next

Wed, 26 Feb 2025 01:03:25 +0100

Merge tag 'v6.14-rc4' into nextSync up with the mainline. List of files: /linux/drivers/firmware/cirrus/test/Makefile

9e676a024fa1fa2bd8150c2d2ba85478280353bc - Merge tag 'v6.14-rc1' into perf-tools-next

Wed, 05 Feb 2025 23:57:18 +0100

Merge tag 'v6.14-rc1' into perf-tools-nextTo get the various fixes in the current master.Signed-off-by: Namhyung Kim List of files: /linux/drivers/firmware/cirrus/test/Makefile

0410c6121529409b08e81a77ae3ee58c657e2243 - Merge drm/drm-next into drm-xe-next

Fri, 28 Feb 2025 15:54:14 +0100

Merge drm/drm-next into drm-xe-nextSync to fix conlicts between drm-xe-next and drm-intel-next.Signed-off-by: Lucas De Marchi List of files: /linux/drivers/firmware/cirrus/test/Makefile

93c7dd1b39444ebd5a6a98e56a363d7a4e646775 - Merge drm/drm-next into drm-misc-next

Thu, 06 Feb 2025 13:47:32 +0100

Merge drm/drm-next into drm-misc-nextBring rc1 to start the new release dev.Signed-off-by: Maxime Ripard List of files: /linux/drivers/firmware/cirrus/test/Makefile

ea9f8f2b21795a5d80418a655bcb212d5b89e08f - Merge drm/drm-next into drm-intel-next

Wed, 05 Feb 2025 18:12:37 +0100

Merge drm/drm-next into drm-intel-nextSync with v6.14-rc1.Signed-off-by: Jani Nikula List of files: /linux/drivers/firmware/cirrus/test/Makefile

c771600c6af14749609b49565ffb4cac2959710d - Merge drm/drm-next into drm-intel-gt-next

Wed, 05 Feb 2025 10:29:14 +0100

Merge drm/drm-next into drm-intel-gt-nextWe need4ba4f1afb6a9 ("perf: Generic hotplug support for a PMU with a scope")in order to land a i915 PMU simplification and a fix. That landed in 6.12and we are stuck at 6.9 so lets bump things forward.Signed-off-by: Tvrtko Ursulin List of files: /linux/drivers/firmware/cirrus/test/Makefile

b3cc7428a32202936904b5b07cf9f135025bafd6 - Merge branch 'for-6.15/amd_sfh' into for-linus

Wed, 26 Mar 2025 13:42:07 +0100

Merge branch 'for-6.15/amd_sfh' into for-linusFrom: Mario Limonciello Some platforms include a human presence detection (HPD) sensor. Whenenabled and a user is detected a wake event will be emitted from thesensor fusion hub that software can react to.Example use cases are "wake from suspend on approach" or to "lockwhen leaving".This is currently enabled by default on supported systems, but userscan't control it. This essentially means that wake on approach isenabled which is a really surprising behavior to users that don'texpect it.Instead of defaulting to enabled add a sysfs knob that users canuse to enable the feature if desirable and set it to disabled bydefault. List of files: /linux/drivers/firmware/cirrus/test/Makefile

2c8d2a510c15c003749e43ac2b8e1bc79a7a00d6 - Merge tag 'sound-6.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound

Fri, 24 Jan 2025 16:54:34 +0100

Merge tag 'sound-6.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/soundPull sound updates from Takashi Iwai: "This was a relatively calm cycle, and most of changes are rather small device-specific fixes. Here are highlights: Core: - Further enhancements of ALSA rawmidi and sequencer APIs for MIDI 2.0 - compress-offload API extensions for ASRC support ASoC: - Allow clocking on each DAI in an audio graph card to be configured separately - Improved power management for Renesas RZ-SSI - KUnit testing for the Cirrus DSP framework - Memory to meory operation support for Freescale/NXP platforms - Support for pause operations in SOF - Support for Allwinner suinv F1C100s, Awinc AW88083, Realtek ALC5682I-VE HD- and USB-audio: - Add support for Focusrite Scarlett 4th Gen 16i16, 18i16, and 18i20 interfaces via new FCP driver - TAS2781 SPI HD-audio sub-codec support - Various device-specific quirks as usual"* tag 'sound-6.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound: (235 commits) ALSA: hda: tas2781-spi: Fix bogus error handling in tas2781_hda_spi_probe() ALSA: hda: tas2781-spi: Fix error code in tas2781_read_acpi() ALSA: hda: tas2781-spi: Delete some dead code ALSA: usb: fcp: Fix return code from poll ops ALSA: usb: fcp: Fix incorrect resp->opcode retrieval ALSA: usb: fcp: Fix meter_levels type to __le32 ALSA: hda/realtek: Enable Mute LED on HP Laptop 14s-fq1xxx ALSA: hda: tas2781-spi: Fix -Wsometimes-uninitialized in tasdevice_spi_switch_book() ALSA: ctxfi: Simplify dao_clear_{left,right}_input() functions ALSA: hda: tas2781-spi: select CRC32 instead of CRC32_SARWATE ALSA: usb: fcp: Fix hwdep read ops types ALSA: scarlett2: Add device_setup option to use FCP driver ALSA: FCP: Add Focusrite Control Protocol driver ALSA: hda/tas2781: Add tas2781 hda SPI driver ALSA: hda/realtek - Fixed headphone distorted sound on Acer Aspire A115-31 laptop ASoC: xilinx: xlnx_spdif: Simpify using devm_clk_get_enabled() ALSA: hda: Support for Ideapad hotkey mute LEDs ASoC: Intel: sof_sdw: Fix DMI match for Lenovo 83JX, 83MC and 83NM ASoC: Intel: sof_sdw: Fix DMI match for Lenovo 83LC ASoC: dapm: add support for preparing streams ... List of files: /linux/drivers/firmware/cirrus/test/Makefile

8514d8f80e5cc87eb68ec037857fcd64d9c0bc68 - Merge tag 'asoc-v6.14' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus

Mon, 20 Jan 2025 16:15:07 +0100

Merge tag 'asoc-v6.14' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linusASoC: Updates for v6.14This was quite a quiet release for what I imagine are holiday relatedreasons, the diffstat is dominated by some Cirrus Logic Kunit tests.There's the usual mix of small improvements and fixes, plus a few newdrivers and features. The diffstat includes some DRM changes due towork on HDMI audio. - Allow clocking on each DAI in an audio graph card to be configured separately. - Improved power management for Renesas RZ-SSI. - KUnit testing for the Cirrus DSP framework. - Memory to meory operation support for Freescale/NXP platforms. - Support for pause operations in SOF. - Support for Allwinner suinv F1C100s, Awinc AW88083, Realtek ALC5682I-VE List of files: /linux/drivers/firmware/cirrus/test/Makefile

94c545aa535d7f5dcf54ad8e648f22943bbfcb32 - firmware: cirrus: Add KUnit tests for cs_dsp

Fri, 13 Dec 2024 18:33:05 +0100

firmware: cirrus: Add KUnit tests for cs_dspMerge series from Richard Fitzgerald :This series adds KUnit tests for the cs_dsp module.Most of the functionality in cs_dsp is for downloading firmware toDSP memory and interacting with "control" words defined in thatmemory. This doesn't require any emulation of running firmware,because it is only reading and writing registers. So the testing canbe done using a dummy regmap. The way this is used to perform testingis described in more detail in the commit message for each test.ADSP1 is not tested because this was only used by the WM2200 codec,a long-obsolete part that was discontinued in 2015. List of files: /linux/drivers/firmware/cirrus/test/Makefile

75a4a6ef615e2f4e9458051641f185498273ce02 - firmware: cs_dsp: Add KUnit testing of client callbacks

Thu, 12 Dec 2024 15:37:25 +0100

firmware: cs_dsp: Add KUnit testing of client callbacksTest that the cs_dsp_client_ops callbacks are called when expected.pre_run, post_run - when cs_dsp_run() is called.pre_stop, post_stop - when cs_dsp_stop() is calledcontrol_add - when a WMFW is loadedcontrol_remove - when cs_dsp_remove() is calledSigned-off-by: Richard Fitzgerald Link: https://patch.msgid.link/20241212143725.1381013-13-rf@opensource.cirrus.comSigned-off-by: Mark Brown List of files: /linux/drivers/firmware/cirrus/test/Makefile

feb5fb0615f321ab514f4fbbab777f3591f7e4b5 - firmware: cs_dsp: Add KUnit testing of wmfw error cases

Thu, 12 Dec 2024 15:37:24 +0100

firmware: cs_dsp: Add KUnit testing of wmfw error casesAdd tests for various types of errors and illegal values inwmfw files. This covers buffer overflows as well as generalunsupported field values.There are several sets of test cases to cover various differentversions of the wmfw file format.V0 format was only used on the earlier ADSP2 devices. It doesnot have algorithm blocks.V1 format is used on all ADSP2 versions. It added algorithmblocks and firmware coefficient descriptor blocks. Stringsare stored in fixed-length arrays.V2 format is used on all ADSP2 versions. It is similar to V1but space for strings is variable-length with either an 8-bitor 16-bit length field.V3 format is used on Halo Core DSPs and is mostly identical tothe V3 format.Signed-off-by: Richard Fitzgerald Link: https://patch.msgid.link/20241212143725.1381013-12-rf@opensource.cirrus.comSigned-off-by: Mark Brown List of files: /linux/drivers/firmware/cirrus/test/Makefile

cd8c058499b65e8605cd3c387bb1f76e2954870e - firmware: cs_dsp: Add KUnit testing of bin error cases

Thu, 12 Dec 2024 15:37:23 +0100

firmware: cs_dsp: Add KUnit testing of bin error casesAdd tests for various types of errors and illegal values inbin files. This covers buffer overflows as well as generalunsupported field values.Signed-off-by: Richard Fitzgerald Link: https://patch.msgid.link/20241212143725.1381013-11-rf@opensource.cirrus.comSigned-off-by: Mark Brown List of files: /linux/drivers/firmware/cirrus/test/Makefile

fe54fd5474f746f07f2b587f2f5e3311bf611970 - firmware: cs_dsp: Add KUnit testing of control read/write

Thu, 12 Dec 2024 15:37:22 +0100

firmware: cs_dsp: Add KUnit testing of control read/writeAdd KUnit test cases for control read/write.Tests cases cover general reading and writing of controls:1) Read/write at offset position in control.2) Read/write of various lengths less than length of the control.3) Rejecting illegal arguments.The test cases are run for ADSP2 with 16-bit registers, ADSP2with 32-bit registers and Halo Core with 32-bit registers. TheADSP2 cases are further divided into runs for V1 and V2 formatWMFW files, because there are differences in how V1 and V2defines controls.The obsolete V0 format does not have controls, so no testing ofthat format is needed.Signed-off-by: Richard Fitzgerald Link: https://patch.msgid.link/20241212143725.1381013-10-rf@opensource.cirrus.comSigned-off-by: Mark Brown List of files: /linux/drivers/firmware/cirrus/test/Makefile

9b33a4fc500cedc1adc9c0ee01e30ffd50e5887a - firmware: cs_dsp: Add KUnit testing of control cache

Thu, 12 Dec 2024 15:37:21 +0100

firmware: cs_dsp: Add KUnit testing of control cacheAdd KUnit test cases for the caching of control content.The test cases can be divided into four groups:1) The cache is correctly initialized when the firmware is first downloaded.2) Reads return the correct data.3) Writes update the registers and cache.4) If a value has been written to the control it is retained in the cache and written out to the registers when the firmware is started.There are multiple test suites to cover: - V1 and V2 format files on 16-bit and 32-bit ADSP2. - V3 format files on Halo Core DSPs.V1 format files, and some V2 format files, didn't provide accessflags for the controls. There are a couple of test cases forunspecified flags to ensure backwards compatibility with theoriginal implementation of these older firmware versions.The obsolete V0 format does not have controls, so no testing ofthat format is needed.Signed-off-by: Richard Fitzgerald Link: https://patch.msgid.link/20241212143725.1381013-9-rf@opensource.cirrus.comSigned-off-by: Mark Brown List of files: /linux/drivers/firmware/cirrus/test/Makefile

83baecd92e7c2a44ac963fab8fd4476c71e19ddd - firmware: cs_dsp: Add KUnit testing of control parsing

Thu, 12 Dec 2024 15:37:20 +0100

firmware: cs_dsp: Add KUnit testing of control parsingAdd KUnit test cases for parsing of firmware controls out of thewmfw. These test cases are only testing that the data in the wmfwis correctly interpreted and entered into the list of controls.The test cases can be roughly divided into three types:1) The correct values are extracted from the wmfw.2) Variable-length strings are handled correctly.3) Controls are correctly identified as unique or identical.There are multiple test suites to cover:- V1 and V2 format files on 16-bit and 32-bit ADSP2.- V3 format files on Halo Core DSPs.V1 format does not have named controls, and the strings in thecoefficient descriptor are fixed-length fields. On V2 and V3 formatthe controls are named and all strings are variable-length.The obsolete V0 format does not have controls, so no testing ofthat format is needed.Signed-off-by: Richard Fitzgerald Link: https://patch.msgid.link/20241212143725.1381013-8-rf@opensource.cirrus.comSigned-off-by: Mark Brown List of files: /linux/drivers/firmware/cirrus/test/Makefile

a2b2f2c1cd2a8b21c23bd1ec33131d2266c7568a - firmware: cs_dsp: Add KUnit testing of wmfw download

Thu, 12 Dec 2024 15:37:19 +0100

firmware: cs_dsp: Add KUnit testing of wmfw downloadThis adds a KUnit test suite to test downloading wmfw files.The general technique is1. Create mock wmfw file content2. Tell cs_dsp to download the wmfw file3. Check in the emulated regmap registers that the correct values have been written to DSP memory4. Drop the regmap cache for the expected written registers and then do a regcache_sync() to check for unexpected writes to other registers.The test covers ADSP2 v1 and v2, and HALO Core DSPs. (ADSP1 is veryobsolete so isn't tested).There is a large number of test cases and parameterized variants of testsbecause of the many different addressing schemes supported by the Cirrusdevices. The DSP has 2 or 3 memory spaces: XM, YM and ZM. The DSP seesthese using its native addressing, which is word-addressed (notbyte-addressed). The host sees these through one of several registermappings (depending on the DSP type and parent codec family). Theregisters have three different addressing schemes: 16-bit registersaddressed by register number, 32-bit registers addressed by registernumber, or 32-bit registers addressed by byte (with a stride of 4). Inaddition to these multiple addressing schemes, the Halo Core DSPs have a"packed" register mapping that maps 4 DSP words into 3 registers. Inaddition to this there are 4 versions of the wmfw file format to betested.The test cases intentionally have relatively little factoring-out ofsimilar code. This makes it much easier to visually verify that a testcase is testing correctly, and what exactly it is testing. Factoring outlarge amounts of code into helper functions tends to obscure what theactual test procedure is, so increasing the chance of hidden errors wheretest cases don't actually test as intended.Signed-off-by: Richard Fitzgerald Link: https://patch.msgid.link/20241212143725.1381013-7-rf@opensource.cirrus.comSigned-off-by: Mark Brown List of files: /linux/drivers/firmware/cirrus/test/Makefile

dd0b6b1f29b92202d03a6d2dd7d65ecead27941a - firmware: cs_dsp: Add KUnit testing of bin file download

Thu, 12 Dec 2024 15:37:18 +0100

firmware: cs_dsp: Add KUnit testing of bin file downloadThis adds a KUnit test suite to test downloading bin files.The general technique is1. Create mock bin file content2. Tell cs_dsp to download the bin file3. Check in the emulated regmap registers that the correct values have been written to DSP memory4. Drop the regmap cache for the expected written registers and then do a regcache_sync() to check for unexpected writes to other registers.The test covers ADSP2 v1 and v2, and HALO Core DSPs. (ADSP1 is veryobsolete so isn't tested).There is a large number of test cases and parameterized variants of testsbecause of the many different addressing schemes supported by the Cirrusdevices. The DSP has 2 or 3 memory spaces: XM, YM and ZM. The DSP seesthese using its native addressing, which is word-addressed (notbyte-addressed). The host sees these through one of several registermappings (depending on the DSP type and parent codec family). Theregisters have three different addressing schemes: 16-bit registersaddressed by register number, 32-bit registers addressed by registernumber, or 32-bit registers addressed by byte (with a stride of 4). Inaddition to these multiple addressing schemes, the Halo Core DSPs have a"packed" register mapping that maps 4 DSP words into 3 registers. The binfile addresses the data blob relative to the base address of an algorithm,which has to be calculated in both DSP words (for the DSP to access) andregister addresses (for the host).This results in many different addressing schemes used in parallel, hencethe complexity of the address and size manipulation in the test cases:word addresses in DSP memory, byte offsets, word offsets, registeraddresses (either byte-addressed 32-bit or index-addressed 16-bit), andpacked register addresses.The test cases intentionally have relatively little factoring-out ofsimilar code. This makes it much easier to visually verify that a testcase is testing correctly, and what exactly it is testing. Factoring outlarge amounts of code into helper functions tends to obscure what theactual test procedure is, so increasing the chance of hidden errors wheretest cases don't actually test as intended.Signed-off-by: Richard Fitzgerald Link: https://patch.msgid.link/20241212143725.1381013-6-rf@opensource.cirrus.comSigned-off-by: Mark Brown List of files: /linux/drivers/firmware/cirrus/test/Makefile