diff options
author | Sean Anderson <sean.anderson@seco.com> | 2022-02-20 15:15:24 +0000 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-02-21 18:00:30 +0100 |
commit | 673d2cc5c1e7d31ee0597f6e18b45dcd257bc5d2 (patch) | |
tree | 842515c58692c78705fd93e55fbd7c8f825b75a7 | |
parent | f78451012b9e159afdba31c3eb69f223a9f42adc (diff) | |
download | linux-stable-673d2cc5c1e7d31ee0597f6e18b45dcd257bc5d2.tar.gz linux-stable-673d2cc5c1e7d31ee0597f6e18b45dcd257bc5d2.tar.bz2 linux-stable-673d2cc5c1e7d31ee0597f6e18b45dcd257bc5d2.zip |
doc: nvmem: Remove references to regmap
Since commit 795ddd18d38f ("nvmem: core: remove regmap dependency"),
nvmem devices do not use the regmap API. Remove references to it from
the documentation.
Signed-off-by: Sean Anderson <sean.anderson@seco.com>
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Link: https://lore.kernel.org/r/20220220151527.17216-11-srinivas.kandagatla@linaro.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-rw-r--r-- | Documentation/driver-api/nvmem.rst | 7 |
1 files changed, 1 insertions, 6 deletions
diff --git a/Documentation/driver-api/nvmem.rst b/Documentation/driver-api/nvmem.rst index 287e86819640..56352ad1b1b0 100644 --- a/Documentation/driver-api/nvmem.rst +++ b/Documentation/driver-api/nvmem.rst @@ -26,9 +26,7 @@ was a rather big abstraction leak. This framework aims at solve these problems. It also introduces DT representation for consumer devices to go get the data they require (MAC -Addresses, SoC/Revision ID, part numbers, and so on) from the NVMEMs. This -framework is based on regmap, so that most of the abstraction available in -regmap can be reused, across multiple types of buses. +Addresses, SoC/Revision ID, part numbers, and so on) from the NVMEMs. NVMEM Providers +++++++++++++++ @@ -60,9 +58,6 @@ For example, a simple qfprom case:: ... } -It is mandatory that the NVMEM provider has a regmap associated with its -struct device. Failure to do would return error code from nvmem_register(). - Users of board files can define and register nvmem cells using the nvmem_cell_table struct:: |