Changes in Makefile

cf4ccd1c - mtd: physmap: Use -y instead of -objs in Makefile

Wed, 08 May 2024 15:11:53 +0000

mtd: physmap: 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: Andy Shevchenko Signed-off-by: Miquel Raynal Link: https://lore.kernel.org/linux-mtd/20240508151222.1443491-1-andriy.shevchenko@linux.intel.com List of files: /linux-6.15/drivers/mtd/maps/Makefile

77bf0325 - mtd: Remove support for Carillo Ranch driver

Fri, 08 Dec 2023 22:47:03 +0000

mtd: Remove support for Carillo Ranch driverAs far as anybody can tell, this product never shipped. If it did,it shipped in 2007 and nobody has access to one any more. Remove themtd NOR driver.Signed-off-by: Matthew Wilcox (Oracle) Signed-off-by: Miquel Raynal Link: https://lore.kernel.org/linux-mtd/20231208224703.1603264-2-willy@infradead.org List of files: /linux-6.15/drivers/mtd/maps/Makefile

7ceeb601 - mtd: maps: ixp4xx: Drop driver

Thu, 07 Apr 2022 21:08:44 +0000

mtd: maps: ixp4xx: Drop driverThis custom maps driver was never used with the device treeenabled IXP4xx systems, which use the physmap add-on fromcommit 2aba2f2a704d("mtd: physmap_of: add a hook for Intel IXP4xx flash probing")Since kernel v5.18-rc1 IXP4xx is only booting from the devicetree so drop this old driver.Signed-off-by: Linus Walleij Signed-off-by: Miquel Raynal Link: https://lore.kernel.org/linux-mtd/20220407210844.2489682-1-linus.walleij@linaro.org List of files: /linux-6.15/drivers/mtd/maps/Makefile

5a8df928 - MIPS: TXX9: Remove rbtx4939 board support

Tue, 30 Nov 2021 16:45:55 +0000

MIPS: TXX9: Remove rbtx4939 board supportNo active MIPS user own this board, so let's remove it.Signed-off-by: Thomas Bogendoerfer Reviewed-by: Geert Uytterhoeven Tested-by: Geert Uytterhoeven List of files: /linux-6.15/drivers/mtd/maps/Makefile

60d06079 - mtd: maps: remove dead MTD map driver for PMC-Sierra MSP boards

Tue, 17 Aug 2021 10:45:31 +0000

mtd: maps: remove dead MTD map driver for PMC-Sierra MSP boardsCommit 1b00767fd8e1 ("MIPS: Remove PMC MSP71xx platform") removes theconfig PMC_MSP in ./arch/mips/Kconfig.Hence, since then, the corresponding MTD map driver for PMC-Sierra MSPboards is dead code. Remove this dead driver.Signed-off-by: Lukas Bulwahn Signed-off-by: Miquel Raynal Link: https://lore.kernel.org/linux-mtd/20210817104531.12675-1-lukas.bulwahn@gmail.com List of files: /linux-6.15/drivers/mtd/maps/Makefile

b3e79e76 - mtd: physmap: Add Baikal-T1 physically mapped ROM support

Sun, 20 Sep 2020 11:14:44 +0000

mtd: physmap: Add Baikal-T1 physically mapped ROM supportBaikal-T1 Boot Controller provides an access to a RO storages, which arephysically mapped into the SoC MMIO space. In particularly there areInternal ROM embedded into the SoC with a pre-installed firmware,externally attached SPI flash (also accessed in the read-only mode) and amemory region, which mirrors one of them in accordance with the currentlyenabled system boot mode (also called Boot ROM).This commit adds the Internal ROM support to the physmap driver of the MTDkernel subsystem. The driver will create the Internal ROM MTD as long asit is defined in the system dts file. The physically mapped SPI flashregion will be used to implement the SPI-mem interface. The mirroringmemory region won't be accessible directly since it's redundant due toboth bootable regions being exposed anyway.Note we had to create a dedicated code for the ROMs since read from thecorresponding memory regions must be done via the dword-aligned addresses.Signed-off-by: Serge Semin Cc: Alexey Malahov Cc: Pavel Parkhomenko Cc: Lee Jones Cc: linux-mips@vger.kernel.orgSigned-off-by: Miquel Raynal Link: https://lore.kernel.org/linux-mtd/20200920111445.21816-1-Sergey.Semin@baikalelectronics.ru List of files: /linux-6.15/drivers/mtd/maps/Makefile

2aba2f2a - mtd: physmap_of: add a hook for Intel IXP4xx flash probing

Sun, 20 Oct 2019 23:00:42 +0000

