Changes in Makefile

3983f7b9 - ALSA: core: Use -y instead of -objs in Makefile

Tue, 07 May 2024 13:55:01 +0000

ALSA: core: Use *-y instead of *-objs in Makefile*-objs suffix is reserved rather for (user-space) host programs whileusually *-y suffix is used for kernel drivers (although *-objs worksfor that purpose for now).Let's correct the old usages of *-objs in Makefiles.Signed-off-by: Takashi Iwai Reviewed-by: Andy Shevchenko Reviewed-by: Jaroslav Kysela Link: https://lore.kernel.org/r/20240507135513.14919-2-tiwai@suse.de List of files: /linux-6.15/sound/core/Makefile

4df49712 - ALSA: Drop leftover snd-rtctimer stuff from Makefile

Wed, 21 Feb 2024 09:21:56 +0000

ALSA: Drop leftover snd-rtctimer stuff from MakefileWe forgot to remove the line for snd-rtctimer from Makefile whiledropping the functionality. Get rid of the stale line.Fixes: 34ce71a96dcb ("ALSA: timer: remove legacy rtctimer")Link: https://lore.kernel.org/r/20240221092156.28695-1-tiwai@suse.deSigned-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

3e39acf5 - ALSA: core: Add sound core KUnit test

Thu, 25 Jan 2024 22:35:21 +0000

ALSA: core: Add sound core KUnit testAt the moment, we have a decent amount of integration tests (selftests)covering different aspects of the sound subsystem. However, a lot ofof sound-related in-kernel functions remains uncovered. This patchintroduces the KUnit test for the core part of the sound subsystem.It includes 10 test cases:- Coverage of the format-related inline functions from 'pcm.h' headerfile: snd_pcm_format_physical_width, snd_pcm_format_width,snd_pcm_format_signed, test_format_endianness- Coverage of the available bytes counting functions from 'pcm.h'header: snd_pcm_capture_avail, snd_pcm_playback_avail- Coverage of functions from pcm_misc: snd_pcm_format_set_silence,snd_pcm_format_name- Coverage of card-related functions from init.c: snd_card_set_id,snd_component_addThis patch depends on the previous patches in this patch series as theycontain fix for the bug, which was found during the test development.Without them, the test doesn't pass.Signed-off-by: Ivan Orlov Link: https://lore.kernel.org/r/20240125223522.1122765-3-ivan.orlov0322@gmail.comSigned-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

0b5288f5 - ALSA: ump: Add legacy raw MIDI support

Tue, 23 May 2023 07:53:35 +0000

ALSA: ump: Add legacy raw MIDI supportThis patch extends the UMP core code to support the legacy MIDI 1.0rawmidi devices. When the new kconfig CONFIG_SND_UMP_LEGACY_RAWMIDIis set, the UMP core allows to attach an additional rawmidi device foreach UMP Endpoint. The rawmidi device contains 16 substreams whereeach substream corresponds to a UMP Group belonging to the EP. Thedevice reads/writes the legacy MIDI 1.0 byte streams and translatesfrom/to UMP packets.The legacy rawmidi devices are exclusive with the UMP rawmidi devices,hence both of them can't be opened at the same time unless the UMPrawmidi is opened in APPEND mode.Reviewed-by: Jaroslav Kysela Link: https://lore.kernel.org/r/20230523075358.9672-15-tiwai@suse.deSigned-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

e3a8a5b7 - ALSA: rawmidi: UMP support

Tue, 23 May 2023 07:53:24 +0000

ALSA: rawmidi: UMP supportThis patch adds the support helpers for UMP (Universal MIDI Packet) inALSA core.The basic design is that a rawmidi instance is assigned to each UMPEndpoint. A UMP Endpoint provides a UMP stream, typicallybidirectional (but can be also uni-directional, too), which may holdup to 16 UMP Groups, where each UMP (input/output) Group correspondsto the traditional MIDI I/O Endpoint.Additionally, the ALSA UMP abstraction provides the multiple UMPBlocks that can be assigned to each UMP Endpoint. A UMP Block is ametadata to hold the UMP Group clusters, and can represent thefunctions assigned to each UMP Group. A typical implementation of UMPBlock is the Group Terminal Blocks of USB MIDI 2.0 specification.For distinguishing from the legacy byte-stream MIDI device, a newdevice "umpC*D*" will be created, instead of the standard (MIDI 1.0)devices "midiC*D*". The UMP instance can be identified by the newrawmidi info bit SNDRV_RAWMIDI_INFO_UMP, too.A UMP rawmidi device reads/writes only in 4-bytes words alignment,stored in CPU native endianness.The transmit and receive functions take care of the input/out dataalignment, and may return zero or aligned size, and the params ioctlmay return -EINVAL when the given input/output buffer size isn'taligned.A few new UMP-specific ioctls are added for obtaining the new UMPendpoint and block information.As of this commit, no ALSA sequencer instance is attached to UMPdevices yet. They will be supported by later patches.Along with those changes, the protocol version for rawmidi is bumpedto 2.0.3.Reviewed-by: Jaroslav Kysela Link: https://lore.kernel.org/r/20230523075358.9672-4-tiwai@suse.deSigned-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

