Changes in Makefile

edc66cf0 - microblaze: Remove gcc flag for non existing early_printk.c file

Thu, 11 Apr 2024 08:21:44 +0000

microblaze: Remove gcc flag for non existing early_printk.c fileearly_printk support for removed long time ago but compilation flag forftrace still points to already removed file that's why remove that linetoo.Fixes: 96f0e6fcc9ad ("microblaze: remove redundant early_printk support")Signed-off-by: Michal Simek Link: https://lore.kernel.org/r/5493467419cd2510a32854e2807bcd263de981a0.1712823702.git.michal.simek@amd.com List of files: /linux-6.15/arch/microblaze/kernel/Makefile

32164845 - kbuild: use obj-y instead extra-y for objects placed at the head

Sat, 24 Sep 2022 18:19:14 +0000

kbuild: use obj-y instead extra-y for objects placed at the headThe objects placed at the head of vmlinux need special treatments: - arch/$(SRCARCH)/Makefile adds them to head-y in order to place them before other archives in the linker command line. - arch/$(SRCARCH)/kernel/Makefile adds them to extra-y instead of obj-y to avoid them going into built-in.a.This commit gets rid of the latter.Create vmlinux.a to collect all the objects that are unconditionallylinked to vmlinux. The objects listed in head-y are moved to the headof vmlinux.a by using 'ar m'.With this, arch/$(SRCARCH)/kernel/Makefile can consistently use obj-yfor builtin objects.There is no *.o that is directly linked to vmlinux. Drop unneeded codein scripts/clang-tools/gen_compile_commands.py.$(AR) mPi needs 'T' to workaround the llvm-ar bug. The fix was suggestedby Nathan Chancellor [1].[1]: https://lore.kernel.org/llvm/YyjjT5gQ2hGMH0ni@dev-arch.thelio-3990X/Signed-off-by: Masahiro Yamada Tested-by: Nick Desaulniers Reviewed-by: Nicolas Schier List of files: /linux-6.15/arch/microblaze/kernel/Makefile

05cdf457 - microblaze: Remove noMMU code

Thu, 26 Nov 2020 13:32:25 +0000

microblaze: Remove noMMU codeThis configuration is obsolete and likely none is really using it. That'swhy remove it to simplify code.Note about CONFIG_MMU in hw_exception_handler.S is left intentionallyfor better comment understanding.Cc: Mike Rapoport Cc: Arnd Bergmann Signed-off-by: Michal Simek Acked-by: Mike Rapoport Acked-by: Arnd Bergmann Link: https://lore.kernel.org/r/43486cab370e0c0a79860120b71e0caac75a7e44.1606397528.git.michal.simek@xilinx.com List of files: /linux-6.15/arch/microblaze/kernel/Makefile

45df561a - microblaze: consolidate GPIO reset handling

Tue, 19 Jun 2018 21:36:20 +0000

microblaze: consolidate GPIO reset handlingNow that platform.c only has the GPIO reset handling left, move theinitcall to reset.c and remove platform.c.Cc: Michal Simek Signed-off-by: Rob Herring Signed-off-by: Michal Simek List of files: /linux-6.15/arch/microblaze/kernel/Makefile

5cf8da7b - microblaze: Remove architecture heart beat code

Tue, 12 Jun 2018 10:46:17 +0000

microblaze: Remove architecture heart beat codeThere is no reason to keep this gpio based code in architecture. Useledtrig-heartbeat.c instead which is much more flexible then thisancient code.Signed-off-by: Michal Simek Reviewed-by: Linus Walleij List of files: /linux-6.15/arch/microblaze/kernel/Makefile

96f0e6fc - microblaze: remove redundant early_printk support

Wed, 28 Mar 2018 02:06:59 +0000

microblaze: remove redundant early_printk supportWith earlycon support now enabled, the arch specific early_printk supportcan be removed.Signed-off-by: Rob Herring Cc: Michal Simek Signed-off-by: Michal Simek List of files: /linux-6.15/arch/microblaze/kernel/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/microblaze/kernel/Makefile

