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/seq/Makefile

81fd444a - ALSA: seq: Bind UMP device

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

ALSA: seq: Bind UMP deviceThis patch introduces a new ALSA sequencer client for the kernel UMPobject, snd-seq-ump-client. It's a UMP version of snd-seq-mididriver, while this driver creates a sequencer client per UMP endpointwhich contains (fixed) 16 ports.The UMP rawmidi device is opened in APPEND mode for output, so thatmultiple sequencer clients can share the same UMP endpoint, as well asthe legacy UMP rawmidi devices that are opened in APPEND mode, too.For input, on the other hand, the incoming data is processed on thefly in the dedicated hook, hence it doesn't open a rawmidi device.The UMP packet group is updated upon delivery depending on the targetsequencer port (which corresponds to the actual UMP group).Each sequencer port sets a new port type bit,SNDRV_SEQ_PORT_TYPE_MIDI_UMP, in addition to the other standardtypes for MIDI.Reviewed-by: Jaroslav Kysela Link: https://lore.kernel.org/r/20230523075358.9672-33-tiwai@suse.deSigned-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/seq/Makefile

e9e02819 - ALSA: seq: Automatic conversion of UMP events

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

ALSA: seq: Automatic conversion of UMP eventsThis patch enables the automatic conversion of UMP events from/to thelegacy ALSA sequencer MIDI events. Also, as UMP itself has twodifferent modes (MIDI 1.0 and MIDI 2.0), yet another convertersbetween them are needed, too. Namely, we have conversions between thelegacy and UMP like: - seq legacy event -> seq UMP MIDI 1.0 event - seq legacy event -> seq UMP MIDI 2.0 event - seq UMP MIDI 1.0 event -> seq legacy event - seq UMP MIDI 2.0 event -> seq legacy eventand the conversions between UMP MIDI 1.0 and 2.0 clients like: - seq UMP MIDI 1.0 event -> seq UMP MIDI 2.0 event - seq UMP MIDI 2.0 event -> seq UMP MIDI 1.0 eventThe translation is per best-effort; some MIDI 2.0 specific events areignored when translated to MIDI 1.0.Reviewed-by: Jaroslav Kysela Link: https://lore.kernel.org/r/20230523075358.9672-31-tiwai@suse.deSigned-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/seq/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/seq/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/seq/Makefile

0181307a - ALSA: seq: Reorganize kconfig and build

Fri, 09 Jun 2017 12:40:18 +0000

ALSA: seq: Reorganize kconfig and buildThis is a slightly intensive rewrite of Kconfig and Makefile aboutALSA sequencer stuff.The first major change is that the kconfig items for the sequencer aremoved to sound/core/seq/Kconfig. OK, that's easy.The substantial change is that, instead of hackish top-level moduleselection in Makefile, we define a Kconfig item for each sequencermodule. The driver that requires such sequencer components selectexclusively the kconfig items. This is more straightforward andstandard way.Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/seq/Makefile

3d774d5e - ALSA: seq: Allow the tristate build of OSS emulation

Fri, 09 Jun 2017 12:06:46 +0000

ALSA: seq: Allow the tristate build of OSS emulationCurrently OSS sequencer emulation is tied with ALSA sequencer core,both are built in the same level; i.e. when CONFIG_SND_SEQUENCER=y,the OSS sequencer emulation is also always built-in, even though thefunctionality can be built as an individual module.This patch changes the rule and allows users to build snd-seq-ossmodule while others are built-in. Essentially, it's just a few simplechanges in Kconfig and Makefile. Some driver codes like opl3 need toconvert from the simple ifdef to IS_ENABLED(). But that's all.You might wonder how about the dependency: right, it can be messy, butit still works. Since we rewrote the sequencer binding with thestandard bus, the driver can be bound at any time on demand. So, thesynthesizer driver module can be loaded individually from the OSSemulation core before/after it.Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/seq/Makefile

b816db9d - ALSA: core: Fix randconfig build wrt CONFIG_PROC_FS

Fri, 29 May 2015 05:01:28 +0000

ALSA: core: Fix randconfig build wrt CONFIG_PROC_FSThere are a few leftover CONFIG_PROC_FS forgotten to replace withCONFIG_SND_PROC_FS.Fixes: cd6a65036f0e ('ALSA: replace CONFIG_PROC_FS with CONFIG_SND_PROC_FS')Reported-by: Jim Davis Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/seq/Makefile

85d14318 - ALSA: core: Build conditionally and remove superfluous ifdefs

Thu, 23 Apr 2015 08:34:34 +0000

ALSA: core: Build conditionally and remove superfluous ifdefsMinor cleanups of Makefile to build some codes conditionally so thata few ifdefs can be reduced.Acked-by: Jaroslav Kysela Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/seq/Makefile

f96e0808 - ALSA: OSS sequencer should be initialized after snd_seq_system_client_init

Sun, 19 Jul 2009 16:28:34 +0000