f95a387c - m68k: coldfire: drop ISA_DMA_API support

Thu, 21 Apr 2022 08:20:12 +0000

m68k: coldfire: drop ISA_DMA_API supportAfter a build regression report, I took a look at possible users ofCONFIG_ISA_DMA_API on m68k and found none, which Greg confirmed. TheCONFIG_GENERIC_ISA_DMA option in turn is only needed to implementISA_DMA_API, and is clearly not used on the platforms with ISA support.The CONFIG_ISA support for AMIGA_PCMCIA is probably also unneeded,but this is less clear. Unlike other PCMCIA implementations, this onedoes not use the drivers/pcmcia subsystem at all and just supportsthe "apne" network driver. When it was first added, one could useISA drivers on it as well, but this probably broke at some point.With no reason to keep this, let's just drop the corresponding filesand prevent the remaining ISA drivers that use this from getting built.The remaining definitions in asm/dma.h are used for PCI support.Link: https://lore.kernel.org/lkml/9e5ee1c3-ca80-f343-a1f5-66f3dd1c0727@linux-m68k.org/Acked-by: Geert Uytterhoeven Acked-by: Ulf Hansson # For MMCAcked-by: Greg Ungerer Acked-by: Takashi Iwai Signed-off-by: Arnd Bergmann Signed-off-by: Greg Ungerer List of files: /linux-6.15/sound/core/Makefile

