summaryrefslogtreecommitdiff
path: root/net/rxrpc/Kconfig
diff options
context:
space:
mode:
authorVladimir Zapolskiy <vladimir_zapolskiy@mentor.com>2015-09-21 20:52:46 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2015-10-18 04:51:47 (GMT)
commitb4c3fcb3c71f26ec18e06721cb3b6bcb314834f3 (patch)
tree839aed04d791708f44c36939d7bd3af8091c7f4f /net/rxrpc/Kconfig
parent50ceb98bebfaf7ae6de5fc46b277c595f4c2ce83 (diff)
downloadlinux-b4c3fcb3c71f26ec18e06721cb3b6bcb314834f3.tar.xz
misc: sram: extend usage of reserved partitions
This change adds functionality to operate on reserved SRAM partitions described in device tree file. Two partition properties are added, "pool" and "export", the first one allows to share a specific partition for usage by a kernel consumer in the same manner as it is done for the whole SRAM device, and "export" property provides access to some SRAM area from userspace over sysfs interface. Practically it is possible to specify both properties for an SRAM partition, however simultaneous access from a kernel consumer and from userspace is not serialized, but still the combination may be useful for debugging purpose. The change opens the following scenarios of SRAM usage: * updates in a particular SRAM area specified by offset and size are done by bootloader, then this information is utilized by the kernel, * a particular SRAM area is rw accessed from userspace, the stored data is persistent on soft reboots, * a device driver secures SRAM area for its purposes, * etc. Note, strictly speaking the added optional properties describe policy of SRAM usage, rather than hardware, but here the policy mostly resembles flash partitions in devicetree, which is undoubtedly a very popular option but it does not describe hardware. Signed-off-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/rxrpc/Kconfig')
0 files changed, 0 insertions, 0 deletions