Changes in Makefile

65dd2f67 - regmap: Provide a ram backed regmap with raw support

Sun, 11 Jun 2023 13:25:02 +0000

regmap: Provide a ram backed regmap with raw supportProvide a simple, 16 bit only, RAM backed regmap which supports raw I/O foruse in testing.Signed-off-by: Mark Brown Link: https://lore.kernel.org/r/20230610-regcache-raw-kunit-v1-1-583112cd28ac@kernel.orgSigned-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

f033c26d - regmap: Add maple tree based register cache

Thu, 30 Mar 2023 00:10:24 +0000

regmap: Add maple tree based register cacheThe current state of the art for sparse register maps is therbtree cache. This works well for most applications but isn'talways ideal for sparser register maps since the rbtree can getdeep, requiring a lot of walking. Fortunately the kernel has adata structure intended to address this very problem, the mapletree. Provide an initial implementation of a register cachebased on the maple tree to start taking advantage of it.The entries stored in the maple tree are arrays of registervalues, with the maple tree keys holding the register addresses.We store data in host native format rather than device nativeformat as we do for rbtree, this will be a benefit for deviceswhere we don't marshal data within regmap and simplifies the codebut will result in additional CPU overhead when syncing the cacheon devices where we do marshal data in regmap.This should work well for a lot of devices, though there's someadditional areas that could be looked at such as caching thelast accessed entry like we do for rbtree and trying to minimisethe maple tree level locking. We should also use bulk writesrather than single register writes when resyncing the cache wherepossible, even if we don't store in device native format.Very small register maps may continue to to better with rbtreelonger term.Signed-off-by: Mark Brown Link: https://lore.kernel.org/r/20230325-regcache-maple-v3-2-23e271f93dc7@kernel.orgSigned-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

2238959b - regmap: Add some basic kunit tests

Sun, 26 Mar 2023 14:11:13 +0000

regmap: Add some basic kunit testsOn the theory that it's better to make a start let's add some KUnit testsfor regmap. Currently this is a bit of a mess but it passes and hopefullywill at some point help catch problems. We provide very basic cover formost of the core functionality that operates at the register level,repeating each test for each cache type in order to exercise the caches.There is no coverage of anything to do with the bulk operations at the buslevel or formatting for byte stream buses yet.Each test creates it's own regmap since the cache structures are builtincrementally, meaning we gain coverage from the different accesspatterns, and some of the tests cover different init scenarios.Signed-off-by: Mark Brown Link: https://lore.kernel.org/r/20230324-regmap-kunit-v2-2-b208801dc2c8@kernel.org List of files: /linux-6.15/drivers/base/regmap/Makefile

f6352424 - regmap: Add RAM backed register map

Sun, 26 Mar 2023 14:11:12 +0000

regmap: Add RAM backed register mapAdd a register map that is a simple array of memory, for use inKUnit testing of the framework. This is not exposed in regmap.hsince I can't think of a non-test use case, it is purely for useinternally. To facilitate testing we track if registers have beenread or written to.Signed-off-by: Mark Brown Link: https://lore.kernel.org/r/20230324-regmap-kunit-v2-1-b208801dc2c8@kernel.org List of files: /linux-6.15/drivers/base/regmap/Makefile

1e2bae6a - regmap: Removed compressed cache support

Fri, 24 Mar 2023 16:21:49 +0000

regmap: Removed compressed cache supportThe compressed register cache support has assumptions that make it hard tocover in testing, mainly that it requires raw registers defaults beprovided. Rather than either address these assumptions or leave it untestedby the forthcoming KUnit tests let's remove it, the use case is quite thinand there are no current users.Signed-off-by: Mark Brown Link: https://lore.kernel.org/r/20230324-regcache-lzo-v1-1-08c5d63e2a5e@kernel.org List of files: /linux-6.15/drivers/base/regmap/Makefile

bf0d29fb - regmap: Add FSI bus support

Wed, 02 Nov 2022 20:51:44 +0000

regmap: Add FSI bus supportAdd regmap support for the FSI bus.Signed-off-by: Eddie James Link: https://lore.kernel.org/r/20221102205148.1334459-2-eajames@linux.ibm.comSigned-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

1f89d2fe - regmap: Add MDIO bus support

Mon, 17 May 2021 19:28:03 +0000