mtd: physmap_of: add a hook for Intel IXP4xx flash probingIn order to support device tree probing of IXP4xx NOR flashchips, a certain big-endian or mixed-endian memory accesspattern need to be used.I have opted to use the pattern set by previous plug-insto physmap for Gemini and Versatile, just override somefunctions and reuse most of the physmap core code as itis to minimize maintenance.Parts of drivers/mtd/ixp4xx.c are copied into this file.After we have IXP4xx converted fully to device tree, thedrivers/mtd/ixp4xx.c file will be deleted and this willbe the only access pattern to the IXP4xx flash.I did not keep the quirk in the flash write functionafter probe, where the old code for a while checks foraccess to odd addresses, fails and assigns a "faster"write function once it has convinced probe to only use2-byte accesses. As we mandate that this device shouldbe using bank-width = <2> this should not be a problemunless misconfigured.Signed-off-by: Linus Walleij Signed-off-by: Miquel Raynal List of files: /linux-6.15/drivers/mtd/maps/Makefile

d24dbd75 - mtd: maps: Get rid of the latch-addr-flash driver

Thu, 04 Oct 2018 22:41:42 +0000

mtd: maps: Get rid of the latch-addr-flash driverLooks like this driver was initially added to support the NOR on theDA830-EVM (Davinci) board, but the board file update was never merged.Keeping unused drivers just adds to the maintenance burden, so let'sremove it if nobody uses it.Cc: David Griego Cc: Aleksey Makarov Cc: Sergei Shtylyov Cc: Savinay Dharmappa Signed-off-by: Boris Brezillon Acked-by: Sekhar Nori List of files: /linux-6.15/drivers/mtd/maps/Makefile

ba32ce95 - mtd: maps: Merge gpio-addr-flash.c into physmap-core.c

Fri, 19 Oct 2018 07:49:07 +0000

mtd: maps: Merge gpio-addr-flash.c into physmap-core.cControlling some MSB address lines using GPIOs is just a smalldeviation from the generic physmap logic, and merging those two driversallows us to share most of the probe logic, which is a good thing.Also, the gpio-addr-flash driver is unused since the removal ofthe blackfin arch in v4.17, so we can safely remove the old driverwithout risking breaking existing boards.Signed-off-by: Boris Brezillon Reviewed-by: Ricardo Ribalda Delgado Tested-by: Ricardo Ribalda Delgado Acked-by: Linus Walleij List of files: /linux-6.15/drivers/mtd/maps/Makefile

6ca15cfa - mtd: maps: Rename physmap_of_{versatile, gemini} into physmap-{versatile, gemini}

Fri, 19 Oct 2018 07:49:05 +0000

mtd: maps: Rename physmap_of_{versatile, gemini} into physmap-{versatile, gemini}Now that the physmap_of driver is gone, the gemini and versativeextensions are part of the physmap driver. Rename the source files andthe config option to reflect this.Signed-off-by: Boris Brezillon Reviewed-by: Ricardo Ribalda Delgado Acked-by: Linus Walleij List of files: /linux-6.15/drivers/mtd/maps/Makefile

642b1e8d - mtd: maps: Merge physmap_of.c into physmap-core.c

Fri, 19 Oct 2018 07:49:04 +0000

mtd: maps: Merge physmap_of.c into physmap-core.cThere's no real reason to have two separate driver for the DT and pdatacase. Just do what we do everywhere else and handle DT and pdataparsing in the same driver.Signed-off-by: Boris Brezillon Reviewed-by: Ricardo Ribalda Delgado Acked-by: Linus Walleij List of files: /linux-6.15/drivers/mtd/maps/Makefile

0c3def9b - mtd: maps: Prepare merging of physmap and physmap_of

Fri, 19 Oct 2018 07:49:03 +0000

mtd: maps: Prepare merging of physmap and physmap_ofWe want to merge the physmap and physmap_of driver, but before we cando that we must prepare things to create physmap.o out of several .cfiles. Rename physmap.c into physmap-core.c and add a new Makefilerule to create physmap.o (right now it only contains physmap-core.o).Signed-off-by: Boris Brezillon Reviewed-by: Ricardo Ribalda Delgado Acked-by: Linus Walleij List of files: /linux-6.15/drivers/mtd/maps/Makefile

5741a164 - mtd: maps: remove bfin-async-flash driver

Wed, 14 Mar 2018 16:30:22 +0000

mtd: maps: remove bfin-async-flash driverThe blackfin architecture is getting removed, so this driverhas become obsolete.Signed-off-by: Arnd Bergmann Signed-off-by: Boris Brezillon List of files: /linux-6.15/drivers/mtd/maps/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/drivers/mtd/maps/Makefile

8c925b26 - mtd: physmap_of: really fix the physmap add-ons

Thu, 30 Mar 2017 15:36:39 +0000