2c95b92e - ALSA: memalloc: Unify x86 SG-buffer handling (take#3)

Tue, 16 Nov 2021 07:33:58 +0000

ALSA: memalloc: Unify x86 SG-buffer handling (take#3)This is a second attempt to unify the x86-specific SG-buffer handlingcode with the new standard non-contiguous page handler.The first try (in commit 2d9ea39917a4) failed due to the wrong pageand address calculations, hence reverted. (And the second try faileddue to a copy&paste error.) Now it's corrected with the previous fixfor noncontig pages, and the proper sg page iteration by this patch.After the migration, SNDRV_DMA_TYPE_DMA_SG becomes identical withSNDRV_DMA_TYPE_NONCONTIG on x86, while others still fall back toSNDRV_DMA_TYPE_DEV.Tested-by: Alex Xu (Hello71) Tested-by: Harald Arnesen Link: https://lore.kernel.org/r/20211017074859.24112-4-tiwai@suse.deLink: https://lore.kernel.org/r/20211109062235.22310-1-tiwai@suse.deLink: https://lore.kernel.org/r/20211116073358.19741-1-tiwai@suse.deSigned-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

7599acb7 - Revert "ALSA: memalloc: Convert x86 SG-buffer handling with non-contiguous type"

Thu, 04 Nov 2021 18:08:46 +0000

Revert "ALSA: memalloc: Convert x86 SG-buffer handling with non-contiguous type"This reverts commit 2d9ea39917a4e4293bc2caea902c7059a330b611.We've got a regression report showing that the audio got broken thedevice over AMD IOMMU. The conversion assumed the wrong pointer /page mapping for the indirect mapping case, and we need to correctthis urgently, so let's revert it for now.Fixes: 2d9ea39917a4 ("ALSA: memalloc: Convert x86 SG-buffer handling with non-contiguous type")Reported-and-tested-by: Alex Xu (Hello71) Link: https://lore.kernel.org/r/20211104180846.16340-1-tiwai@suse.deSigned-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

2d9ea399 - ALSA: memalloc: Convert x86 SG-buffer handling with non-contiguous type

Sun, 17 Oct 2021 07:48:59 +0000

ALSA: memalloc: Convert x86 SG-buffer handling with non-contiguous typeWe've had an x86-specific SG-buffer handling code, but now it can bemerged gracefully with the standard non-contiguous DMA pages.After the migration, SNDRV_DMA_TYPE_DMA_SG becomes identical withSNDRV_DMA_TYPE_NONCONTIG on x86, while others still fall back toSNDRV_DMA_TYPE_DEV.The remaining problem is about the SG-buffer with WC pages: the DMAcore stuff on x86 doesn't treat it well, so we still need some specialhandling to manipulate the page attribute manually. The mmap handlerfor SNDRV_DMA_TYPE_DEV_SG_WC still returns -ENOENT intentionally forthe fallback to the default handler.Link: https://lore.kernel.org/r/20211017074859.24112-4-tiwai@suse.deSigned-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

3c05f147 - ALSA: ISA: not for M68K

Sat, 16 Oct 2021 06:26:02 +0000

ALSA: ISA: not for M68KOn m68k, compiling drivers under SND_ISA causes build errors:../sound/core/isadma.c: In function 'snd_dma_program':../sound/core/isadma.c:33:17: error: implicit declaration of function 'claim_dma_lock' [-Werror=implicit-function-declaration] 33 | flags = claim_dma_lock(); | ^~~~~~~~~~~~~~../sound/core/isadma.c:41:9: error: implicit declaration of function 'release_dma_lock' [-Werror=implicit-function-declaration] 41 | release_dma_lock(flags); | ^~~~~~~~~~~~~~~~../sound/isa/sb/sb16_main.c: In function 'snd_sb16_playback_prepare':../sound/isa/sb/sb16_main.c:253:72: error: 'DMA_AUTOINIT' undeclared (first use in this function) 253 | snd_dma_program(dma, runtime->dma_addr, size, DMA_MODE_WRITE | DMA_AUTOINIT); | ^~~~~~~~~~~~../sound/isa/sb/sb16_main.c:253:72: note: each undeclared identifier is reported only once for each function it appears in../sound/isa/sb/sb16_main.c: In function 'snd_sb16_capture_prepare':../sound/isa/sb/sb16_main.c:322:71: error: 'DMA_AUTOINIT' undeclared (first use in this function) 322 | snd_dma_program(dma, runtime->dma_addr, size, DMA_MODE_READ | DMA_AUTOINIT); | ^~~~~~~~~~~~and more...Signed-off-by: Randy Dunlap Cc: Jaroslav Kysela Cc: Takashi Iwai Cc: alsa-devel@alsa-project.orgCc: linux-m68k@lists.linux-m68k.orgCc: Geert Uytterhoeven Link: https://lore.kernel.org/r/20211016062602.3588-1-rdunlap@infradead.orgSigned-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

22d8de62 - ALSA: control - add generic LED trigger module as the new control layer

Wed, 17 Mar 2021 17:29:42 +0000

ALSA: control - add generic LED trigger module as the new control layerThe recent laptops have usually two LEDs assigned to reflectthe speaker and microphone mute state. This implementationadds a tiny layer on top of the control API which calculatesthe state for those LEDs using the driver callbacks.Two new access flags are introduced to describe the controlswhich affects the audio path settings (an easy code changefor drivers).The LED resource can be shared with multiple sound cards withthis code. The user space controls may be added to the statechain on demand, too.This code should replace the LED code in the HDA driver andadd a possibility to easy extend the other drivers (ASoCcodecs etc.).Signed-off-by: Jaroslav Kysela Link: https://lore.kernel.org/r/20210317172945.842280-4-perex@perex.czSigned-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/sound/core/Makefile

111b0cdb - ALSA: seq: Allow the modular sequencer registration

Fri, 09 Jun 2017 13:11:58 +0000

ALSA: seq: Allow the modular sequencer registrationMany drivers bind the sequencer stuff in off-load by another drivermodule, so that it's loaded only on demand. In the current code, thismechanism doesn't work when the driver is built-in while the sequenceris module. We check with IS_REACHABLE() and enable only when thesequencer is in the same level of build.However, this is basically a overshoot. The binder code(snd-seq-device) is an individual module from the sequencer core(snd-seq), and we just have to make the former a built-in whilekeeping the latter a module for allowing the scenario like the above.This patch achieves that by rewriting Kconfig slightly. Now, a driverthat provides the manual sequencer device binding should selectCONFIG_SND_SEQ_DEVICE in a way as select SND_SEQ_DEVICE if SND_SEQUENCER != nNote that the "!=n" is needed here to avoid the influence of thesequencer core is module while the driver is built-in.Also, since rawmidi.o may be linked with snd_seq_device.o whenbuilt-in, we have to shuffle the code to make the linker happy.(the kernel linker isn't smart enough yet to handle such a case.)That is, snd_seq_device.c is moved to sound/core from sound/core/seq,as well as Makefile.Last but not least, the patch replaces the code using IS_REACHABLE()with IS_ENABLED(), since now the condition meets always when enabled.Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

be4e31da - ALSA: pcm: tracepoints for refining PCM parameters

Tue, 06 Jun 2017 23:46:43 +0000

ALSA: pcm: tracepoints for refining PCM parametersWhen working for devices which support configurable modes for its datatransmission or which consists of several components, developers arelikely to use rules of parameters of PCM substream. However, there's noinfrastructure to assist their work.In old days, ALSA PCM core got a local 'RULES_DEBUG' macro to debugrefinement of parameters for PCM substream. Although this is merely amakeshift. With some modifications, we get the infrastructure.This commit is for the purpose. Refinement of mask/interval type ofPCM parameters is probed as tracepoint events as 'hw_mask_param' and'hw_interval_param' on existent 'snd_pcm' subsystem.Signed-off-by: Takashi Sakamoto Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

34ce71a9 - ALSA: timer: remove legacy rtctimer

Sat, 23 Apr 2016 00:58:05 +0000

ALSA: timer: remove legacy rtctimerThere are no users of rtctimer left. Remove its code as this is thein-kernel user of the legacy PC RTC driver that will hopefully be removedat some point.Signed-off-by: Alexandre Belloni Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

90bbaf66 - ALSA: timer: add config item to export PCM timer disabling for expert

Fri, 16 Oct 2015 09:57:46 +0000

ALSA: timer: add config item to export PCM timer disabling for expertPCM timer is not always used. For embedded device, we need an interfaceto disable it when it is not needed, to shrink the kernel size andmemory footprint, here add CONFIG_SND_PCM_TIMER for it.When both CONFIG_SND_PCM_TIMER and CONFIG_SND_TIMER is unselected,about 25KB saving bonus we can get.Please be noted that when disabled, those stubs who using pcm timer(e.g. dmix, dsnoop & co) may work incorrectlly.Suggested-by: Takashi Iwai Signed-off-by: Jie Yang Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

cd6a6503 - ALSA: replace CONFIG_PROC_FS with CONFIG_SND_PROC_FS

Wed, 27 May 2015 11:45:45 +0000

ALSA: replace CONFIG_PROC_FS with CONFIG_SND_PROC_FSWe may disable proc fs only for sound part, to reduce ALSAmemory footprint. So add CONFIG_SND_PROC_FS and replace theold CONFIG_PROC_FSs in alsa code.With sound proc fs disabled, we can save about 9KB memorysize on X86_64 platform.Signed-off-by: Jie Yang Reviewed-by: Mark Brown Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

9203dd01 - ALSA: pcm: add IEC958 channel status helper

Sat, 09 May 2015 10:26:47 +0000

ALSA: pcm: add IEC958 channel status helperAdd a helper to create the IEC958 channel status from an ALSAsnd_pcm_runtime structure, taking account of the sample rate andsample size.Signed-off-by: Russell King Reviwed-by: Mark Brown Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

838d1631 - ALSA: pcm: add DRM ELD helper

Sat, 09 May 2015 10:26:42 +0000

ALSA: pcm: add DRM ELD helperAdd a helper for the EDID like data structure, which is typically passedfrom a HDMI adapter to its associated audio driver. This informs theaudio driver of the capabilities of the attached HDMI sink.Signed-off-by: Russell King Reviewed-by: Mark Brown Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile

9058cbe1 - ALSA: jack: implement kctl creating for jack devices

Mon, 27 Apr 2015 13:20:56 +0000

ALSA: jack: implement kctl creating for jack devicesCurrently the ALSA jack core registers only input devices for each jackregistered. These jack input devices are not readable by userspace devicesthat run as non root. This patch series will implement kctls inside thecore jack part, including kctls creating, status changing report, for bothHD-Audio and ASoC jack. This allows non root userspace to read jack statusand act on it.This patch adds a new API called snd_jack_add_new_kctl(), which will createa kcontrol, add it to the card, and also attach it to the jack kctl list.This patch also initialises the jack kctl list after jack is newed, andreports kctl status when jack insertion/removal events occur.snd_jack_new() is updated in the following patches to also support creatingphantom jacks and jack kcontrols. We then remove these duplicated featuresfrom HDA jack and have jack kctls handled by core throughout HDA and ASoC.Signed-off-by: Liam Girdwood Modified-by: Jie Yang Signed-off-by: Jie Yang Reveiwed-by: Mark Brown Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/Makefile