linux-toradex.git/drivers/char/Kconfig, branch v3.14.45

raw: set range for MAX_RAW_DEVS

2014-02-07T16:29:46+00:00

The Kconfig symbol MAX_RAW_DEVS is meant to be between 1 and 65536. But
those boundaries are not enforced by its Kconfig entry.

Note that MAX_RAW_DEVS is used to set MAX_RAW_MINORS in
drivers/char/raw.c. If one would accidentally set MAX_RAW_DEVS to an
invalid value, that invalid value will actually end up being used in
raw_init().

So add an appropriate range to this Kconfig entry.

Signed-off-by: Paul Bolle 
Signed-off-by: Greg Kroah-Hartman

drivers/char/hpet.c: allow user controlled mmap for user processes

2013-11-13T03:09:11+00:00

The CONFIG_HPET_MMAP Kconfig option exposes the memory map of the HPET
registers to userspace.  The Kconfig help points out that in some cases
this can be a security risk as some systems may erroneously configure the
map such that additional data is exposed to userspace.

This is a problem for distributions -- some users want the MMAP
functionality but it comes with a significant security risk.  In an effort
to mitigate this risk, and due to the low number of users of the MMAP
functionality, I've introduced a kernel parameter, hpet_mmap_enable, that
is required in order to actually have the HPET MMAP exposed.

Signed-off-by: Prarit Bhargava 
Acked-by: Matt Wilson 
Signed-off-by: Clemens Ladisch 
Cc: Randy Dunlap 
Cc: Tomas Winkler 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

stallion: final cleanup

2013-06-03T21:31:39+00:00

Support for the Stallion multiport serial drivers was removed in v3.1.
Clean up their last references in the tree: mainly an outdated Kconfig
entry and unneeded documentation.

Signed-off-by: Paul Bolle 
Acked-by: Arnd Bergmann 
Signed-off-by: Greg Kroah-Hartman

tty: Added a CONFIG_TTY option to allow removal of TTY

2013-01-19T00:15:27+00:00

The option allows you to remove TTY and compile without errors. This
saves space on systems that won't support TTY interfaces anyway.
bloat-o-meter output is below.

The bulk of this patch consists of Kconfig changes adding "depends on
TTY" to various serial devices and similar drivers that require the TTY
layer.  Ideally, these dependencies would occur on a common intermediate
symbol such as SERIO, but most drivers "select SERIO" rather than
"depends on SERIO", and "select" does not respect dependencies.

bloat-o-meter output comparing our previous minimal to new minimal by
removing TTY.  The list is filtered to not show removed entries with awk
'$3 != "-"' as the list was very long.

add/remove: 0/226 grow/shrink: 2/14 up/down: 6/-35356 (-35350)
function                                     old     new   delta
chr_dev_init                                 166     170      +4
allow_signal                                  80      82      +2
static.__warned                              143     142      -1
disallow_signal                               63      62      -1
__set_special_pids                            95      94      -1
unregister_console                           126     121      -5
start_kernel                                 546     541      -5
register_console                             593     588      -5
copy_from_user                                45      40      -5
sys_setsid                                   128     120      -8
sys_vhangup                                   32      19     -13
do_exit                                     1543    1526     -17
bitmap_zero                                   60      40     -20
arch_local_irq_save                          137     117     -20
release_task                                 674     652     -22
static.spin_unlock_irqrestore                308     260     -48

Signed-off-by: Joe Millenbach 
Reviewed-by: Jamey Sharp 
Reviewed-by: Josh Triplett 
Signed-off-by: Greg Kroah-Hartman

char/misc: remove CONFIG_EXPERIMENTAL dependencies

2012-09-18T15:14:53+00:00

As discussed at the kernel summit this year, CONFIG_EXPERIMENTAL means
nothing, so let's get rid of it.

