Changes in Makefile

0113a99b - eeprom: Remove deprecated legacy eeprom driver

Sun, 24 Sep 2023 21:49:09 +0000

eeprom: Remove deprecated legacy eeprom driverDriver was marked deprecated 4 years ago, so it's time to remove it.This driver is the only i2c client driver using class I2C_CLASS_SPD.Apparently, as a follow-up step, we can remove I2C_CLASS_SPDaltogether.Signed-off-by: Heiner Kallweit Reviewed-by: Jean Delvare Link: https://lore.kernel.org/r/18241458-52db-4537-bead-d570801253c3@gmail.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/eeprom/Makefile

3b7584a2 - eeprom: New ee1004 driver for DDR4 memory

Sun, 07 Oct 2018 17:05:00 +0000

eeprom: New ee1004 driver for DDR4 memoryThe EEPROMs which hold the SPD data on DDR4 memory modules are nolonger standard AT24C02-compatible EEPROMs. They are 512-byte EEPROMswhich use only 1 I2C address for data access. You need to switchbetween the lower page and the upper page of data by sending commandson the SMBus.Signed-off-by: Jean Delvare Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/eeprom/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/misc/eeprom/Makefile

cfad6425 - eeprom: Add IDT 89HPESx EEPROM/CSR driver

Fri, 13 Jan 2017 12:16:52 +0000

eeprom: Add IDT 89HPESx EEPROM/CSR driver This driver provides an access to EEPROM of IDT PCIe-switches. IDT PCIe-switches expose a simple SMBus interface to perform IO-operations from/toEEPROM, which is located at private (so called Master) SMBus. The drivercreates a simple binary sysfs-file to have an access to the EEPROM usingthe SMBus-slave interface in the i2c-device susfs-directory: /sys/bus/i2c/devices/-/eepromIn case if read-only flag is specified at dts-node of the device, User-spaceapplications won't be able to write to the EEPROM sysfs-node. Additionally IDT 89HPESx SMBus interface has an ability to read/writevalues of device CSRs. This driver exposes debugfs-file to perform simpleIO-operations using that ability for just basic debug purpose. Particularlythe next file is created in the specific debugfs-directory: /sys/kernel/debug/idt_csr/Format of the debugfs-file value is: $ cat /sys/kernel/debug/idt_csr/-/; :So reading the content of the file gives current CSR address and it value.If User-space application wishes to change current CSR address, it can justwrite a proper value to the sysfs-file: $ echo "" > /sys/kernel/debug/idt_csr/-/If it wants to change the CSR value as well, the format of the writeoperation is: $ echo ":" > \ /sys/kernel/debug/idt_csr/-/;CSR address and value can be any of hexadecimal, decimal or octal format.Signed-off-by: Serge Semin Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/eeprom/Makefile

3d0b16a6 - nvmem: sunxi: Move the SID driver to the nvmem framework

Mon, 27 Jul 2015 11:17:09 +0000

nvmem: sunxi: Move the SID driver to the nvmem frameworkNow that we have the nvmem framework, we can consolidate the commondriver code. Move the driver to the framework, and hopefully, it willfix the sysfs file creation race.Signed-off-by: Maxime Ripard [srinivas.kandagatla: Moved to regmap based EEPROM framework]Signed-off-by: Srinivas Kandagatla Tested-by: Philipp Zabel Tested-by: Rajendra Nayak Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/eeprom/Makefile

9fd379e9 - ARM: sunxi: Initial support for Allwinner's Security ID fuses

Tue, 03 Sep 2013 10:33:27 +0000

ARM: sunxi: Initial support for Allwinner's Security ID fusesAllwinner has electric fuses (efuse) on their line of chips. This driverreads those fuses, seeds the kernel entropy and exports them as a sysfsnode.These fuses are most likely to be programmed at the factory, encodingthings like Chip ID, some sort of serial number, etc. and appear to bereasonably unique.While in theory, these should be writeable by the user, it will probablybe inconvenient to do so. Allwinner recommends that a certain input pin,labeled 'efuse_vddq', be connected to GND. To write these fuses however,a 2.5 V programming voltage needs to be applied to this pin.Even so, they can still be used to generate a board-unique mac from,board unique RSA key and seed the kernel RNG.On sun7i additional storage is available, this is initially used for anUEFI BOOT key, Secure JTAG key, HDMI-HDCP key and vendor specific keys.Currently supported are the following known chips:Allwinner sun4i (A10)Allwinner sun5i (A10s, A13)Allwinner sun7i (A20)Signed-off-by: Oliver Schinagl Acked-by: Maxime Ripard Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/misc/eeprom/Makefile

