Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Lukasz Luba <l.luba@partner.samsung.com>
To:     linux-kernel@vger.kernel.org, lukasz.luba@polnum.com
Cc:     b.zolnierkie@samsung.com, m.szyprowski@samsung.com,
        s.nawrocki@samsung.com, Lukasz Luba <l.luba@partner.samsung.com>
Subject: [RFC 0/2] SRAMFS a direct mapped SRAM pages into user space
Date:   Fri,  4 Oct 2019 15:38:53 +0200
Message-Id: <20191004133855.17474-1-l.luba@partner.samsung.com>
Content-Type: text/plain; charset="utf-8"
CMS-TYPE: 201P
References: <CGME20191004133905eucas1p1f002c9e76ceaef205b48e941707af726@eucas1p1.samsung.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi all,

This patch set tries to introduce a direct mapping mechanism of SRAM
memory regions directly into user space.
This is a draft of some reaserch work which I am going to continue.
Since it is my last day in the office I have publish it as a RFC.

Benefits of having SRAM memory in the user space:
- lower latency access
- lower power usage
- managable scratchpad which could be sharable between processes
- could be used toughether with dedicated instructions like dot product
  calculation

Regards,
Lukasz Luba

Lukasz Luba (2):
  DT: ARM: exynos: change SRAM device node
  dirvers & fs: add sram driver and sramfs

 arch/arm/boot/dts/exynos54xx.dtsi |  12 +-
 drivers/misc/Kconfig              |   7 +
 drivers/misc/Makefile             |   1 +
 drivers/misc/sram.h               |   1 +
 drivers/misc/sram_direct.c        | 863 ++++++++++++++++++++++++++++++
 include/uapi/linux/magic.h        |   1 +
 mm/memory.c                       |   5 +-
 7 files changed, 878 insertions(+), 12 deletions(-)
 create mode 100644 drivers/misc/sram_direct.c

-- 
2.17.1