0547dc78 - microblaze/irqchip: Move intc driver to irqchip

Mon, 14 Nov 2016 12:13:45 +0000

microblaze/irqchip: Move intc driver to irqchipThe Xilinx AXI Interrupt Controller IP block is used by the MIPSbased xilfpga platform and a few PowerPC based platforms.Move the interrupt controller code out of arch/microblaze so thatit can be used by everyoneTested-by: Michal Simek Signed-off-by: Zubair Lutfullah Kakakhel Signed-off-by: Marc Zyngier List of files: /linux-6.15/arch/microblaze/kernel/Makefile

32db31da - microblaze: Remove unused prom_parse.c

Thu, 18 Dec 2014 14:30:49 +0000

microblaze: Remove unused prom_parse.cof_parse_dma_window is completely unused.Signed-off-by: Michal Simek List of files: /linux-6.15/arch/microblaze/kernel/Makefile

c24cf712 - microblaze: Remove platform folder

Mon, 07 Apr 2014 11:05:00 +0000

microblaze: Remove platform folderThere is no reason to use platform folder structure now.Everything is OF driven.Signed-off-by: Michal Simek List of files: /linux-6.15/arch/microblaze/kernel/Makefile

9e77dab6 - microblaze: Remove selfmodified feature

Tue, 27 Aug 2013 07:57:52 +0000

microblaze: Remove selfmodified featureThis was experimental feature which has never beenwidely used because it expects GCC behaviour.Also remove INTC_BASE and TIMER_BASE macros.Signed-off-by: Michal Simek List of files: /linux-6.15/arch/microblaze/kernel/Makefile

16caadb8 - microblaze: Use generic init_task

Thu, 03 May 2012 09:02:55 +0000

microblaze: Use generic init_taskSame code. Use the generic version.Signed-off-by: Thomas Gleixner Cc: Michal Simek Link: http://lkml.kernel.org/r/20120503085034.881532838@linutronix.de List of files: /linux-6.15/arch/microblaze/kernel/Makefile

9e1491de - microblaze: Fix ftrace

Fri, 18 Mar 2011 12:52:27 +0000

microblaze: Fix ftrace- Do not trace idle loop which takes a lot time- Fix cache handling in generic ftrace code- Do not trace lib functions ashldi3, ashrdi3, lshrdi3 Functions are called from generic ftrace code which can't be tracedSigned-off-by: Michal Simek List of files: /linux-6.15/arch/microblaze/kernel/Makefile

2d5973cb - microblaze: Add KGDB support

Tue, 03 Aug 2010 09:45:08 +0000

microblaze: Add KGDB supportKgdb uses brki r16, 0x18 instruction to calllow level _debug_exception function which savecurrent state to pt_regs and call microblaze_kgdb_breakfunction. _debug_exception should be called only fromthe kernel space. User space calling is not supportedbecause user application debugging uses different handling.pt_regs_to_gdb_regs loads additional special registerswhich can't be changed * Enable KGDB in Kconfig * Remove ancient not-tested KGDB support * Remove ancient _debug_exception code from entry.SOnly MMU KGDB support is supported.Signed-off-by: Michal Simek CC: Jason Wessel CC: John Williams CC: Edgar E. Iglesias CC: linux-kernel@vger.kernel.orgAcked-by: Jason Wessel List of files: /linux-6.15/arch/microblaze/kernel/Makefile

ce3266c0 - microblaze: Add stack unwinder

Tue, 27 Apr 2010 17:37:54 +0000

microblaze: Add stack unwinderImplement intelligent backtracing by searching for stack frame creation,and emitting only return addresses. Use print_hex_dump() to display theentire binary kernel stack.Limitation: MMU kernels are not currently able to trace beyond a system trap(interrupt, syscall, etc.). It is the intent of this patch to provideinfrastructure that can be extended to add this capability later.Changes from V1:* Removed checks in find_frame_creation() that prevented location of the frame creation instruction in heavily optimized code* Various formatting/commenting/file location tweaks per review comments* Dropped Kconfig option to enable STACKTRACE as something logically separateSigned-off-by: Steven J. Magnani List of files: /linux-6.15/arch/microblaze/kernel/Makefile