mtd: physmap_of: really fix the physmap add-onsThe current way of building the of_physmap add-ons result in justthe add-on being in the object code, and not the actual coreimplementation and regress the Gemini and Versatile.Bake the physmap_of.o object by baking physmap_of_core.o andadding the Versatile and/or Gemini add-ons to the final object.Rename the source file physmap_of_core.c to get the desiredbuild components.Suggested-by: Boris Brezillon Fixes: 4f04f68e1598 ("mtd: physmap_of: fixup gemini/versatile dependencies")Signed-off-by: Linus Walleij Acked-by: Boris Brezillon Signed-off-by: Brian Norris List of files: /linux-6.15/drivers/mtd/maps/Makefile

4f04f68e - mtd: physmap_of: fixup gemini/versatile dependencies

Thu, 09 Feb 2017 02:09:37 +0000

mtd: physmap_of: fixup gemini/versatile dependenciesphysmap_of sort of depends on the gemini and versatile modules (whenthey're enabled), but this isn't expressed in Kconfig. Let's just mergethe modules all together, when enabled. Then we can avoid exporting afew symbols, and the versatile and gemini code can now be modular again(the below commit accidentally made them built-in only).Resolves errors like this:ERROR: "of_flash_probe_versatile" [drivers/mtd/maps/physmap_of.ko] undefined!ERROR: "of_flash_probe_gemini" [drivers/mtd/maps/physmap_of.ko] undefined!Fixes: 56ff337ea433 ("mtd: physmap_of: add a hook for Gemini flash probing")Cc: Linus Walleij Signed-off-by: Brian Norris Reviewed-by: Linus Walleij List of files: /linux-6.15/drivers/mtd/maps/Makefile

56ff337e - mtd: physmap_of: add a hook for Gemini flash probing

Sat, 28 Jan 2017 21:50:48 +0000

mtd: physmap_of: add a hook for Gemini flash probingIn order to support device tree probing of Gemini NOR flashchips, a certain register in the syscon needs to be pokedto enable parallel flash mode.Such things used to happen in "necessarily different" boardfile code, and this indeed was also done for the Gemini, sothe MTD driver could treat it as any memory-mapped NOR flash,but this is not the way in the future: board files need togo, and hardware concerns distributed down to the applicabledrivers.This adds a hook in the same way that the Versatile did: ifthe Kconfig symbol is not selected the net total of supportingGemini should be zero bytes of added code. To live up to thispromise, also the return value error print from the Versatileextra probe call get to be removed in this patch, all printingneed to happen in the add-ons.Cc: Janos Laube Cc: Paulius Zaleckas Cc: Hans Ulli Kroll Cc: Florian Fainelli Signed-off-by: Linus Walleij Acked-by: Marek Vasut Signed-off-by: Brian Norris List of files: /linux-6.15/drivers/mtd/maps/Makefile

c5f9d6b1 - physmap_of: ensure versatile code is reachable

Mon, 25 Apr 2016 23:01:40 +0000

physmap_of: ensure versatile code is reachableWith the newly added physmap_of_versatile code, we get a build errorwhen physmap_of is in a module, because of_flash_probe_versatileis not exported:ERROR: "of_flash_probe_versatile" [drivers/mtd/maps/physmap_of.ko] undefined!This adds the export, and changes the Makefile so that the code isalso put into a loadable module rather than built-in when physmap_ofitself is a module.Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/mtd/maps/Makefile

b0afd44b - mtd: physmap_of: add a hook for Versatile write protection

Tue, 26 Jan 2016 10:58:07 +0000

mtd: physmap_of: add a hook for Versatile write protectionIn order to support device tree probing of Versatile NOR flashchips, there must be a way to add the VPP (write protection)enable/disable callback. The register in question is in thesystem controllers of these machines. Apart from this quirk,the ARM flash chips are standard CFI flash chips from variousvendors.Additionally, the Integrator/AP require you to set up the externalbus interface (EBI) to allow writes to the chip select where theflash memory is connected.Solve this by looking for the arm,versatile-flash compatiblestring in the flash device tree node. In the driver,add a special hook to check for the various Versatile syscons andregister a callback for .set_vpp() if this compatible is present.Provide a special Kconfig entry for the addon hook so it willnot be compiled in if the Versatile boards are not supported.Stubs in the header file make sure the impact will be zero onother platforms. (Compilers optimze this out.)With this patch, a large slew of ARM board file code can beremoved.Cc: Grant Likely Cc: Rob Herring Cc: Arnd Bergmann Signed-off-by: Linus Walleij List of files: /linux-6.15/drivers/mtd/maps/Makefile

795add9a - mtd: remove obsolete JEDEC mapping drivers

Mon, 13 May 2013 14:40:39 +0000

mtd: remove obsolete JEDEC mapping driversJEDEC device support was removed in v2.6.22. (It had been marked asBROKEN (indirectly) since at least v2.6.12.)When it was removed the two JEDEC mapping drivers that depended on itshould have been removed too. Do so now.Signed-off-by: Paul Bolle Acked-by: Brian Norris Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse List of files: /linux-6.15/drivers/mtd/maps/Makefile