Commit 673d2cc5 authored by Sean Anderson's avatar Sean Anderson Committed by Greg Kroah-Hartman

doc: nvmem: Remove references to regmap

Since commit 795ddd18 ("nvmem: core: remove regmap dependency"),
nvmem devices do not use the regmap API. Remove references to it from
the documentation.
Signed-off-by: default avatarSean Anderson <sean.anderson@seco.com>
Signed-off-by: default avatarSrinivas Kandagatla <srinivas.kandagatla@linaro.org>
Link: https://lore.kernel.org/r/20220220151527.17216-11-srinivas.kandagatla@linaro.orgSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent f7845101
...@@ -26,9 +26,7 @@ was a rather big abstraction leak. ...@@ -26,9 +26,7 @@ was a rather big abstraction leak.
This framework aims at solve these problems. It also introduces DT This framework aims at solve these problems. It also introduces DT
representation for consumer devices to go get the data they require (MAC 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 Addresses, SoC/Revision ID, part numbers, and so on) from the NVMEMs.
framework is based on regmap, so that most of the abstraction available in
regmap can be reused, across multiple types of buses.
NVMEM Providers NVMEM Providers
+++++++++++++++ +++++++++++++++
...@@ -60,9 +58,6 @@ For example, a simple qfprom case:: ...@@ -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 Users of board files can define and register nvmem cells using the
nvmem_cell_table struct:: nvmem_cell_table struct::
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment