Changes in Makefile

0d7bb85e - ARM: omap1: remove unused board files

Thu, 29 Sep 2022 13:38:56 +0000

ARM: omap1: remove unused board filesAll board support that was marked as 'unused' earlier cannow be removed, leaving the five machines that that stillhad someone using them in 2022, or that are supported inqemu.Cc: Aaro Koskinen Cc: Janusz Krzysztofik Cc: Tony Lindgren Cc: linux-omap@vger.kernel.orgSigned-off-by: Arnd Bergmann List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

980a637d - ARM: omap1: fix !ARCH_OMAP1_ANY link failures

Wed, 04 Jan 2023 08:35:09 +0000

ARM: omap1: fix !ARCH_OMAP1_ANY link failuresWhile compile-testing randconfig builds for the upcoming boardfileremoval, I noticed that an earlier patch of mine was completelybroken, and the introduction of CONFIG_ARCH_OMAP1_ANY only replacedone set of build failures with another one, now resulting inlink failures likeld: drivers/video/fbdev/omap/omapfb_main.o: in function `omapfb_do_probe':drivers/video/fbdev/omap/omapfb_main.c:1703: undefined reference to `omap_set_dma_priority'ld: drivers/dma/ti/omap-dma.o: in function `omap_dma_free_chan_resources':drivers/dma/ti/omap-dma.c:777: undefined reference to `omap_free_dma'drivers/dma/ti/omap-dma.c:1685: undefined reference to `omap_get_plat_info'ld: drivers/usb/gadget/udc/omap_udc.o: in function `next_in_dma':drivers/usb/gadget/udc/omap_udc.c:820: undefined reference to `omap_get_dma_active_status'I tried reworking it, but the resulting patch ended up much bigger thansimply avoiding the original problem of unused-function warnings likearch/arm/mach-omap1/mcbsp.c:76:30: error: unused variable 'omap1_mcbsp_ops' [-Werror,-Wunused-variable]As a result, revert the previous fix, and rearrange the code thatproduces warnings to hide them. For mcbsp, the #ifdef check cansimply be removed as the cpu_is_omapxxx() checks already achievethe same result, while in the io.c the easiest solution appears tobe to merge the common map bits into each soc specific portion.This gets cleaned in a nicer way after omap7xx support gets dropped,as the remaining SoCs all have the exact same I/O map.Fixes: 615dce5bf736 ("ARM: omap1: fix build with no SoC selected")Cc: stable@vger.kernel.orgAcked-by: Aaro Koskinen Signed-off-by: Arnd Bergmann List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

615dce5b - ARM: omap1: fix build with no SoC selected

Thu, 12 Sep 2019 08:11:24 +0000

ARM: omap1: fix build with no SoC selectedIn a multiplatform randconfig kernel, one can haveCONFIG_ARCH_OMAP1 enabled, but none of the specific SoCs.This leads to some build issues as the code is notmeant to deal with this configuration at the moment:arch/arm/mach-omap1/io.c:86:20: error: unused function 'omap1_map_common_io' [-Werror,-Wunused-function]arch/arm/mach-omap1/pm.h:113:2: error: "Power management for this processor not implemented yet" [-Werror,-W#warnings]Use the same trick as on OMAP2 and guard the actual compilationof platform code with another Makefile ifdef check basedon an option that depends on having at least one SoC enabled.The io.c file still needs to get compiled to allow buildingdevice drivers with a dependency on CONFIG_ARCH_OMAP1.Acked-by: Tony Lindgren Signed-off-by: Arnd Bergmann List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

16630718 - ARM: omap1: move plat/dma.c to mach/omap-dma.c

Fri, 27 Nov 2020 13:05:55 +0000

ARM: omap1: move plat/dma.c to mach/omap-dma.cMost of the interface functions in plat/dma.c are only used from theUSB driver, which is practically OMAP1 specific, except for compiletesting.The omap_get_plat_info(), omap_request_dma() and omap_free_dma()functions are never called on omap2 because of runtime checks.Acked-by: Tony Lindgren Signed-off-by: Arnd Bergmann List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

042c4884 - ARM: omap1: move lcd_dma code into omapfb driver

Mon, 05 Aug 2019 21:15:37 +0000

ARM: omap1: move lcd_dma code into omapfb driverThe omapfb driver is split into platform specific code for omap1, anddriver code that is also specific to omap1.Moving both parts into the driver directory simplifies the structureand avoids the dependency on certain omap machine header files.As mach/lcd_dma.h can not be included from include/linux/omap-dma.hany more now, move the omap_lcd_dma_running() declaration into theomap-dma header, which matches where it is defined.Acked-by: Bartlomiej Zolnierkiewicz Acked-by: Tony Lindgren Signed-off-by: Arnd Bergmann List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

c27ace2e - ARM: OMAP1: Makefile: Update for new MCBSP Kconfig option

Mon, 17 Dec 2018 12:21:36 +0000

ARM: OMAP1: Makefile: Update for new MCBSP Kconfig optionThe MCBSP config option has been changed.Signed-off-by: Peter Ujfalusi Acked-by: Tony Lindgren Signed-off-by: Mark Brown List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

c7b7b5cb - ARM: OMAP1: fix USB configuration for device-only setups

Tue, 04 Dec 2018 17:57:42 +0000

ARM: OMAP1: fix USB configuration for device-only setupsCurrently we do USB configuration only if the host mode (CONFIG_USB)is enabled. But it should be done also in the case of device-only setups,so change the condition to CONFIG_USB_SUPPORT. This allows to useomap_udc on Palm Tungsten E.Signed-off-by: Aaro Koskinen Signed-off-by: Tony Lindgren List of files: /linux-6.15/arch/arm/mach-omap1/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/arch/arm/mach-omap1/Makefile

dc7ad3a0 - ARM: OMAP1: Remove board support for VoiceBlue board

Thu, 13 Aug 2015 20:47:18 +0000

ARM: OMAP1: Remove board support for VoiceBlue boardRemove board support files for 10 years discontinued VoiceBlue board.Signed-off-by: Ladislav Michl Signed-off-by: Tony Lindgren List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

c869c75c - mailbox/omap: move the OMAP mailbox framework to drivers

Tue, 12 Mar 2013 22:55:29 +0000

mailbox/omap: move the OMAP mailbox framework to driversThe mailbox hardware (in OMAP) uses a queued mailbox interruptmechanism that provides a communication channel between processorsthrough a set of registers and their associated interrupt signalsby sending and receiving messages.The OMAP mailbox framework/driver code is moved to be underdrivers/mailbox, in preparation for adapting to a common mailboxdriver framework. This allows the build for OMAP mailbox to beenabled (it was disabled during the multi-platform support).As part of the migration from plat and mach code:- Kconfig symbols have been renamed to build OMAP1 or OMAP2+ drivers.- mailbox.h under plat-omap/plat/include has been split into a public and private header files. The public header has only the API related functions and types.- The module name mailbox.ko from plat-omap is changed to omap-mailbox.ko- The module name mailbox_mach.ko from mach-omapX is changed as mailbox_omap1.ko for OMAP1 mailbox_omap2.ko for OMAP2+Cc: Tony Lindgren [gregkh@linuxfoundation.org: ack for staging part]Acked-by: Greg Kroah-Hartman Signed-off-by: Omar Ramirez Luna Signed-off-by: Suman Anna List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

16d60bb8 - ARM: OMAP: Split fb.c to remove last remaining cpu_is_omap usage

Sun, 16 Dec 2012 19:39:40 +0000

ARM: OMAP: Split fb.c to remove last remaining cpu_is_omap usageLooks like we missed plat-omap/fb.c for cpu_is_omap usagemach-omap2. This is the last user of cpu_is_omap, so let'squickly fix it up so we can finally remove plat/cpu.h foromap2lus.We want to limit cpu_is_omap macro usage to mach-omap2 only sowe can make plat/cpu.h private. After this we can finally dropplat/cpu.h for omap2+.Cc: Tomi Valkeinen Signed-off-by: Tony Lindgren List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

f205cfaf - ARM: OMAP: Move omap1 specific code to local sram.c

Mon, 29 Oct 2012 21:46:30 +0000

ARM: OMAP: Move omap1 specific code to local sram.cLet's make the omap1 specific parts private to mach-omap1.These should not be in the shared code.Signed-off-by: Tony Lindgren List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

dafbeadf - ARM: mach-omap1: retire custom LED code

Tue, 13 Mar 2012 18:14:39 +0000

ARM: mach-omap1: retire custom LED codeSigned-off-by: Bryan Wu Acked-by: Tony Lindgren List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

31cde044 - ARM: OMAP1: board files: deduplicate and clean some NAND-related code

Fri, 13 Apr 2012 12:34:31 +0000

ARM: OMAP1: board files: deduplicate and clean some NAND-related codeThe H2, H3, Perseus2, and FSample board files all contain the sameduplicated code to handle NAND commands. That code is missingsome casts around conversions from unsigned long to void __iomem *.Consolidate the duplicated code into a new file,arch/arm/mach-omap1/board-nand.c. Resolve the sparse warnings byadding appropriate casts:arch/arm/mach-omap1/board-h2.c:193:9: warning: incorrect type in argument 1 (different base types)arch/arm/mach-omap1/board-h2.c:193:9: expected void const volatile [noderef] *arch/arm/mach-omap1/board-h2.c:193:9: got unsigned longarch/arm/mach-omap1/board-perseus2.c:157:9: warning: incorrect type in argument 1 (different base types)arch/arm/mach-omap1/board-perseus2.c:157:9: expected void const volatile [noderef] *arch/arm/mach-omap1/board-perseus2.c:157:9: got unsigned longarch/arm/mach-omap1/board-fsample.c:199:9: warning: incorrect type in argument 1 (different base types)arch/arm/mach-omap1/board-fsample.c:199:9: expected void const volatile [noderef] *arch/arm/mach-omap1/board-fsample.c:199:9: got unsigned longarch/arm/mach-omap1/board-h3.c:195:9: warning: incorrect type in argument 1 (different base types)arch/arm/mach-omap1/board-h3.c:195:9: expected void const volatile [noderef] *arch/arm/mach-omap1/board-h3.c:195:9: got unsigned longThanks to Arnd Bergmann for suggesting a cleanerimplementation of omap1_nand_cmd_ctl(), avoiding some casts.Signed-off-by: Paul Walmsley Cc: Brian Swetland Cc: Imre Deak Cc: Greg Lonnon Cc: Kevin Hilman Cc: Kevin Hilman Cc: Arnd Bergmann List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

6f3c1af2 - ARM: OMAP1: OCPI: move to mach-omap1/

Fri, 13 Apr 2012 12:34:27 +0000

ARM: OMAP1: OCPI: move to mach-omap1/Move the OMAP1 OCPI "bus" code to arch/arm/mach-omap1, since it isonly used on OMAP1 devices. In the long term, it probably makes senseto move the OCPI bus code to somewhere under drivers/.Signed-off-by: Paul Walmsley Cc: Tony Lindgren List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

3ead4679 - ARM: OMAP: Remove CONFIG_OMAP_MCBSP references

Fri, 09 Mar 2012 08:23:27 +0000

ARM: OMAP: Remove CONFIG_OMAP_MCBSP referencesThe McBSP driver stack has been moved to ASoC. The CONFIG_OMAP_MCBSP willbe removed since the CONFIG_SND_OMAP_SOC_MCBSP will trigger to build theMcBSP (audio) drivers.Signed-off-by: Peter Ujfalusi Acked-by: Tony Lindgren Signed-off-by: Liam Girdwood List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

97933d6c - ARM: OMAP1: dmtimer: conversion to platform devices

Tue, 20 Sep 2011 11:30:17 +0000

ARM: OMAP1: dmtimer: conversion to platform devicesConvert OMAP1 dmtimers into a platform devices and then registers withdevice model framework so that it can be bound to corresponding driver.Signed-off-by: Thara Gopinath Signed-off-by: Tarun Kanti DebBarma Reviewed-by: Santosh Shilimkar Acked-by: Cousson, Benoit Signed-off-by: Tony Lindgren List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

e9e35c5a - OMAP1: PM: register notifiers with generic clock ops even when !PM_RUNTIME

Tue, 14 Jun 2011 12:53:18 +0000

OMAP1: PM: register notifiers with generic clock ops even when !PM_RUNTIMEWhen runtime PM is disabled, device clocks need to be enabled ondevice add and disabled on device remove. This currently is nothappening because in the !PM_RUNTIME case, no notifiers are registeredfor OMAP1 devices.Fix this by ensuring notifiers are registered, even in the !PM_RUNTIME case.Reported-by: Janusz Krzysztofik Tested-by: Janusz Krzysztofik Signed-off-by: Kevin Hilman Signed-off-by: Tony Lindgren List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

ee54dba9 - ARM: OMAP: Allow platforms to hook reset cleanly

Fri, 28 Jan 2011 00:39:45 +0000

ARM: OMAP: Allow platforms to hook reset cleanlyThis adds a clean method to allow platforms to hook into the resetcode if they require to.Signed-off-by: Russell King Signed-off-by: Tony Lindgren List of files: /linux-6.15/arch/arm/mach-omap1/Makefile

05b5ca9b - omap1: Fix booting for 15xx and 730 with omap1_defconfig

Tue, 18 Jan 2011 20:42:23 +0000

omap1: Fix booting for 15xx and 730 with omap1_defconfigFor omap15xx and 730 we need to use the MPU timeras the 32K timer is not available. For omap16xxwe want to use the 32K timer because of PM. Fix thisby allowing to build in both timers.Signed-off-by: Tony Lindgren List of files: /linux-6.15/arch/arm/mach-omap1/Makefile