Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 4dd2b32f authored by Greg Kroah-Hartman's avatar Greg Kroah-Hartman
Browse files

staging: memrar: remove driver from tree



It's no longer needed at all.

Cc: Ossama Othman <ossama.othman@intel.com>
Cc: Eugene Epshteyn <eugene.epshteyn@intel.com>
Cc: Alan Cox <alan@linux.intel.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
parent 00838d4f
Loading
Loading
Loading
Loading
+0 −2
Original line number Diff line number Diff line
@@ -117,8 +117,6 @@ source "drivers/staging/hv/Kconfig"

source "drivers/staging/vme/Kconfig"

source "drivers/staging/memrar/Kconfig"

source "drivers/staging/sep/Kconfig"

source "drivers/staging/iio/Kconfig"
+0 −1
Original line number Diff line number Diff line
@@ -40,7 +40,6 @@ obj-$(CONFIG_VT6655) += vt6655/
obj-$(CONFIG_VT6656)		+= vt6656/
obj-$(CONFIG_HYPERV)		+= hv/
obj-$(CONFIG_VME_BUS)		+= vme/
obj-$(CONFIG_MRST_RAR_HANDLER)	+= memrar/
obj-$(CONFIG_DX_SEP)            += sep/
obj-$(CONFIG_IIO)		+= iio/
obj-$(CONFIG_CS5535_GPIO)	+= cs5535_gpio/

drivers/staging/memrar/Kconfig

deleted100644 → 0
+0 −15
Original line number Diff line number Diff line
config MRST_RAR_HANDLER
	tristate "RAR handler driver for Intel Moorestown platform"
	depends on RAR_REGISTER
	---help---
	  This driver provides a memory management interface to
	  restricted access regions (RAR) available on the Intel
	  Moorestown platform.

	  Once locked down, restricted access regions are only
	  accessible by specific hardware on the platform.  The x86
	  CPU is typically not one of those platforms.  As such this
	  driver does not access RAR, and only provides a buffer
	  allocation/bookkeeping mechanism.

	  If unsure, say N.

drivers/staging/memrar/Makefile

deleted100644 → 0
+0 −2
Original line number Diff line number Diff line
obj-$(CONFIG_MRST_RAR_HANDLER)	+= memrar.o
memrar-y			:= memrar_allocator.o memrar_handler.o

drivers/staging/memrar/TODO

deleted100644 → 0
+0 −43
Original line number Diff line number Diff line
RAR Handler (memrar) Driver TODO Items
======================================

Maintainer: Eugene Epshteyn <eugene.epshteyn@intel.com>

memrar.h
--------
1. This header exposes the driver's user space and kernel space
   interfaces.  It should be moved to <linux/rar/memrar.h>, or
   something along those lines, when this memrar driver is moved out
   of `staging'.
     a. It would be ideal if staging/rar_register/rar_register.h was
        moved to the same directory.

memrar_allocator.[ch]
---------------------
1. Address potential fragmentation issues with the memrar_allocator.

2. Hide struct memrar_allocator details/fields.  They need not be
   exposed to the user.
     a. Forward declare struct memrar_allocator.
     b. Move all three struct definitions to `memrar_allocator.c'
        source file.
     c. Add a memrar_allocator_largest_free_area() function, or
        something like that to get access to the value of the struct
        memrar_allocator "largest_free_area" field.  This allows the
        struct memrar_allocator fields to be completely hidden from
        the user.  The memrar_handler code really only needs this for
        statistic gathering on-demand.
     d. Do the same for the "capacity" field as the
        "largest_free_area" field.

3. Move memrar_allocator.* to kernel `lib' directory since it is HW
   neutral.
     a. Alternatively, use lib/genalloc.c instead.
     b. A kernel port of Doug Lea's malloc() implementation may also
        be an option.

memrar_handler.c
----------------
1. Split user space interface (ioctl code) from core/kernel code,
   e.g.:
     memrar_handler.c -> memrar_core.c, memrar_user.c
Loading