ALSA: OSS sequencer should be initialized after snd_seq_system_client_initWhen build SND_SEQUENCER in kernel then OSS sequencer(alsa_seq_oss_init)is initialized before System (snd_seq_system_client_init) which leads tomemory leak :unreferenced object 0xf6b0e680 (size 256): comm "swapper", pid 1, jiffies 4294670753 backtrace: [] create_object+0x135/0x204 [] kmemleak_alloc+0x26/0x4c [] kmem_cache_alloc+0x72/0xff [] seq_create_client1+0x22/0x160 [] snd_seq_create_kernel_client+0x72/0xef [] snd_seq_oss_create_client+0x86/0x142 [] alsa_seq_oss_init+0xf6/0x155 [] do_one_initcall+0x4f/0x111 [] kernel_init+0x115/0x166 [] kernel_thread_helper+0x7/0x10 [] 0xffffffffunreferenced object 0xf688a580 (size 64): comm "swapper", pid 1, jiffies 4294670753 backtrace: [] create_object+0x135/0x204 [] kmemleak_alloc+0x26/0x4c [] kmem_cache_alloc+0x72/0xff [] snd_seq_pool_new+0x1c/0xb8 [] seq_create_client1+0x87/0x160 [] snd_seq_create_kernel_client+0x72/0xef [] snd_seq_oss_create_client+0x86/0x142 [] alsa_seq_oss_init+0xf6/0x155 [] do_one_initcall+0x4f/0x111 [] kernel_init+0x115/0x166 [] kernel_thread_helper+0x7/0x10 [] 0xffffffffunreferenced object 0xf6b0e480 (size 256): comm "swapper", pid 1, jiffies 4294670754 backtrace: [] create_object+0x135/0x204 [] kmemleak_alloc+0x26/0x4c [] kmem_cache_alloc+0x72/0xff [] snd_seq_create_port+0x51/0x21c [] snd_seq_ioctl_create_port+0x57/0x13c [] snd_seq_do_ioctl+0x4a/0x69 [] snd_seq_kernel_client_ctl+0x33/0x49 [] snd_seq_oss_create_client+0xf5/0x142 [] alsa_seq_oss_init+0xf6/0x155 [] do_one_initcall+0x4f/0x111 [] kernel_init+0x115/0x166 [] kernel_thread_helper+0x7/0x10 [] 0xffffffffThe correct order should be :System (snd_seq_system_client_init) should be initialized beforeOSS sequencer(alsa_seq_oss_init) which is equivalent to :1. insmod sound/core/seq/snd-seq-device.ko2. insmod sound/core/seq/snd-seq.ko3. insmod sound/core/seq/snd-seq-midi-event.ko4. insmod sound/core/seq/oss/snd-seq-oss.koIncluding sound/core/seq/oss/Makefile after other seq modulesfixes the ordering and memory leak.Signed-off-by: Jaswinder Singh Rajput Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/seq/Makefile

0528c749 - ALSA: clean up the logic for building sequencer modules

Tue, 26 May 2009 15:07:52 +0000

ALSA: clean up the logic for building sequencer modulesInstead of mangling the CONFIG_* variables in the makefiles over andover, set a few helper variables in Kconfig.Signed-off-by: Michal Marek Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/seq/Makefile

e5723b41 - [ALSA] Remove sequencer instrument layer

Tue, 30 Oct 2007 11:17:17 +0000

[ALSA] Remove sequencer instrument layerRemove sequencer instrument layer from the tree.This mechanism hasn't been used much with the actual devices. The onlyreasonable user was OPL3 loader, and now it was rewritten to use hwdepinstead. So, let's remove the rest of rotten codes.Signed-off-by: Takashi Iwai Signed-off-by: Jaroslav Kysela List of files: /linux-6.15/sound/core/seq/Makefile

c1017a4c - [ALSA] Changed Jaroslav Kysela's e-mail from perex@suse.cz to perex@perex.cz

Mon, 15 Oct 2007 07:50:19 +0000

[ALSA] Changed Jaroslav Kysela's e-mail from perex@suse.cz to perex@perex.czSigned-off-by: Jaroslav Kysela List of files: /linux-6.15/sound/core/seq/Makefile

08844847 - [ALSA] Fix dependency of GUS driver

Thu, 30 Jun 2005 07:55:31 +0000

[ALSA] Fix dependency of GUS driverALSA sequencerAdd the missing snd-seq-midi-emul to SND_GUS_SYNTH list.Signed-off-by: Takashi Iwai List of files: /linux-6.15/sound/core/seq/Makefile

1da177e4 - Linux-2.6.12-rc2

Sat, 16 Apr 2005 22:20:36 +0000

Linux-2.6.12-rc2Initial git repository build. I'm not bothering with the full history,even though we have it. We can create a separate "historical" gitarchive of that later if we want to, and in the meantime it's about3.2GB when imported into git - space that would just make the earlygit days unnecessarily complicated, when we don't have a lot of goodinfrastructure for it.Let it rip! List of files: /linux-6.15/sound/core/seq/Makefile