2019-04-02 19:31:48 +09:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2008-09-25 06:46:44 +09:00
|
|
|
menuconfig STAGING
|
|
|
|
|
bool "Staging drivers"
|
|
|
|
|
---help---
|
|
|
|
|
This option allows you to select a number of drivers that are
|
|
|
|
|
not of the "normal" Linux kernel quality level. These drivers
|
2009-01-26 19:12:25 +09:00
|
|
|
are placed here in order to get a wider audience to make use of
|
2008-09-25 06:46:44 +09:00
|
|
|
them. Please note that these drivers are under heavy
|
|
|
|
|
development, may or may not work, and may contain userspace
|
|
|
|
|
interfaces that most likely will be changed in the near
|
|
|
|
|
future.
|
|
|
|
|
|
|
|
|
|
Using any of these drivers will taint your kernel which might
|
|
|
|
|
affect support options from both the community, and various
|
2009-01-26 19:12:25 +09:00
|
|
|
commercial support organizations.
|
2008-09-25 06:46:44 +09:00
|
|
|
|
|
|
|
|
If you wish to work on these drivers, to help improve them, or
|
|
|
|
|
to report problems you have with them, please see the
|
2019-04-26 04:49:04 +09:00
|
|
|
drivers/staging/<driver_name>/TODO file to see what needs to be
|
|
|
|
|
worked on, and who to contact.
|
2008-09-25 06:46:44 +09:00
|
|
|
|
|
|
|
|
If in doubt, say N here.
|
|
|
|
|
|
2008-11-08 14:12:17 +09:00
|
|
|
|
2008-11-28 06:01:28 +09:00
|
|
|
if STAGING
|
|
|
|
|
|
2008-10-03 03:29:28 +09:00
|
|
|
source "drivers/staging/wlan-ng/Kconfig"
|
|
|
|
|
|
2008-11-05 13:29:31 +09:00
|
|
|
source "drivers/staging/comedi/Kconfig"
|
|
|
|
|
|
2016-04-05 05:52:35 +09:00
|
|
|
source "drivers/staging/olpc_dcon/Kconfig"
|
|
|
|
|
|
2009-11-03 18:17:24 +09:00
|
|
|
source "drivers/staging/rtl8192u/Kconfig"
|
|
|
|
|
|
2009-08-05 07:57:55 +09:00
|
|
|
source "drivers/staging/rtl8192e/Kconfig"
|
2008-08-22 06:04:55 +09:00
|
|
|
|
2017-03-30 02:47:51 +09:00
|
|
|
source "drivers/staging/rtl8723bs/Kconfig"
|
|
|
|
|
|
2010-08-21 00:15:30 +09:00
|
|
|
source "drivers/staging/rtl8712/Kconfig"
|
|
|
|
|
|
2013-08-22 12:34:13 +09:00
|
|
|
source "drivers/staging/rtl8188eu/Kconfig"
|
2014-03-29 11:37:43 +09:00
|
|
|
|
2013-11-12 18:16:08 +09:00
|
|
|
source "drivers/staging/rts5208/Kconfig"
|
|
|
|
|
|
2009-05-06 09:35:21 +09:00
|
|
|
source "drivers/staging/octeon/Kconfig"
|
|
|
|
|
|
2013-06-02 03:42:58 +09:00
|
|
|
source "drivers/staging/octeon-usb/Kconfig"
|
|
|
|
|
|
2009-06-03 03:44:46 +09:00
|
|
|
source "drivers/staging/vt6655/Kconfig"
|
|
|
|
|
|
2009-06-13 20:39:00 +09:00
|
|
|
source "drivers/staging/vt6656/Kconfig"
|
2009-06-03 14:45:46 +09:00
|
|
|
|
2009-08-19 02:06:19 +09:00
|
|
|
source "drivers/staging/iio/Kconfig"
|
|
|
|
|
|
2015-03-03 19:51:06 +09:00
|
|
|
source "drivers/staging/sm750fb/Kconfig"
|
|
|
|
|
|
2014-06-06 19:44:17 +09:00
|
|
|
source "drivers/staging/emxx_udc/Kconfig"
|
2010-09-22 14:56:27 +09:00
|
|
|
|
2010-10-08 03:20:02 +09:00
|
|
|
source "drivers/staging/speakup/Kconfig"
|
|
|
|
|
|
2011-05-19 23:34:42 +09:00
|
|
|
source "drivers/staging/nvec/Kconfig"
|
|
|
|
|
|
2011-11-02 09:23:55 +09:00
|
|
|
source "drivers/staging/media/Kconfig"
|
2011-11-01 00:24:52 +09:00
|
|
|
|
2011-11-30 20:33:10 +09:00
|
|
|
source "drivers/staging/android/Kconfig"
|
|
|
|
|
|
2014-06-06 19:44:43 +09:00
|
|
|
source "drivers/staging/board/Kconfig"
|
|
|
|
|
|
2013-07-25 03:36:17 +09:00
|
|
|
source "drivers/staging/gdm724x/Kconfig"
|
|
|
|
|
|
2012-11-02 21:16:33 +09:00
|
|
|
source "drivers/staging/fwserial/Kconfig"
|
|
|
|
|
|
2013-01-23 23:13:52 +09:00
|
|
|
source "drivers/staging/goldfish/Kconfig"
|
|
|
|
|
|
2013-03-06 23:12:22 +09:00
|
|
|
source "drivers/staging/netlogic/Kconfig"
|
|
|
|
|
|
2014-01-21 16:47:06 +09:00
|
|
|
source "drivers/staging/gs_fpgaboot/Kconfig"
|
|
|
|
|
|
2014-03-04 22:58:05 +09:00
|
|
|
source "drivers/staging/unisys/Kconfig"
|
|
|
|
|
|
2014-10-03 01:13:35 +09:00
|
|
|
source "drivers/staging/clocking-wizard/Kconfig"
|
|
|
|
|
|
2014-12-31 18:11:09 +09:00
|
|
|
source "drivers/staging/fbtft/Kconfig"
|
|
|
|
|
|
2017-04-28 18:50:28 +09:00
|
|
|
source "drivers/staging/fsl-dpaa2/Kconfig"
|
|
|
|
|
|
2015-05-11 14:30:56 +09:00
|
|
|
source "drivers/staging/wilc1000/Kconfig"
|
|
|
|
|
|
Staging: most: add MOST driver's core module
This patch adds the core module of the MOST driver to the kernel's driver
staging area. This module is part of the MOST driver and handles the
configuration interface in sysfs, the buffer management and the data
routing.
MOST defines the protocol, hardware and software layers necessary to allow
for the efficient and low-cost transport of control, real-time and packet
data using a single medium (physical layer). Media currently in use are
fiber optics, unshielded twisted pair cables (UTP) and coax cables. MOST
also supports various speed grades up to 150 Mbps.
For more information on MOST, visit the MOST Cooperation website:
www.mostcooperation.com.
Cars continue to evolve into sophisticated consumer electronics platforms,
increasing the demand for reliable and simple solutions to support audio,
video and data communications. MOST can be used to connect multiple
consumer devices via optical or electrical physical layers directly to one
another or in a network configuration. As a synchronous network, MOST
provides excellent Quality of Service and seamless connectivity for
audio/video streaming. Therefore, the driver perfectly fits to the mission
of Automotive Grade Linux to create open source software solutions for
automotive applications.
The driver consists basically of three layers. The hardware layer, the
core layer and the application layer. The core layer consists of the core
module only. This module handles the communication flow through all three
layers, the configuration of the driver, the configuration interface
representation in sysfs, and the buffer management.
For each of the other two layers a selection of modules is provided. These
modules can arbitrarily be combined to meet the needs of the desired
system architecture. A module of the hardware layer is referred to as an
HDM (hardware dependent module). Each module of this layer handles exactly
one of the peripheral interfaces of a network interface controller (e.g.
USB, MediaLB, I2C). A module of the application layer is referred to as an
AIM (application interfacing module). The modules of this layer give access
to MOST via one the following ways: character devices, ALSA, Networking or
V4L2.
To physically access MOST, an Intelligent Network Interface Controller
(INIC) is needed. For more information on available controllers visit:
www.microchip.com
Signed-off-by: Christian Gromm <christian.gromm@microchip.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2015-07-24 23:11:48 +09:00
|
|
|
source "drivers/staging/most/Kconfig"
|
|
|
|
|
|
2016-05-31 19:56:13 +09:00
|
|
|
source "drivers/staging/ks7010/Kconfig"
|
|
|
|
|
|
2016-09-19 22:46:40 +09:00
|
|
|
source "drivers/staging/greybus/Kconfig"
|
|
|
|
|
|
staging: add bcm2708 vchiq driver
Signed-off-by: popcornmix <popcornmix@gmail.com>
vchiq: create_pagelist copes with vmalloc memory
Signed-off-by: Daniel Stone <daniels@collabora.com>
vchiq: fix the shim message release
Signed-off-by: Daniel Stone <daniels@collabora.com>
vchiq: export additional symbols
Signed-off-by: Daniel Stone <daniels@collabora.com>
VCHIQ: Make service closure fully synchronous (drv)
This is one half of a two-part patch, the other half of which is to
the vchiq_lib user library. With these patches, calls to
vchiq_close_service and vchiq_remove_service won't return until any
associated callbacks have been delivered to the callback thread.
VCHIQ: Add per-service tracing
The new service option VCHIQ_SERVICE_OPTION_TRACE is a boolean that
toggles tracing for the specified service.
This commit also introduces vchi_service_set_option and the associated
option VCHI_SERVICE_OPTION_TRACE.
vchiq: Make the synchronous-CLOSE logic more tolerant
vchiq: Move logging control into debugfs
vchiq: Take care of a corner case tickled by VCSM
Closing a connection that isn't fully open requires care, since one
side does not know the other side's port number. Code was present to
handle the case where a CLOSE is sent immediately after an OPEN, i.e.
before the OPENACK has been received, but this was incorrectly being
used when an OPEN from a client using port 0 was rejected.
(In the observed failure, the host was attempting to use the VCSM
service, which isn't present in the 'cutdown' firmware. The failure
was intermittent because sometimes the keepalive service would
grab port 0.)
This case can be distinguished because the client's remoteport will
still be VCHIQ_PORT_FREE, and the srvstate will be OPENING. Either
condition is sufficient to differentiate it from the special case
described above.
vchiq: Avoid high load when blocked and unkillable
vchiq: Include SIGSTOP and SIGCONT in list of signals not-masked by vchiq to allow gdb to work
vchiq_arm: Complete support for SYNCHRONOUS mode
vchiq: Remove inline from suspend/resume
vchiq: Allocation does not need to be atomic
vchiq: Fix wrong condition check
The log level is checked from within the log call. Remove the check in the call.
Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
BCM270x: Add vchiq device to platform file and Device Tree
Prepare to turn the vchiq module into a driver.
Signed-off-by: Noralf Trønnes <noralf@tronnes.org>
bcm2708: vchiq: Add Device Tree support
Turn vchiq into a driver and stop hardcoding resources.
Use devm_* functions in probe path to simplify cleanup.
A global variable is used to hold the register address. This is done
to keep this patch as small as possible.
Also make available on ARCH_BCM2835.
Based on work by Lubomir Rintel.
Signed-off-by: Noralf Trønnes <noralf@tronnes.org>
vchiq: Change logging level for inbound data
vchiq_arm: Two cacheing fixes
1) Make fragment size vary with cache line size
Without this patch, non-cache-line-aligned transfers may corrupt
(or be corrupted by) adjacent data structures.
Both ARM and VC need to be updated to enable this feature. This is
ensured by having the loader apply a new DT parameter -
cache-line-size. The existence of this parameter guarantees that the
kernel is capable, and the parameter will only be modified from the
safe default if the loader is capable.
2) Flush/invalidate vmalloc'd memory, and invalidate after reads
vchiq: fix NULL pointer dereference when closing driver
The following code run as root will cause a null pointer dereference oops:
int fd = open("/dev/vc-cma", O_RDONLY);
if (fd < 0)
err(1, "open failed");
(void)close(fd);
[ 1704.877721] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[ 1704.877725] pgd = b899c000
[ 1704.877736] [00000000] *pgd=37fab831, *pte=00000000, *ppte=00000000
[ 1704.877748] Internal error: Oops: 817 [#1] PREEMPT SMP ARM
[ 1704.877765] Modules linked in: evdev i2c_bcm2708 uio_pdrv_genirq uio
[ 1704.877774] CPU: 2 PID: 3656 Comm: stress-ng-fstat Not tainted 3.19.1-12-generic-bcm2709 #12-Ubuntu
[ 1704.877777] Hardware name: BCM2709
[ 1704.877783] task: b8ab9b00 ti: b7e68000 task.ti: b7e68000
[ 1704.877798] PC is at __down_interruptible+0x50/0xec
[ 1704.877806] LR is at down_interruptible+0x5c/0x68
[ 1704.877813] pc : [<80630ee8>] lr : [<800704b0>] psr: 60080093
sp : b7e69e50 ip : b7e69e88 fp : b7e69e84
[ 1704.877817] r10: b88123c8 r9 : 00000010 r8 : 00000001
[ 1704.877822] r7 : b8ab9b00 r6 : 7fffffff r5 : 80a1cc34 r4 : 80a1cc34
[ 1704.877826] r3 : b7e69e50 r2 : 00000000 r1 : 00000000 r0 : 80a1cc34
[ 1704.877833] Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
[ 1704.877838] Control: 10c5387d Table: 3899c06a DAC: 00000015
[ 1704.877843] Process do-oops (pid: 3656, stack limit = 0xb7e68238)
[ 1704.877848] Stack: (0xb7e69e50 to 0xb7e6a000)
[ 1704.877856] 9e40: 80a1cc3c 00000000 00000010 b88123c8
[ 1704.877865] 9e60: b7e69e84 80a1cc34 fff9fee9 ffffffff b7e68000 00000009 b7e69ea4 b7e69e88
[ 1704.877874] 9e80: 800704b0 80630ea4 fff9fee9 60080013 80a1cc28 fff9fee9 b7e69edc b7e69ea8
[ 1704.877884] 9ea0: 8040f558 80070460 fff9fee9 ffffffff 00000000 00000000 00000009 80a1cb7c
[ 1704.877893] 9ec0: 00000000 80a1cb7c 00000000 00000010 b7e69ef4 b7e69ee0 803e1ba4 8040f514
[ 1704.877902] 9ee0: 00000e48 80a1cb7c b7e69f14 b7e69ef8 803e1c9c 803e1b74 b88123c0 b92acb18
[ 1704.877911] 9f00: b8812790 b8d815d8 b7e69f24 b7e69f18 803e2250 803e1bc8 b7e69f5c b7e69f28
[ 1704.877921] 9f20: 80167bac 803e222c 00000000 00000000 b7e69f54 b8ab9ffc 00000000 8098c794
[ 1704.877930] 9f40: b8ab9b00 8000efc4 b7e68000 00000000 b7e69f6c b7e69f60 80167d6c 80167b28
[ 1704.877939] 9f60: b7e69f8c b7e69f70 80047d38 80167d60 b7e68000 b7e68010 8000efc4 b7e69fb0
[ 1704.877949] 9f80: b7e69fac b7e69f90 80012820 80047c84 01155490 011549a8 00000001 00000006
[ 1704.877957] 9fa0: 00000000 b7e69fb0 8000ee5c 80012790 00000000 353d8c0f 7efc4308 00000000
[ 1704.877966] 9fc0: 01155490 011549a8 00000001 00000006 00000000 00000000 76cf3ba0 00000003
[ 1704.877975] 9fe0: 00000000 7efc42e4 0002272f 76e2ed66 60080030 00000003 00000000 00000000
[ 1704.877998] [<80630ee8>] (__down_interruptible) from [<800704b0>] (down_interruptible+0x5c/0x68)
[ 1704.878015] [<800704b0>] (down_interruptible) from [<8040f558>] (vchiu_queue_push+0x50/0xd8)
[ 1704.878032] [<8040f558>] (vchiu_queue_push) from [<803e1ba4>] (send_worker_msg+0x3c/0x54)
[ 1704.878045] [<803e1ba4>] (send_worker_msg) from [<803e1c9c>] (vc_cma_set_reserve+0xe0/0x1c4)
[ 1704.878057] [<803e1c9c>] (vc_cma_set_reserve) from [<803e2250>] (vc_cma_release+0x30/0x38)
[ 1704.878069] [<803e2250>] (vc_cma_release) from [<80167bac>] (__fput+0x90/0x1e0)
[ 1704.878082] [<80167bac>] (__fput) from [<80167d6c>] (____fput+0x18/0x1c)
[ 1704.878094] [<80167d6c>] (____fput) from [<80047d38>] (task_work_run+0xc0/0xf8)
[ 1704.878109] [<80047d38>] (task_work_run) from [<80012820>] (do_work_pending+0x9c/0xc4)
[ 1704.878123] [<80012820>] (do_work_pending) from [<8000ee5c>] (work_pending+0xc/0x20)
[ 1704.878133] Code: e50b1034 e3a01000 e50b2030 e580300c (e5823000)
..the fix is to ensure that we have actually initialized the queue before we attempt
to push any items onto it. This occurs if we do an open() followed by a close() without
any activity in between.
Signed-off-by: Colin Ian King <colin.king@canonical.com>
vchiq_arm: Sort out the vmalloc case
See: https://github.com/raspberrypi/linux/issues/1055
vchiq: hack: Add include depecated dma include file
[gregkh] added dependancy on CONFIG_BROKEN to make things sane for now.
Cc: Eric Anholt <eric@anholt.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-07-03 07:42:01 +09:00
|
|
|
source "drivers/staging/vc04_services/Kconfig"
|
|
|
|
|
|
2017-07-16 19:52:06 +09:00
|
|
|
source "drivers/staging/pi433/Kconfig"
|
|
|
|
|
|
2018-08-03 17:26:54 +09:00
|
|
|
source "drivers/staging/mt7621-pci/Kconfig"
|
2018-03-15 05:22:35 +09:00
|
|
|
|
2019-01-04 16:08:21 +09:00
|
|
|
source "drivers/staging/mt7621-pci-phy/Kconfig"
|
|
|
|
|
|
2018-03-15 05:22:35 +09:00
|
|
|
source "drivers/staging/mt7621-pinctrl/Kconfig"
|
2018-03-15 05:22:35 +09:00
|
|
|
|
2018-03-15 05:22:35 +09:00
|
|
|
source "drivers/staging/mt7621-dma/Kconfig"
|
|
|
|
|
|
2019-01-11 09:43:36 +09:00
|
|
|
source "drivers/staging/ralink-gdma/Kconfig"
|
|
|
|
|
|
2018-03-15 05:22:36 +09:00
|
|
|
source "drivers/staging/mt7621-dts/Kconfig"
|
|
|
|
|
|
drivers/staging: Gasket driver framework + Apex driver
The Gasket (Google ASIC Software, Kernel Extensions, and Tools) kernel
framework is a generic, flexible system that supports thin kernel
drivers. Gasket kernel drivers are expected to handle opening and
closing devices, mmap'ing BAR space as requested, a small selection of
ioctls, and handling page table translation (covered below). Any other
functions should be handled by userspace code.
The Gasket common module is not enough to run a device. In order to
customize the Gasket code for a given piece of hardware, a device
specific module must be created. At a minimum, this module must define a
struct gasket_driver_desc containing the device-specific data for use by
the framework; in addition, the module must declare an __init function
that calls gasket_register_device with the module's gasket_driver_desc
struct. Finally, the driver must define an exit function that calls
gasket_unregister_device with the module's gasket_driver_desc struct.
One of the core assumptions of the Gasket framework is that precisely
one process is allowed to have an open write handle to the device node
at any given time. (That process may, once it has one write handle, open
any number of additional write handles.) This is accomplished by
tracking open and close data for each driver instance.
Signed-off-by: Rob Springer <rspringer@google.com>
Signed-off-by: John Joseph <jnjoseph@google.com>
Signed-off-by: Simon Que <sque@chromium.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-06-30 11:49:38 +09:00
|
|
|
source "drivers/staging/gasket/Kconfig"
|
|
|
|
|
|
2018-07-23 10:27:37 +09:00
|
|
|
source "drivers/staging/axis-fifo/Kconfig"
|
|
|
|
|
|
2019-04-17 00:56:12 +09:00
|
|
|
source "drivers/staging/fieldbus/Kconfig"
|
|
|
|
|
|
2019-04-20 03:42:05 +09:00
|
|
|
source "drivers/staging/kpc2000/Kconfig"
|
|
|
|
|
|
isdn: move capi drivers to staging
I tried to find any indication of whether the capi drivers are still in
use, and have not found anything from a long time ago.
With public ISDN networks almost completely shut down over the past 12
months, there is very little you can actually do with this hardware. The
main remaining use case would be to connect ISDN voice phones to an
in-house installation with Asterisk or LCR, but anyone trying this in
turn seems to be using either the mISDN driver stack, or out-of-tree
drivers from the hardware vendors.
I may of course have missed something, so I would suggest moving these
three drivers (avm, hysdn, gigaset) into drivers/staging/ just in case
someone still uses them.
If nobody complains, we can remove them entirely in six months, or
otherwise move the core code and any drivers that are still needed back
into drivers/isdn.
As Paul Bolle notes, he is still testing the gigaset driver as long as
he can, but the Dutch ISDN network will be shut down in September 2019,
which puts an end to that.
Marcel Holtmann still maintains the Bluetooth CMTP profile and wants to
keep that alive, so the actual CAPI subsystem code remains in place for
now, after all other drivers are gone, CMTP and CAPI can be merged into
a single driver directory.
Cc: Marcel Holtmann <marcel@holtmann.org>
Cc: Paul Bolle <pebolle@tiscali.nl>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2019-04-21 05:28:45 +09:00
|
|
|
source "drivers/staging/isdn/Kconfig"
|
|
|
|
|
|
2019-08-06 19:15:09 +09:00
|
|
|
source "drivers/staging/wusbcore/Kconfig"
|
|
|
|
|
source "drivers/staging/uwb/Kconfig"
|
|
|
|
|
|
2019-08-29 01:08:17 +09:00
|
|
|
source "drivers/staging/exfat/Kconfig"
|
|
|
|
|
|
2019-07-23 15:14:13 +09:00
|
|
|
source "drivers/staging/qlge/Kconfig"
|
|
|
|
|
|
2017-05-19 17:35:21 +09:00
|
|
|
source "drivers/staging/fsl_qbman/Kconfig"
|
2017-11-01 14:41:30 +09:00
|
|
|
source "drivers/staging/fsl_ppfe/Kconfig"
|
2017-05-19 17:35:21 +09:00
|
|
|
|
2008-11-28 06:01:28 +09:00
|
|
|
endif # STAGING
|