| nvmem.rst (4f2c0a4acffbec01079c28f839422e64ddeff004) | nvmem.rst (266570f496b90dea8fda893c2cf7c28d63ae2bd9) |
|---|---|
| 1.. SPDX-License-Identifier: GPL-2.0 2 3=============== 4NVMEM Subsystem 5=============== 6 7 Srinivas Kandagatla <srinivas.kandagatla@linaro.org> 8 --- 171 unchanged lines hidden (view full) --- 180 ... 181 * 182 0001000 183 1847. DeviceTree Binding 185===================== 186 187See Documentation/devicetree/bindings/nvmem/nvmem.txt | 1.. SPDX-License-Identifier: GPL-2.0 2 3=============== 4NVMEM Subsystem 5=============== 6 7 Srinivas Kandagatla <srinivas.kandagatla@linaro.org> 8 --- 171 unchanged lines hidden (view full) --- 180 ... 181 * 182 0001000 183 1847. DeviceTree Binding 185===================== 186 187See Documentation/devicetree/bindings/nvmem/nvmem.txt |
| 188 1898. NVMEM layouts 190================ 191 192NVMEM layouts are yet another mechanism to create cells. With the device 193tree binding it is possible to specify simple cells by using an offset 194and a length. Sometimes, the cells doesn't have a static offset, but 195the content is still well defined, e.g. tag-length-values. In this case, 196the NVMEM device content has to be first parsed and the cells need to 197be added accordingly. Layouts let you read the content of the NVMEM device 198and let you add cells dynamically. 199 200Another use case for layouts is the post processing of cells. With layouts, 201it is possible to associate a custom post processing hook to a cell. It 202even possible to add this hook to cells not created by the layout itself. |
|