Changes in Makefile

78c08247 - mtd: Support kmsg dumper based on pstore/blk

Wed, 25 Mar 2020 08:55:06 +0000

mtd: Support kmsg dumper based on pstore/blkThis introduces mtdpstore, which is similar to mtdoops but morepowerful. It uses pstore/blk, and aims to store panic and oops logs toa flash partition, where pstore can later read back and present as filesin the mounted pstore filesystem.To make mtdpstore work, the "blkdev" of pstore/blk should be setas MTD device name or MTD device number. For more details, seeDocumentation/admin-guide/pstore-blk.rstThis solves a number of issues:- Work duplication: both of pstore and mtdoops do the same job storing panic/oops log. They have very similar logic, registering to kmsg dumper and storing logs to several chunks one by one.- Layer violations: drivers should provides methods instead of polices. MTD should provide read/write/erase operations, and allow a higher level drivers to provide the chunk management, kmsg dump configuration, etc.- Missing features: pstore provides many additional features, including presenting the logs as files, logging dump time and count, and supporting other frontends like pmsg, console, etc.Signed-off-by: WeiXiong Liao Link: https://lore.kernel.org/lkml/20200511233229.27745-11-keescook@chromium.org/Link: https://lore.kernel.org/r/1589266715-4168-1-git-send-email-liaoweixiong@allwinnertech.comSigned-off-by: Kees Cook List of files: /linux-6.15/drivers/mtd/Makefile

a3f12a35 - mtd: parsers: Move CMDLINE parser

Tue, 13 Aug 2019 07:25:31 +0000

mtd: parsers: Move CMDLINE parserThis moves the CMDLINE partition parser down into theparser subdirectory. No functional change.Signed-off-by: Linus Walleij Signed-off-by: Richard Weinberger List of files: /linux-6.15/drivers/mtd/Makefile

c5da56f7 - mtd: parsers: Move OF parser

Tue, 13 Aug 2019 07:25:30 +0000

mtd: parsers: Move OF parserThis moves the OF/device tree partition parser down into theparser subdirectory. No functional change.Signed-off-by: Linus Walleij Signed-off-by: Richard Weinberger List of files: /linux-6.15/drivers/mtd/Makefile

ac37d352 - mtd: parsers: Move BCM63xx parser

Tue, 13 Aug 2019 07:25:29 +0000

mtd: parsers: Move BCM63xx parserThis moves the BCM63xx partition parser down into theparser subdirectory. No functional change.Signed-off-by: Linus Walleij Signed-off-by: Richard Weinberger List of files: /linux-6.15/drivers/mtd/Makefile

11f74023 - mtd: parsers: Move BCM47xx parser

Tue, 13 Aug 2019 07:25:28 +0000

mtd: parsers: Move BCM47xx parserThis moves the BCM47xx partition parser down into theparser subdirectory. No functional change.Signed-off-by: Linus Walleij Signed-off-by: Richard Weinberger List of files: /linux-6.15/drivers/mtd/Makefile

5a4a335a - mtd: parsers: Move TI AR7 parser

Tue, 13 Aug 2019 07:25:27 +0000

mtd: parsers: Move TI AR7 parserThis moves the TI AR7 partition parser down into theparser subdirectory. No functional change.Signed-off-by: Linus Walleij Signed-off-by: Richard Weinberger List of files: /linux-6.15/drivers/mtd/Makefile

dcc7d344 - mtd: Add support for HyperBus memory devices

Tue, 25 Jun 2019 07:57:44 +0000