c0dd394c - of: remove of_default_bus_ids

Fri, 23 Jul 2010 18:19:24 +0000

of: remove of_default_bus_idsThis list used was by only two platforms with all other platforms defining anown list of valid bus id's to pass to of_platform_bus_probe. This patch:i) copies the default list to the two platforms that depended on it (powerpc)ii) remove the usage of of_default_bus_ids in of_platform_bus_probeiii) removes the definition of the list from all architectures that defined itPassing a NULL 'matches' parameter to of_platform_bus_probe is still valid; thefunction returns no error in that case as the NULL value is equivalent to anempty list.Signed-off-by: Jonas Bonn [grant.likely@secretlab.ca: added __initdata annotations, warn on and return error on missing match table, and fix whitespace errors]Signed-off-by: Grant Likely List of files: /linux-6.15/arch/microblaze/kernel/Makefile

94c09319 - of: Merge of_device_alloc() and of_device_make_bus_id()

Tue, 08 Jun 2010 13:48:14 +0000

of: Merge of_device_alloc() and of_device_make_bus_id()This patch merges the common routines of_device_alloc() andof_device_make_bus_id() from powerpc and microblaze.Signed-off-by: Grant Likely CC: Michal Simek CC: Grant Likely CC: Benjamin Herrenschmidt CC: Stephen Rothwell CC: microblaze-uclinux@itee.uq.edu.auCC: linuxppc-dev@ozlabs.orgCC: devicetree-discuss@lists.ozlabs.org List of files: /linux-6.15/arch/microblaze/kernel/Makefile

ccfe27d7 - microblaze: Support DMA

Thu, 14 Jan 2010 10:21:02 +0000

microblaze: Support DMAAdd DMA support for Microblaze. There are some part of this new feature:1. Basic DMA support2. Enable DMA debug option3. Setup notifierAd 1. dma-mapping come from powerpc and x86 version and it is based ongeneric dma-mapping-common.hAd 2. DMA support debug features which is used in generic file.For more information please look at Documentation/DMA-API.txtAd 3. notifier is very important to setup dma_ops. Without this partfor example ll_temac driver failed because there are no setup dma operations.Signed-off-by: Michal Simek List of files: /linux-6.15/arch/microblaze/kernel/Makefile

7d241ff0 - microblaze: ftrace: Add dynamic trace support

Thu, 10 Dec 2009 13:15:44 +0000

microblaze: ftrace: Add dynamic trace supportWith dynamic function tracer, by default, _mcount is defined as an"empty" function, it returns directly without any more action. Whenenabling it in user-space, it will jump to a real tracingfunction(ftrace_caller), and do the real job for us.Differ from the static function tracer, dynamic function tracer providestwo functions ftrace_make_call()/ftrace_make_nop() to enable/disable thetracing of some indicated kernel functions(set_ftrace_filter).In the kernel version, there is only one "_mcount" string for everykernel function, so, we just need to match this one in mcount_regex ofscripts/recordmcount.pl.For more information please look at code and Documentation/trace folder.Steven ACK that scripts/recordmcount.pl part.Acked-by: Steven Rostedt Signed-off-by: Michal Simek List of files: /linux-6.15/arch/microblaze/kernel/Makefile

2fd7c761 - microblaze: ftrace: add static function tracer

Mon, 16 Nov 2009 08:40:14 +0000

microblaze: ftrace: add static function tracerIf -pg of gcc is enabled with CONFIG_FUNCTION_TRACER=y. a calling to_mcount will be inserted into each kernel function. so, there is apossibility to trace the kernel functions in _mcount.This patch add the specific _mcount support for static functiontracing. by default, ftrace_trace_function is initialized asftrace_stub(an empty function), so, the default _mcount will introducevery little overhead. after enabling ftrace in user-space, it will jumpto a real tracing function and do static function tracing for us.Commit message from Wu Zhangjin Signed-off-by: Michal Simek List of files: /linux-6.15/arch/microblaze/kernel/Makefile