Cc: Kees Cook 
Cc: Arnd Bergmann 
Cc: Tomas Winkler 
Cc: Jiri Kosina 
Cc: Paul Bolle 
Cc: Andrew Morton 
Cc: Anatolij Gustschin 
Signed-off-by: Greg Kroah-Hartman

ramoops: Move to fs/pstore/ram.c

2012-05-16T15:06:37+00:00

Since ramoops was converted to pstore, it has nothing to do with character
devices nowadays. Instead, today it is just a RAM backend for pstore.

The patch just moves things around. There are a few changes were needed
because of the move:

1. Kconfig and Makefiles fixups, of course.

2. In pstore/ram.c we have to play a bit with MODULE_PARAM_PREFIX, this
   is needed to keep user experience the same as with ramoops driver
   (i.e. so that ramoops.foo kernel command line arguments would still
   work).

Signed-off-by: Anton Vorontsov 
Acked-by: Marco Stornelli 
Acked-by: Kees Cook 
Signed-off-by: Greg Kroah-Hartman

ramoops: use pstore interface

2012-05-16T15:06:33+00:00

Instead of using /dev/mem directly and forcing userspace to know (or
extract) where the platform has defined persistent memory, how many slots
it has, the sizes, etc, use the common pstore infrastructure to handle
Oops gathering and extraction.  This presents a much easier to use
filesystem-based view to the memory region.  This also means that any
other tools that are written to understand pstore will automatically be
able to process ramoops too.

Signed-off-by: Kees Cook 
Cc: Tony Luck 
Cc: Marco Stornelli 
Cc: Arnd Bergmann 
Cc: Randy Dunlap 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

tty: delete briq_panel.c driver

2012-03-08T18:45:55+00:00

This driver is broken, as reported by Jiri, and to quote Ben:
	Just remove the driver, I don't think anybody cares.
so I'm doing just that here.

Reported-by: Jiri Slaby 
Cc: Alan Cox 
Cc: Josh Boyer 
Cc: Benjamin Herrenschmidt 
Signed-off-by: Greg Kroah-Hartman

um: switch to use of drivers/Kconfig

2011-11-02T13:15:41+00:00

Signed-off-by: Al Viro 
Signed-off-by: Richard Weinberger

arch/tile: add hypervisor-based character driver for SPI flash ROM

2011-06-10T17:07:48+00:00

The first version of this patch proposed an arch/tile/drivers/ directory,
but the consensus was that this was probably a poor choice for a place to
group Tilera-specific drivers, and that in any case grouping by platform
was discouraged, and grouping by function was preferred.

This version of the patch addresses various issues raised in the
community, primarily the absence of sysfs integration.  The sysfs
integration now handles passing information on sector size, page size,
and total partition size to userspace as well.  In addition, we now
use a single "struct cdev" to manage all the partition minor devices,
and dynamically discover the correct number of partitions from the
hypervisor rather than using a module_param with a default value.

This driver has no particular "peer" drivers it can be grouped with.
It is sort of like an MTD driver for SPI ROM, but it doesn't group well
with the other MTD devices since it relies on hypervisor virtualization
to handle many of the irritating aspects of flash ROM management: sector
awareness, background read for sub-sector writes, bit examination to
determine whether a sector erase needs to be issued, etc.  It is in fact
more like an EEPROM driver, but the hypervisor virtualization does require
a "flush" command if you wish to commit a sector write prior to writing
to a different sector, and this is sufficiently different from generic
I2C/SPI EEPROMs that as a result it doesn't group well with them either.

The simple character device is already in use by a range of Tilera
SPI ROM management tools, as well as by customers.  In addition, using
the simple character device actually simplifies the userspace tools,
since they don't need to manage sector erase, background read, etc.
This both simplifies the code (since we can uniformly manage plain files
and the SPI ROM) as well as makes the user code portable to non-Linux
platforms that don't offer the same MTD ioctls.

Signed-off-by: Chris Metcalf 
Reviewed-by: Arnd Bergmann