regmap: Add MDIO bus supportBasic support for MDIO bus access. Support only includes clause-22register access, with 5-bit addresses, and 16-bit wide registers.Signed-off-by: Sander Vanheule Link: https://lore.kernel.org/r/63b99a2fec2c4ea3c461d59d451af8d675ecf312.1621279162.git.sander@svanheule.netSigned-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

fb5103f9 - regmap/SoundWire: sdw: add support for SoundWire 1.2 MBQ

Tue, 03 Nov 2020 17:22:23 +0000

regmap/SoundWire: sdw: add support for SoundWire 1.2 MBQThe SoundWire 1.1 specification only allowed for reads and writes ofbytes. The SoundWire 1.2 specification adds a new capability totransfer "Multi-Byte Quantities" (MBQ) across the bus. The transfersstill happens one-byte-at-a-time, but the update is atomic.For example when writing a 16-bit volume, the first byte transferredis only taken into account when the second byte is successfullytransferred.The mechanism is symmetrical for read and writes:- On a read, the address of the last byte to be read is modified bysetting the MBQ bit- On a write, the address of all but the last byte to be written aremodified by setting the MBQ bit. The address for the last byte relieson the MBQ bit being cleared.The current definitions for MBQ-based controls in the SDCA draftstandard are limited to 16 bits for volumes, so for now this is theonly supported format. An update will be provided if and when supportfor 24-bit and 32-bit values is specified by the SDCA standard.One possible objection is that this code could have been handled withregmap-sdw.c. However this is a new spec addition not handled by everySoundWire 1.1 and non-SDCA device, so there's no reason to load codethat will never be used.Also in practice it's extremely unlikely that CONFIG_REGMAP would notbe selected with CONFIG_REGMAP_MBQ selected. However there's nofunctional dependency between the two modules so they can be selectedseparately.Reviewed-by: Rander Wang Reviewed-by: Guennadi Liakhovetski Reviewed-by: Kai Vehmanen Signed-off-by: Pierre-Louis Bossart Signed-off-by: Bard Liao Reviewed-by: Vinod Koul Link: https://lore.kernel.org/r/20201103172226.4278-3-yung-chuan.liao@linux.intel.comSigned-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

7f9fb673 - regmap: add Intel SPI Slave to AVMM Bus Bridge support

Wed, 19 Aug 2020 07:34:56 +0000

regmap: add Intel SPI Slave to AVMM Bus Bridge supportThis patch add support for regmap APIs that are intended to be used bythe drivers of some SPI slave chips which integrate the "SPI slave toAvalon Master Bridge" (spi-avmm) IP.The spi-avmm IP acts as a bridge to convert encoded streams of bytesfrom the host to the chip's internal register read/write on Avalon bus.The driver implements the register read/write operations for a genericSPI master to access the sub devices behind spi-avmm bridge.Signed-off-by: Xu Yilun Signed-off-by: Wu Hao Signed-off-by: Matthew Gerlach Signed-off-by: Russ Weight Reviewed-by: Tom Rix Reviewed-by: Luis Claudio R. Goncalves Link: https://lore.kernel.org/r/1597822497-25107-2-git-send-email-yilun.xu@intel.comSigned-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

6445500b - regmap: add i3c bus support

Thu, 06 Jun 2019 15:12:02 +0000

regmap: add i3c bus supportAdd basic support for i3c bus.This is a simple implementation that only give supportfor SDR Read and Write commands.Signed-off-by: Vitor Soares Signed-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

bcf7eac3 - regmap: add SCCB support

Mon, 16 Jul 2018 15:47:48 +0000

regmap: add SCCB supportThis adds Serial Camera Control Bus (SCCB) support for regmap API thatis intended to be used by some of Omnivision sensor drivers.The ov772x and ov9650 drivers are going to use this SCCB regmap API.The ov772x driver was previously only worked with the i2c controllerdrivers that support I2C_FUNC_PROTOCOL_MANGLING, because the ov772xdevice doesn't support repeated starts. After commit 0b964d183cbf("media: ov772x: allow i2c controllers withoutI2C_FUNC_PROTOCOL_MANGLING"), reading ov772x register is replaced withissuing two separated i2c messages in order to avoid repeated start.Using this SCCB regmap hides the implementation detail.The ov9650 driver also issues two separated i2c messages to read theregisters as the device doesn't support repeated start. So it canmake use of this SCCB regmap.Cc: Mark Brown Cc: Peter Rosin Cc: Sebastian Reichel Cc: Wolfram Sang Cc: Sylwester Nawrocki Cc: Jacopo Mondi Cc: Laurent Pinchart Cc: Hans Verkuil Cc: Sakari Ailus Cc: Mauro Carvalho Chehab Signed-off-by: Akinobu Mita Signed-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