469dded1 - misc/eeprom: add eeprom access driver for digsy_mtc board

Tue, 26 Jul 2011 00:13:29 +0000

misc/eeprom: add eeprom access driver for digsy_mtc boardBoth displays on digsy_mtc board obtain their configuration from microwireEEPROMs which are connected to the SoC over GPIO lines. We need an easyway to access the EEPROMs to write the needed display configuration or toread out the currently programmed configuration. The genericeeprom_93xx46 SPI driver added by previous patch allows EEPROM access oversysfs. Using the simple driver added by this patch we provide used GPIOinterface and access control description on the board for genericeeprom_93xx46 driver and spi_gpio driver.Signed-off-by: Anatolij Gustschin Cc: Jonathan Cameron Cc: Grant Likely Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/misc/eeprom/Makefile

06b4501e - misc/eeprom: add driver for microwire 93xx46 EEPROMs

Tue, 26 Jul 2011 00:13:27 +0000

misc/eeprom: add driver for microwire 93xx46 EEPROMsAdd EEPROM driver for 93xx46 chips. It can also be used with spi_gpiodriver to access 93xx46 EEPROMs connected over GPIO lines. This driversupports read/write/erase access to the EEPROM chips over sysfs files.[rdunlap@xenotime.net: fix printk format]Signed-off-by: Anatolij Gustschin Cc: Jonathan Cameron Cc: Grant Likely Signed-off-by: Randy Dunlap Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/misc/eeprom/Makefile

4b364f23 - i2c/chips: Move max6875 to drivers/misc/eeprom

Mon, 15 Jun 2009 16:01:49 +0000

i2c/chips: Move max6875 to drivers/misc/eepromThis driver only reads the user EEPROM of that chip, so we can move itto the eeprom-directory in order to further clean up (and later remove)drivers/i2c/chips.The Kconfig text was updated to match the current functionality,dropping the meanwhile obsoleted parts.Defconfigs have been adapted.Signed-off-by: Wolfram Sang Acked-by: Ben Gardner Signed-off-by: Jean Delvare List of files: /linux-6.15/drivers/misc/eeprom/Makefile

dd7f8dbe - eeprom: More consistent symbol names

Mon, 26 Jan 2009 20:19:57 +0000

eeprom: More consistent symbol namesNow that all EEPROM drivers live in the same place, let's harmonizetheir symbol names.Also fix eeprom's dependencies, it definitely needs sysfs, and is nolonger experimental after many years in the kernel tree.Signed-off-by: Jean Delvare Acked-by: Wolfram Sang Cc: David Brownell List of files: /linux-6.15/drivers/misc/eeprom/Makefile

0eb6da20 - eeprom: Move 93cx6 eeprom driver to /drivers/misc/eeprom

Mon, 26 Jan 2009 20:19:54 +0000

eeprom: Move 93cx6 eeprom driver to /drivers/misc/eepromSigned-off-by: Wolfram Sang Signed-off-by: Jean Delvare List of files: /linux-6.15/drivers/misc/eeprom/Makefile

e51d565f - spi: Move at25 (for SPI eeproms) to /drivers/misc/eeprom

Mon, 26 Jan 2009 20:19:54 +0000

spi: Move at25 (for SPI eeproms) to /drivers/misc/eepromSigned-off-by: Wolfram Sang Signed-off-by: Jean Delvare List of files: /linux-6.15/drivers/misc/eeprom/Makefile

2e157888 - i2c: Move old eeprom driver to /drivers/misc/eeprom

Mon, 26 Jan 2009 20:19:53 +0000

i2c: Move old eeprom driver to /drivers/misc/eepromUpdate Kconfig text to specify this driver as I2C.Signed-off-by: Wolfram Sang Signed-off-by: Jean Delvare List of files: /linux-6.15/drivers/misc/eeprom/Makefile

5195e509 - i2c: Move at24 to drivers/misc/eeprom

Mon, 26 Jan 2009 20:19:53 +0000

i2c: Move at24 to drivers/misc/eepromAs drivers/i2c/chips is going to go away, move the driver todrivers/misc/eeprom. Other eeprom drivers may be moved here later, too.Update Kconfig text to specify this driver as I2C.Signed-off-by: Wolfram Sang Signed-off-by: Jean Delvare List of files: /linux-6.15/drivers/misc/eeprom/Makefile