linux-stable.git/drivers/char/Kconfig, branch v4.7

char: Drop bogus dependency of DEVPORT on !M68K

2016-05-01T21:20:04+00:00

According to full-history-linux commit d3794f4fa7c3edc3 ("[PATCH] M68k
update (part 25)"), port operations are allowed on m68k if CONFIG_ISA is
defined.

However, commit 153dcc54df826d2f ("[PATCH] mem driver: fix conditional
on isa i/o support") accidentally changed an "||" into an "&&",
disabling it completely on m68k. This logic was retained when
introducing the DEVPORT symbol in commit 4f911d64e04a44c4 ("Make
/dev/port conditional on config symbol").

Drop the bogus dependency on !M68K to fix this.

Fixes: 153dcc54df826d2f ("[PATCH] mem driver: fix conditional on isa i/o support")
Signed-off-by: Geert Uytterhoeven 
Tested-by: Al Stone 
Signed-off-by: Greg Kroah-Hartman

char/rtc: replace blacklist with whitelist

2016-05-01T21:07:28+00:00

Every new architecture has to add itself to the growing list of those
that do not support the legacy PC RTC driver.

This replaces the long list of architectures that don't support it
with a shorter list of those that do.

The list is taken from those architectures that have a non-empty
asm/mc146818rtc.h header file and were not explicitly blacklisted
or select RTC_LIB.

Alpha and Loongson64 can already choose between this driver and
an rtc-class based one. mn10300 is actually the only architecture
now that still requires this driver, and that should be fairly
easy to change to use rtc-cmos if we want to kill off rtc.ko
for good.

Signed-off-by: Arnd Bergmann 
Acked-by: Alexandre Belloni 
Acked-by: Geert Uytterhoeven 
Signed-off-by: Greg Kroah-Hartman

char: genrtc: replace blacklist with whitelist

2016-03-05T20:19:39+00:00

Every new architecture has to add itself to the growing list of those
that do not support the old "generic" RTC driver.

This replaces the long list of architectures that don't support it
with a shorter list of those that do.

The list is taken from those architectures that have a non-empty
asm/rtc.h header file and were not explicitly blacklisted.

Signed-off-by: Arnd Bergmann 
Acked-by: Alexandre Belloni 
Reviewed-by: Geert Uytterhoeven 
Signed-off-by: Greg Kroah-Hartman

drivers/char: Remove msm_smd_pkt driver

2015-05-24T19:24:35+00:00

This code is no longer used now that mach-msm has been removed.
Delete it.

Cc: David Brown 
Cc: Bryan Huntsman 
Cc: Daniel Walker 
Signed-off-by: Stephen Boyd 
Signed-off-by: Greg Kroah-Hartman

drivers: char: mem: Make /dev/mem an optional device

2015-01-12T13:04:11+00:00

Adds Kconfig option CONFIG_DEVMEM that allows the
/dev/mem device to be disabled.

Option defaults to /dev/mem enabled.

Signed-off-by: Rob Ward 
Acked-by: Arnd Bergmann 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

xillybus: Move out of staging

2014-09-24T06:44:16+00:00

This driver has been functional and stable throughout the year it has spent
in the staging area. It has been patched for minor bugs, coding style issues
and improvements during this period.

This is the second submission of this move-out, after making several style
improvements, as suggested by Dan Carpenter.

Signed-off-by: Eli Billauer 
Signed-off-by: Greg Kroah-Hartman

ttyprintk: Allow built as a module

2014-04-16T21:21:06+00:00

The driver is well written to be used as a module, just the exit call
is missing.

Reviewed-by: Jean Delvare 
Signed-off-by: Takashi Iwai 
Signed-off-by: Greg Kroah-Hartman

sonypi: Simplify dependencies

2014-04-06T16:58:13+00:00

X86 && !64BIT is better expressed as X86_32.

Signed-off-by: Jean Delvare 
Cc: Arnd Bergmann 
Cc: Greg Kroah-Hartman 
Cc: Mattia Dongili 
Signed-off-by: Matthew Garrett

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