Searched hist:d5bbb5021ce8d9ff561c7469f5b4589ccb3bc4a6 (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/include/linux/ |
| H A D | nvram.h | diff d5bbb5021ce8d9ff561c7469f5b4589ccb3bc4a6 Mon Jan 14 22:18:56 CST 2019 Finn Thain <fthain@telegraphics.com.au> char/nvram: Adopt arch_nvram_ops
NVRAMs on different platforms and architectures have different attributes
and access methods. E.g. some platforms have byte-at-a-time accessor
functions while others have byte-range accessor functions. Some have
checksum functionality while others do not. By calling ops struct methods
via the common wrapper functions, the nvram module and other drivers can
make use of the available NVRAM functionality in a portable way.
Signed-off-by: Finn Thain <fthain@telegraphics.com.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| /openbmc/linux/drivers/char/ |
| H A D | nvram.c | diff d5bbb5021ce8d9ff561c7469f5b4589ccb3bc4a6 Mon Jan 14 22:18:56 CST 2019 Finn Thain <fthain@telegraphics.com.au> char/nvram: Adopt arch_nvram_ops
NVRAMs on different platforms and architectures have different attributes
and access methods. E.g. some platforms have byte-at-a-time accessor
functions while others have byte-range accessor functions. Some have
checksum functionality while others do not. By calling ops struct methods
via the common wrapper functions, the nvram module and other drivers can
make use of the available NVRAM functionality in a portable way.
Signed-off-by: Finn Thain <fthain@telegraphics.com.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|