On Mon, Aug 10, 2015 at 12:40:02AM +0300, Vladimir Zapolskiy wrote: > 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.
This scares me, why do we need to partition sram off in this manner? What uses it in this way? I need some other people to weigh in on this, and at the very least, I need some DT people to bless the changes there... thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