7c22ce6e - regmap: Add SoundWire bus support

Mon, 08 Jan 2018 10:20:59 +0000

regmap: Add SoundWire bus supportSoundWire bus provides sdw_read() and sdw_write() APIs for Slavedevices to program the registers. Provide support in regmap forSoundWire bus.Signed-off-by: Hardik T Shah Signed-off-by: Sanyog Kale Reviewed-by: Philippe Ombredanne Acked-by: Pierre-Louis Bossart Reviewed-by: Takashi Iwai Signed-off-by: Vinod Koul Signed-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

7d6f7fb0 - regmap: add SLIMbus support

Mon, 11 Dec 2017 23:43:02 +0000

regmap: add SLIMbus supportThis patch adds support to read/write SLIMbus value elements.Currently it only supports byte read/write. Adding this support inregmap would give codec drivers more flexibility when there are morethan 2 control interfaces like SLIMbus, i2c.Without this patch each codec driver has to directly call SLIMbus valueelement apis, and this could would get messy once we want to add i2cinterface to it.Signed-off-by: Srinivas Kandagatla Reviwed-by: Mark Brown Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/base/regmap/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/base/regmap/Makefile

cc5d0db3 - regmap: Add 1-Wire bus support

Fri, 02 Jun 2017 07:06:27 +0000

regmap: Add 1-Wire bus supportAdd basic support regmap (register map access) API for 1-Wire busSigned-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

34a730aa - regmap: make LZO cache optional

Fri, 02 Jun 2017 13:15:37 +0000

regmap: make LZO cache optionalCommit 2cbbb579bcbe3 ("regmap: Add the LZO cache support") added supportfor LZO compression in regcache, but there were never any users addedafterwards. Since LZO support itself has its own size, it currently israther a deoptimization.So make it optional by introducing a symbol that can be selected bydrivers wanting to make use of it.Saves e.g. ~46 kB on MIPS (size of LZO support + regcache LZO code).Signed-off-by: Jonas Gorski Signed-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

f58078da - regmap: Move tracing header into drivers/base/regmap

Thu, 19 Mar 2015 21:50:47 +0000

regmap: Move tracing header into drivers/base/regmapThe tracing events for regmap are confined to the regmap subsystem. Italso requires accessing an internal header. Instead of including theinternal header from a generic file location, move the tracing fileinto the regmap directory.Also rename the regmap tracing header to trace.h, as it is redundant tokeep the regmap.h name when it is in the regmap directory.Signed-off-by: Steven Rostedt Signed-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

22853223 - regmap: ac97: Add generic AC'97 callbacks

Tue, 18 Nov 2014 18:45:51 +0000

regmap: ac97: Add generic AC'97 callbacksUse the recently added support for bus operations to provide a standardmapping for AC'97 register I/O.Signed-off-by: Mark Brown Signed-off-by: Lars-Peter Clausen List of files: /linux-6.15/drivers/base/regmap/Makefile

a01779f8 - regmap: add SPMI support

Mon, 28 Oct 2013 18:12:35 +0000

regmap: add SPMI supportAdd basic support for the System Power Management Interface (SPMI) bus.This is a simple implementation which only implements register accessesvia the Extended Register Read/Write Long commands.Signed-off-by: Josh Cartwright Signed-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile

2ac902ce - regmap: flat: Add flat cache type

Wed, 19 Dec 2012 14:51:55 +0000

regmap: flat: Add flat cache typeWhile for I2C and SPI devices the overhead of using rbtree for devices withonly one block of registers is negligible the same isn't always going tobe true for MMIO devices where the I/O costs are very much lower. Caterfor these devices by adding a simple flat array type for them where thelookups are simple array accesses, taking us right back to the originalASoC cache implementation.Thanks to Magnus Damm for the discussion which prompted this.Signed-off-by: Mark Brown List of files: /linux-6.15/drivers/base/regmap/Makefile