mtd: Add support for HyperBus memory devicesCypress' HyperBus is Low Signal Count, High Performance Double Data RateBus interface between a host system master and one or more slaveinterfaces. HyperBus is used to connect microprocessor, microcontroller,or ASIC devices with random access NOR flash memory (called HyperFlash)or self refresh DRAM (called HyperRAM).Its a 8-bit data bus (DQ[7:0]) with Read-Write Data Strobe (RWDS)signal and either Single-ended clock(3.0V parts) or Differential clock(1.8V parts). It uses ChipSelect lines to select b/w multiple slaves.At bus level, it follows a separate protocol described in HyperBusspecification[1].HyperFlash follows CFI AMD/Fujitsu Extended Command Set (0x0002) similarto that of existing parallel NORs. Since HyperBus is x8 DDR bus,its equivalent to x16 parallel NOR flash with respect to bits per clockcycle. But HyperBus operates at >166MHz frequencies.HyperRAM provides direct random read/write access to flash memoryarray.But, HyperBus memory controllers seem to abstract implementation detailsand expose a simple MMIO interface to access connected flash.Add support for registering HyperFlash devices with MTD framework. MTDmaps framework along with CFI chip support framework are used to supportcommunicating with flash.Framework is modelled along the lines of spi-nor framework. HyperBusmemory controller (HBMC) drivers calls hyperbus_register_device() toregister a single HyperFlash device. HyperFlash core parses MMIO accessinformation from DT, sets up the map_info struct, probes CFI flash andregisters it with MTD framework.Some HBMC masters need calibration/training sequence[3] to be carriedout, in order for DLL inside the controller to lock, by reading a knownstring/pattern. This is done by repeatedly reading CFI QueryIdentification String. Calibration needs to be done before trying to detectflash as part of CFI flash probe.HyperRAM is not supported at the moment.HyperBus specification can be found at[1]HyperFlash datasheet can be found at[2][1] https://www.cypress.com/file/213356/download[2] https://www.cypress.com/file/213346/download[3] http://www.ti.com/lit/ug/spruid7b/spruid7b.pdf Table 12-5741. HyperFlash Access SequenceSigned-off-by: Vignesh Raghavendra Signed-off-by: Miquel Raynal List of files: /linux-6.15/drivers/mtd/Makefile

2aa3b8e1 - mtd: afs: Move AFS partition parser to parsers subdir

Thu, 02 May 2019 14:30:26 +0000

mtd: afs: Move AFS partition parser to parsers subdirThis moves the AFS (ARM Firmware Suite) partition parserfor NOR flash down into the parsers subdirectory.Signed-off-by: Linus Walleij Signed-off-by: Richard Weinberger List of files: /linux-6.15/drivers/mtd/Makefile

43f1fd01 - mtd: Move Redboot partition parser

Sat, 10 Nov 2018 20:01:25 +0000

mtd: Move Redboot partition parserThis moves the Redboot partition parser down to the parserssubdirectory.Signed-off-by: Linus Walleij Signed-off-by: Boris Brezillon List of files: /linux-6.15/drivers/mtd/Makefile

26777d37 - mtd: Move onenand code base to drivers/mtd/nand/onenand

Sun, 18 Feb 2018 16:05:16 +0000

mtd: Move onenand code base to drivers/mtd/nand/onenandMove onenand code base to the drivers/mtd/nand directory in the hopethat someday someone will patch it to use the generic NAND helpers.If it never happens, at least we'll have all NAND related support in asingle directory and not spread over the drivers/mtd/ directory.Signed-off-by: Boris Brezillon List of files: /linux-6.15/drivers/mtd/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/Makefile

99352afe - mtd: extract TRX parser out of bcm47xxpart into a separated module

Wed, 21 Jun 2017 06:26:47 +0000

mtd: extract TRX parser out of bcm47xxpart into a separated moduleThis makes TRX parsing code reusable with other platforms and parsers.Please note this patch doesn't really change anything in the existingcode, just moves it. There is still some place for improvement (e.g.working on non-hacky method of checking rootfs format) but it's notreally a subject of this change.Signed-off-by: Rafał Miłecki Signed-off-by: Brian Norris List of files: /linux-6.15/drivers/mtd/Makefile

e43b2061 - mtd: spi-nor: shorten Kconfig naming

Wed, 09 Apr 2014 03:30:25 +0000

mtd: spi-nor: shorten Kconfig namingSigned-off-by: Brian Norris Reviewed-by: Marek Vasut Acked-by: Huang Shijie List of files: /linux-6.15/drivers/mtd/Makefile

b199489d - mtd: spi-nor: add the framework for SPI NOR

Mon, 24 Feb 2014 10:37:37 +0000

mtd: spi-nor: add the framework for SPI NORThis patch cloned most of the m25p80.c. In theory, it adds a new spi-nor layer.Before this patch, the layer is like: MTD ------------------------ m25p80 ------------------------ spi bus driver ------------------------ SPI NOR chipAfter this patch, the layer is like: MTD ------------------------ spi-nor ------------------------ m25p80 ------------------------ spi bus driver ------------------------ SPI NOR chipWith the spi-nor controller driver(Freescale Quadspi), it looks like: MTD ------------------------ spi-nor ------------------------ fsl-quadspi ------------------------ SPI NOR chipNew APIs: spi_nor_scan: used to scan a spi-nor flash.Signed-off-by: Huang Shijie Acked-by: Marek Vasut [Brian: rebased to include additional m25p_ids[] entry]Signed-off-by: Brian Norris List of files: /linux-6.15/drivers/mtd/Makefile

