aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace
diff options
context:
space:
mode:
authorRafał Miłecki <[email protected]>2023-12-15 11:13:58 +0000
committerGreg Kroah-Hartman <[email protected]>2023-12-15 13:15:02 +0100
commit1e37bf84afacd5ba17b7a13a18ca2bc78aff05c0 (patch)
tree821a41db0be7eb4ec03260b41774e27dad06d566 /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace
parenta2a8aefecbd0f87d6127951cef33b3def8439057 (diff)
nvmem: brcm_nvram: store a copy of NVRAM content
This driver uses MMIO access for reading NVRAM from a flash device. Underneath there is a flash controller that reads data and provides mapping window. Using MMIO interface affects controller configuration and may break real controller driver. It was reported by multiple users of devices with NVRAM stored on NAND. Modify driver to read & cache NVRAM content during init and use that copy to provide NVMEM data when requested. On NAND flashes due to their alignment NVRAM partitions can be quite big (1 MiB and more) while actual NVRAM content stays quite small (usually 16 to 32 KiB). To avoid allocating so much memory check for actual data length. Link: https://lore.kernel.org/linux-mtd/CACna6rwf3_9QVjYcM+847biTX=K0EoWXuXcSMkJO1Vy_5vmVqA@mail.gmail.com/ Fixes: 3fef9ed0627a ("nvmem: brcm_nvram: new driver exposing Broadcom's NVRAM") Cc: <[email protected]> Cc: Arınç ÜNAL <[email protected]> Cc: Florian Fainelli <[email protected]> Cc: Scott Branden <[email protected]> Signed-off-by: Rafał Miłecki <[email protected]> Acked-by: Arınç ÜNAL <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace')
0 files changed, 0 insertions, 0 deletions