660685d9 - mtd: merge mtdchar module with mtdcore

Thu, 14 Mar 2013 11:27:40 +0000

mtd: merge mtdchar module with mtdcoreThe MTD subsystem has historically tried to be as configurable as possible. Theside-effect of this is that its configuration menu is rather large, and we aregradually shrinking it. For example, we recently merged partitions support withthe mtdcore.This patch does the next step - it merges the mtdchar module to mtdcore. And inthis case this is not only about eliminating too fine-grained separation andsimplifying the configuration menu. This is also about eliminating seeminglyuseless kernel module.Indeed, mtdchar is a module that allows user-space making use of MTD devicesvia /dev/mtd* character devices. If users do not enable it, they simply cannotuse MTD devices at all. They cannot read or write the flash contents. Is it asane and useful setup? I believe not. And everyone just enables mtdchar.Having mtdchar separate is also a little bit harmful. People sometimes miss thefact that they need to enable an additional configuration option to haveuser-space MTD interfaces, and then they wonder why on earth the kernel doesnot allow using the flash? They spend time asking around.Thus, let's just get rid of this module and make it part of mtd core.Note, mtdchar had additional configuration option to enable OTP interfaces,which are present on some flashes. I removed that option as well - it saves areally tiny amount space.[dwmw2: Strictly speaking, you can mount file systems on MTD devices just fine without the mtdchar (or mtdblock) devices; you just can't do other manipulations directly on the underlying device. But still I agree that it makes sense to make this unconditional. And Yay! we get to kill off an instance of checking CONFIG_foo_MODULE, which is an abomination that should never happen.]Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse List of files: /linux-6.15/drivers/mtd/Makefile

3cf7f131 - mtd: bcm47part driver for BCM47XX chipsets

Thu, 30 Aug 2012 05:41:16 +0000

mtd: bcm47part driver for BCM47XX chipsetsThis driver provides parser detecting partitions on BCM47XX flashmemories. It has many differences in comparison to BCM63XX, like:1) Different CFE with no more trivial MAGICs2) More partitions types (board_data, ML, POT)3) Supporting more than 1 flash on a devicewhich resulted in decision of writing new parser.It uses generic mtd interface and was successfully tested with NetgearWNDR4500 router which has 2 flash memories: serial one and NAND one.Signed-off-by: Rafał Miłecki Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse List of files: /linux-6.15/drivers/mtd/Makefile

70a3c167 - mtd: maps: bcm963xx-flash: make CFE partition parsing an mtd parser

Mon, 05 Dec 2011 15:08:08 +0000

mtd: maps: bcm963xx-flash: make CFE partition parsing an mtd parserRecent BCM63XX devices support a variety of flash types (parallel, SPI,NAND) and share the partition layout. To prevent code duplication makethe CFE partition parsing code a stand alone mtd parser to allow SPI orNAND flash drivers to use it.Signed-off-by: Jonas Gorski Acked-by: Florian Fainelli Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse List of files: /linux-6.15/drivers/mtd/Makefile

d6137bad - mtd: make ofpart buildable as a separate module

Sun, 26 Jun 2011 21:02:59 +0000

mtd: make ofpart buildable as a separate moduleAs ofpart now uses a standard mtd partitions parser interface, make itbuildable as a separate module. Also provide MODULE_DESCRIPTION andMODULE_AUTHOR for this module.Signed-off-by: Dmitry Eremin-Solenikov Acked-by: Randy Dunlap Signed-off-by: Artem Bityutskiy List of files: /linux-6.15/drivers/mtd/Makefile

6a8a98b2 - mtd: kill CONFIG_MTD_PARTITIONS

Mon, 23 May 2011 09:23:43 +0000

mtd: kill CONFIG_MTD_PARTITIONSNow that none of the drivers use CONFIG_MTD_PARTITIONS we can removeit from Kconfig and the last remaining uses.Signed-off-by: Jamie Iles Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse List of files: /linux-6.15/drivers/mtd/Makefile

a3215902 - mtd: Add mtdswap block driver

Mon, 14 Feb 2011 14:16:11 +0000

mtd: Add mtdswap block driverAdd a driver for allowing an mtd device to be used as a block device forswapping. The block device is volatile, and the mapping of swapped pagesis not stored on flash.Signed-off-by: Jarkko Lavinen Tested-by: Artem Bityutskiy Signed-off-by: David Woodhouse List of files: /linux-6.15/drivers/mtd/Makefile