2005-04-17 06:20:36 +08:00
|
|
|
menu "Generic Driver Options"
|
|
|
|
|
|
2014-04-11 05:09:31 +08:00
|
|
|
config UEVENT_HELPER
|
|
|
|
|
bool "Support for uevent helper"
|
|
|
|
|
default y
|
2007-08-15 21:38:28 +08:00
|
|
|
help
|
2014-04-11 05:09:31 +08:00
|
|
|
The uevent helper program is forked by the kernel for
|
2007-08-15 21:38:28 +08:00
|
|
|
every uevent.
|
2010-01-15 05:49:39 +08:00
|
|
|
Before the switch to the netlink-based uevent source, this was
|
|
|
|
|
used to hook hotplug scripts into kernel device events. It
|
|
|
|
|
usually pointed to a shell script at /sbin/hotplug.
|
|
|
|
|
This should not be used today, because usual systems create
|
|
|
|
|
many events at bootup or device discovery in a very short time
|
|
|
|
|
frame. One forked process per event can create so many processes
|
|
|
|
|
that it creates a high system load, or on smaller systems
|
|
|
|
|
it is known to create out-of-memory situations during bootup.
|
2007-08-15 21:38:28 +08:00
|
|
|
|
2014-04-11 05:09:31 +08:00
|
|
|
config UEVENT_HELPER_PATH
|
|
|
|
|
string "path to uevent helper"
|
|
|
|
|
depends on UEVENT_HELPER
|
|
|
|
|
default ""
|
|
|
|
|
help
|
|
|
|
|
To disable user space helper program execution at by default
|
|
|
|
|
specify an empty string here. This setting can still be altered
|
2011-06-20 04:30:16 +08:00
|
|
|
via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper
|
|
|
|
|
later at runtime.
|
|
|
|
|
|
Driver Core: devtmpfs - kernel-maintained tmpfs-based /dev
Devtmpfs lets the kernel create a tmpfs instance called devtmpfs
very early at kernel initialization, before any driver-core device
is registered. Every device with a major/minor will provide a
device node in devtmpfs.
Devtmpfs can be changed and altered by userspace at any time,
and in any way needed - just like today's udev-mounted tmpfs.
Unmodified udev versions will run just fine on top of it, and will
recognize an already existing kernel-created device node and use it.
The default node permissions are root:root 0600. Proper permissions
and user/group ownership, meaningful symlinks, all other policy still
needs to be applied by userspace.
If a node is created by devtmps, devtmpfs will remove the device node
when the device goes away. If the device node was created by
userspace, or the devtmpfs created node was replaced by userspace, it
will no longer be removed by devtmpfs.
If it is requested to auto-mount it, it makes init=/bin/sh work
without any further userspace support. /dev will be fully populated
and dynamic, and always reflect the current device state of the kernel.
With the commonly used dynamic device numbers, it solves the problem
where static devices nodes may point to the wrong devices.
It is intended to make the initial bootup logic simpler and more robust,
by de-coupling the creation of the inital environment, to reliably run
userspace processes, from a complex userspace bootstrap logic to provide
a working /dev.
Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Jan Blunck <jblunck@suse.de>
Tested-By: Harald Hoyer <harald@redhat.com>
Tested-By: Scott James Remnant <scott@ubuntu.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2009-04-30 21:23:42 +08:00
|
|
|
config DEVTMPFS
|
2010-01-15 05:47:57 +08:00
|
|
|
bool "Maintain a devtmpfs filesystem to mount at /dev"
|
Driver Core: devtmpfs - kernel-maintained tmpfs-based /dev
Devtmpfs lets the kernel create a tmpfs instance called devtmpfs
very early at kernel initialization, before any driver-core device
is registered. Every device with a major/minor will provide a
device node in devtmpfs.
Devtmpfs can be changed and altered by userspace at any time,
and in any way needed - just like today's udev-mounted tmpfs.
Unmodified udev versions will run just fine on top of it, and will
recognize an already existing kernel-created device node and use it.
The default node permissions are root:root 0600. Proper permissions
and user/group ownership, meaningful symlinks, all other policy still
needs to be applied by userspace.
If a node is created by devtmps, devtmpfs will remove the device node
when the device goes away. If the device node was created by
userspace, or the devtmpfs created node was replaced by userspace, it
will no longer be removed by devtmpfs.
If it is requested to auto-mount it, it makes init=/bin/sh work
without any further userspace support. /dev will be fully populated
and dynamic, and always reflect the current device state of the kernel.
With the commonly used dynamic device numbers, it solves the problem
where static devices nodes may point to the wrong devices.
It is intended to make the initial bootup logic simpler and more robust,
by de-coupling the creation of the inital environment, to reliably run
userspace processes, from a complex userspace bootstrap logic to provide
a working /dev.
Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Jan Blunck <jblunck@suse.de>
Tested-By: Harald Hoyer <harald@redhat.com>
Tested-By: Scott James Remnant <scott@ubuntu.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2009-04-30 21:23:42 +08:00
|
|
|
help
|
2010-03-17 04:55:21 +08:00
|
|
|
This creates a tmpfs/ramfs filesystem instance early at bootup.
|
2010-01-15 05:47:57 +08:00
|
|
|
In this filesystem, the kernel driver core maintains device
|
|
|
|
|
nodes with their default names and permissions for all
|
|
|
|
|
registered devices with an assigned major/minor number.
|
|
|
|
|
Userspace can modify the filesystem content as needed, add
|
|
|
|
|
symlinks, and apply needed permissions.
|
|
|
|
|
It provides a fully functional /dev directory, where usually
|
|
|
|
|
udev runs on top, managing permissions and adding meaningful
|
|
|
|
|
symlinks.
|
|
|
|
|
In very limited environments, it may provide a sufficient
|
|
|
|
|
functional /dev without any further help. It also allows simple
|
|
|
|
|
rescue systems, and reliably handles dynamic major/minor numbers.
|
Driver Core: devtmpfs - kernel-maintained tmpfs-based /dev
Devtmpfs lets the kernel create a tmpfs instance called devtmpfs
very early at kernel initialization, before any driver-core device
is registered. Every device with a major/minor will provide a
device node in devtmpfs.
Devtmpfs can be changed and altered by userspace at any time,
and in any way needed - just like today's udev-mounted tmpfs.
Unmodified udev versions will run just fine on top of it, and will
recognize an already existing kernel-created device node and use it.
The default node permissions are root:root 0600. Proper permissions
and user/group ownership, meaningful symlinks, all other policy still
needs to be applied by userspace.
If a node is created by devtmps, devtmpfs will remove the device node
when the device goes away. If the device node was created by
userspace, or the devtmpfs created node was replaced by userspace, it
will no longer be removed by devtmpfs.
If it is requested to auto-mount it, it makes init=/bin/sh work
without any further userspace support. /dev will be fully populated
and dynamic, and always reflect the current device state of the kernel.
With the commonly used dynamic device numbers, it solves the problem
where static devices nodes may point to the wrong devices.
It is intended to make the initial bootup logic simpler and more robust,
by de-coupling the creation of the inital environment, to reliably run
userspace processes, from a complex userspace bootstrap logic to provide
a working /dev.
Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Jan Blunck <jblunck@suse.de>
Tested-By: Harald Hoyer <harald@redhat.com>
Tested-By: Scott James Remnant <scott@ubuntu.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2009-04-30 21:23:42 +08:00
|
|
|
|
2010-03-17 04:55:21 +08:00
|
|
|
Notice: if CONFIG_TMPFS isn't enabled, the simpler ramfs
|
|
|
|
|
file system will be used instead.
|
|
|
|
|
|
Driver Core: devtmpfs - kernel-maintained tmpfs-based /dev
Devtmpfs lets the kernel create a tmpfs instance called devtmpfs
very early at kernel initialization, before any driver-core device
is registered. Every device with a major/minor will provide a
device node in devtmpfs.
Devtmpfs can be changed and altered by userspace at any time,
and in any way needed - just like today's udev-mounted tmpfs.
Unmodified udev versions will run just fine on top of it, and will
recognize an already existing kernel-created device node and use it.
The default node permissions are root:root 0600. Proper permissions
and user/group ownership, meaningful symlinks, all other policy still
needs to be applied by userspace.
If a node is created by devtmps, devtmpfs will remove the device node
when the device goes away. If the device node was created by
userspace, or the devtmpfs created node was replaced by userspace, it
will no longer be removed by devtmpfs.
If it is requested to auto-mount it, it makes init=/bin/sh work
without any further userspace support. /dev will be fully populated
and dynamic, and always reflect the current device state of the kernel.
With the commonly used dynamic device numbers, it solves the problem
where static devices nodes may point to the wrong devices.
It is intended to make the initial bootup logic simpler and more robust,
by de-coupling the creation of the inital environment, to reliably run
userspace processes, from a complex userspace bootstrap logic to provide
a working /dev.
Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Jan Blunck <jblunck@suse.de>
Tested-By: Harald Hoyer <harald@redhat.com>
Tested-By: Scott James Remnant <scott@ubuntu.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2009-04-30 21:23:42 +08:00
|
|
|
config DEVTMPFS_MOUNT
|
2010-01-15 05:47:57 +08:00
|
|
|
bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
|
Driver Core: devtmpfs - kernel-maintained tmpfs-based /dev
Devtmpfs lets the kernel create a tmpfs instance called devtmpfs
very early at kernel initialization, before any driver-core device
is registered. Every device with a major/minor will provide a
device node in devtmpfs.
Devtmpfs can be changed and altered by userspace at any time,
and in any way needed - just like today's udev-mounted tmpfs.
Unmodified udev versions will run just fine on top of it, and will
recognize an already existing kernel-created device node and use it.
The default node permissions are root:root 0600. Proper permissions
and user/group ownership, meaningful symlinks, all other policy still
needs to be applied by userspace.
If a node is created by devtmps, devtmpfs will remove the device node
when the device goes away. If the device node was created by
userspace, or the devtmpfs created node was replaced by userspace, it
will no longer be removed by devtmpfs.
If it is requested to auto-mount it, it makes init=/bin/sh work
without any further userspace support. /dev will be fully populated
and dynamic, and always reflect the current device state of the kernel.
With the commonly used dynamic device numbers, it solves the problem
where static devices nodes may point to the wrong devices.
It is intended to make the initial bootup logic simpler and more robust,
by de-coupling the creation of the inital environment, to reliably run
userspace processes, from a complex userspace bootstrap logic to provide
a working /dev.
Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Jan Blunck <jblunck@suse.de>
Tested-By: Harald Hoyer <harald@redhat.com>
Tested-By: Scott James Remnant <scott@ubuntu.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2009-04-30 21:23:42 +08:00
|
|
|
depends on DEVTMPFS
|
|
|
|
|
help
|
2010-01-15 05:47:57 +08:00
|
|
|
This will instruct the kernel to automatically mount the
|
|
|
|
|
devtmpfs filesystem at /dev, directly after the kernel has
|
|
|
|
|
mounted the root filesystem. The behavior can be overridden
|
|
|
|
|
with the commandline parameter: devtmpfs.mount=0|1.
|
|
|
|
|
This option does not affect initramfs based booting, here
|
|
|
|
|
the devtmpfs filesystem always needs to be mounted manually
|
2013-12-02 21:59:39 +08:00
|
|
|
after the rootfs is mounted.
|
2010-01-15 05:47:57 +08:00
|
|
|
With this option enabled, it allows to bring up a system in
|
|
|
|
|
rescue mode with init=/bin/sh, even when the /dev directory
|
|
|
|
|
on the rootfs is completely empty.
|
Driver Core: devtmpfs - kernel-maintained tmpfs-based /dev
Devtmpfs lets the kernel create a tmpfs instance called devtmpfs
very early at kernel initialization, before any driver-core device
is registered. Every device with a major/minor will provide a
device node in devtmpfs.
Devtmpfs can be changed and altered by userspace at any time,
and in any way needed - just like today's udev-mounted tmpfs.
Unmodified udev versions will run just fine on top of it, and will
recognize an already existing kernel-created device node and use it.
The default node permissions are root:root 0600. Proper permissions
and user/group ownership, meaningful symlinks, all other policy still
needs to be applied by userspace.
If a node is created by devtmps, devtmpfs will remove the device node
when the device goes away. If the device node was created by
userspace, or the devtmpfs created node was replaced by userspace, it
will no longer be removed by devtmpfs.
If it is requested to auto-mount it, it makes init=/bin/sh work
without any further userspace support. /dev will be fully populated
and dynamic, and always reflect the current device state of the kernel.
With the commonly used dynamic device numbers, it solves the problem
where static devices nodes may point to the wrong devices.
It is intended to make the initial bootup logic simpler and more robust,
by de-coupling the creation of the inital environment, to reliably run
userspace processes, from a complex userspace bootstrap logic to provide
a working /dev.
Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Jan Blunck <jblunck@suse.de>
Tested-By: Harald Hoyer <harald@redhat.com>
Tested-By: Scott James Remnant <scott@ubuntu.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2009-04-30 21:23:42 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config STANDALONE
|
2012-10-24 04:01:50 +08:00
|
|
|
bool "Select only drivers that don't need compile-time external firmware"
|
2005-04-17 06:20:36 +08:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Select this option if you don't have magic firmware for drivers that
|
|
|
|
|
need it.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
|
|
|
|
config PREVENT_FIRMWARE_BUILD
|
|
|
|
|
bool "Prevent firmware from being built"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Say yes to avoid building firmware. Firmware is usually shipped
|
2011-06-13 02:17:30 +08:00
|
|
|
with the driver and only when updating the firmware should a
|
|
|
|
|
rebuild be made.
|
|
|
|
|
If unsure, say Y here.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config FW_LOADER
|
2011-01-21 06:44:16 +08:00
|
|
|
tristate "Userspace firmware loading support" if EXPERT
|
2008-06-11 00:04:08 +08:00
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
---help---
|
2011-06-13 02:17:30 +08:00
|
|
|
This option is provided for the case where none of the in-tree modules
|
|
|
|
|
require userspace firmware loading support, but a module built
|
|
|
|
|
out-of-tree does.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2008-06-25 20:56:07 +08:00
|
|
|
config FIRMWARE_IN_KERNEL
|
|
|
|
|
bool "Include in-kernel firmware blobs in kernel binary"
|
|
|
|
|
depends on FW_LOADER
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
The kernel source tree includes a number of firmware 'blobs'
|
2011-06-13 02:17:30 +08:00
|
|
|
that are used by various drivers. The recommended way to
|
2011-06-13 02:17:31 +08:00
|
|
|
use these is to run "make firmware_install", which, after
|
|
|
|
|
converting ihex files to binary, copies all of the needed
|
|
|
|
|
binary files in firmware/ to /lib/firmware/ on your system so
|
2008-06-25 20:56:07 +08:00
|
|
|
that they can be loaded by userspace helpers on request.
|
|
|
|
|
|
|
|
|
|
Enabling this option will build each required firmware blob
|
|
|
|
|
into the kernel directly, where request_firmware() will find
|
|
|
|
|
them without having to call out to userspace. This may be
|
2011-06-13 02:17:30 +08:00
|
|
|
useful if your root file system requires a device that uses
|
|
|
|
|
such firmware and do not wish to use an initrd.
|
2008-06-25 20:56:07 +08:00
|
|
|
|
|
|
|
|
This single option controls the inclusion of firmware for
|
2011-06-13 02:17:30 +08:00
|
|
|
every driver that uses request_firmware() and ships its
|
|
|
|
|
firmware in the kernel source tree, which avoids a
|
|
|
|
|
proliferation of 'Include firmware for xxx device' options.
|
2008-06-25 20:56:07 +08:00
|
|
|
|
|
|
|
|
Say 'N' and let firmware be loaded from userspace.
|
|
|
|
|
|
2008-05-23 20:58:12 +08:00
|
|
|
config EXTRA_FIRMWARE
|
|
|
|
|
string "External firmware blobs to build into the kernel binary"
|
|
|
|
|
depends on FW_LOADER
|
|
|
|
|
help
|
2011-06-13 02:17:30 +08:00
|
|
|
This option allows firmware to be built into the kernel for the case
|
|
|
|
|
where the user either cannot or doesn't want to provide it from
|
2008-05-23 20:58:12 +08:00
|
|
|
userspace at runtime (for example, when the firmware in question is
|
|
|
|
|
required for accessing the boot device, and the user doesn't want to
|
|
|
|
|
use an initrd).
|
|
|
|
|
|
2011-06-13 02:17:30 +08:00
|
|
|
This option is a string and takes the (space-separated) names of the
|
|
|
|
|
firmware files -- the same names that appear in MODULE_FIRMWARE()
|
2008-05-23 20:58:12 +08:00
|
|
|
and request_firmware() in the source. These files should exist under
|
|
|
|
|
the directory specified by the EXTRA_FIRMWARE_DIR option, which is
|
2011-06-13 02:17:30 +08:00
|
|
|
by default the firmware subdirectory of the kernel source tree.
|
2008-05-23 20:58:12 +08:00
|
|
|
|
2011-06-13 02:17:30 +08:00
|
|
|
For example, you might set CONFIG_EXTRA_FIRMWARE="usb8388.bin", copy
|
|
|
|
|
the usb8388.bin file into the firmware directory, and build the kernel.
|
|
|
|
|
Then any request_firmware("usb8388.bin") will be satisfied internally
|
|
|
|
|
without needing to call out to userspace.
|
2008-05-23 20:58:12 +08:00
|
|
|
|
|
|
|
|
WARNING: If you include additional firmware files into your binary
|
2011-06-13 02:17:30 +08:00
|
|
|
kernel image that are not available under the terms of the GPL,
|
2008-05-23 20:58:12 +08:00
|
|
|
then it may be a violation of the GPL to distribute the resulting
|
2011-06-13 02:17:30 +08:00
|
|
|
image since it combines both GPL and non-GPL work. You should
|
2008-05-23 20:58:12 +08:00
|
|
|
consult a lawyer of your own before distributing such an image.
|
|
|
|
|
|
|
|
|
|
config EXTRA_FIRMWARE_DIR
|
|
|
|
|
string "Firmware blobs root directory"
|
|
|
|
|
depends on EXTRA_FIRMWARE != ""
|
|
|
|
|
default "firmware"
|
|
|
|
|
help
|
|
|
|
|
This option controls the directory in which the kernel build system
|
|
|
|
|
looks for the firmware files listed in the EXTRA_FIRMWARE option.
|
2011-06-13 02:17:30 +08:00
|
|
|
The default is firmware/ in the kernel source tree, but by changing
|
|
|
|
|
this option you can point it elsewhere, such as /lib/firmware/ or
|
|
|
|
|
some other directory containing the firmware files.
|
2008-05-23 20:58:12 +08:00
|
|
|
|
2013-01-31 18:13:55 +08:00
|
|
|
config FW_LOADER_USER_HELPER
|
firmware loader: allow disabling of udev as firmware loader
[The patch was originally proposed by Tom Gundersen, and rewritten
afterwards by me; most of changelogs below borrowed from Tom's
original patch -- tiwai]
Currently (at least) the dell-rbu driver selects FW_LOADER_USER_HELPER,
which means that distros can't really stop loading firmware through
udev without breaking other users (though some have).
Ideally we would remove/disable the udev firmware helper in both the
kernel and in udev, but if we were to disable it in udev and not the
kernel, the result would be (seemingly) hung kernels as no one would
be around to cancel firmware requests.
This patch allows udev firmware loading to be disabled while still
allowing non-udev firmware loading, as done by the dell-rbu driver, to
continue working. This is achieved by only using the fallback
mechanism when the uevent is suppressed.
The patch renames the user-selectable Kconfig from FW_LOADER_USER_HELPER
to FW_LOADER_USER_HELPER_FALLBACK, and the former is reverse-selected
by the latter or the drivers that need userhelper like dell-rbu.
Also, the "default y" is removed together with this change, since it's
been deprecated in udev upstream, thus rather better to disable it
nowadays.
Tested with
FW_LOADER_USER_HELPER=n
LATTICE_ECP3_CONFIG=y
DELL_RBU=y
and udev without the firmware loading support, but I don't have the
hardware to test the lattice/dell drivers, so additional testing would
be appreciated.
Reviewed-by: Tom Gundersen <teg@jklm.no>
Cc: Ming Lei <ming.lei@canonical.com>
Cc: Abhay Salunke <Abhay_Salunke@dell.com>
Cc: Stefan Roese <sr@denx.de>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Kay Sievers <kay@vrfy.org>
Tested-by: Balaji Singh <B_B_Singh@DELL.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-06-04 23:48:15 +08:00
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config FW_LOADER_USER_HELPER_FALLBACK
|
2013-01-31 18:13:55 +08:00
|
|
|
bool "Fallback user-helper invocation for firmware loading"
|
|
|
|
|
depends on FW_LOADER
|
firmware loader: allow disabling of udev as firmware loader
[The patch was originally proposed by Tom Gundersen, and rewritten
afterwards by me; most of changelogs below borrowed from Tom's
original patch -- tiwai]
Currently (at least) the dell-rbu driver selects FW_LOADER_USER_HELPER,
which means that distros can't really stop loading firmware through
udev without breaking other users (though some have).
Ideally we would remove/disable the udev firmware helper in both the
kernel and in udev, but if we were to disable it in udev and not the
kernel, the result would be (seemingly) hung kernels as no one would
be around to cancel firmware requests.
This patch allows udev firmware loading to be disabled while still
allowing non-udev firmware loading, as done by the dell-rbu driver, to
continue working. This is achieved by only using the fallback
mechanism when the uevent is suppressed.
The patch renames the user-selectable Kconfig from FW_LOADER_USER_HELPER
to FW_LOADER_USER_HELPER_FALLBACK, and the former is reverse-selected
by the latter or the drivers that need userhelper like dell-rbu.
Also, the "default y" is removed together with this change, since it's
been deprecated in udev upstream, thus rather better to disable it
nowadays.
Tested with
FW_LOADER_USER_HELPER=n
LATTICE_ECP3_CONFIG=y
DELL_RBU=y
and udev without the firmware loading support, but I don't have the
hardware to test the lattice/dell drivers, so additional testing would
be appreciated.
Reviewed-by: Tom Gundersen <teg@jklm.no>
Cc: Ming Lei <ming.lei@canonical.com>
Cc: Abhay Salunke <Abhay_Salunke@dell.com>
Cc: Stefan Roese <sr@denx.de>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Kay Sievers <kay@vrfy.org>
Tested-by: Balaji Singh <B_B_Singh@DELL.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-06-04 23:48:15 +08:00
|
|
|
select FW_LOADER_USER_HELPER
|
2013-01-31 18:13:55 +08:00
|
|
|
help
|
|
|
|
|
This option enables / disables the invocation of user-helper
|
|
|
|
|
(e.g. udev) for loading firmware files as a fallback after the
|
|
|
|
|
direct file loading in kernel fails. The user-mode helper is
|
|
|
|
|
no longer required unless you have a special firmware file that
|
firmware loader: allow disabling of udev as firmware loader
[The patch was originally proposed by Tom Gundersen, and rewritten
afterwards by me; most of changelogs below borrowed from Tom's
original patch -- tiwai]
Currently (at least) the dell-rbu driver selects FW_LOADER_USER_HELPER,
which means that distros can't really stop loading firmware through
udev without breaking other users (though some have).
Ideally we would remove/disable the udev firmware helper in both the
kernel and in udev, but if we were to disable it in udev and not the
kernel, the result would be (seemingly) hung kernels as no one would
be around to cancel firmware requests.
This patch allows udev firmware loading to be disabled while still
allowing non-udev firmware loading, as done by the dell-rbu driver, to
continue working. This is achieved by only using the fallback
mechanism when the uevent is suppressed.
The patch renames the user-selectable Kconfig from FW_LOADER_USER_HELPER
to FW_LOADER_USER_HELPER_FALLBACK, and the former is reverse-selected
by the latter or the drivers that need userhelper like dell-rbu.
Also, the "default y" is removed together with this change, since it's
been deprecated in udev upstream, thus rather better to disable it
nowadays.
Tested with
FW_LOADER_USER_HELPER=n
LATTICE_ECP3_CONFIG=y
DELL_RBU=y
and udev without the firmware loading support, but I don't have the
hardware to test the lattice/dell drivers, so additional testing would
be appreciated.
Reviewed-by: Tom Gundersen <teg@jklm.no>
Cc: Ming Lei <ming.lei@canonical.com>
Cc: Abhay Salunke <Abhay_Salunke@dell.com>
Cc: Stefan Roese <sr@denx.de>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Kay Sievers <kay@vrfy.org>
Tested-by: Balaji Singh <B_B_Singh@DELL.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-06-04 23:48:15 +08:00
|
|
|
resides in a non-standard path. Moreover, the udev support has
|
|
|
|
|
been deprecated upstream.
|
|
|
|
|
|
|
|
|
|
If you are unsure about this, say N here.
|
2013-01-31 18:13:55 +08:00
|
|
|
|
device coredump: add new device coredump class
Many devices run firmware and/or complex hardware, and most of that
can have bugs. When it misbehaves, however, it is often much harder
to debug than software running on the host.
Introduce a "device coredump" mechanism to allow dumping internal
device/firmware state through a generalized mechanism. As devices
are different and information needed can vary accordingly, this
doesn't prescribe a file format - it just provides mechanism to
get data to be able to capture it in a generalized way (e.g. in
distributions.)
The dumped data will be readable in sysfs in the virtual device's
data file under /sys/class/devcoredump/devcd*/. Writing to it will
free the data and remove the device, as does a 5-minute timeout.
Note that generalized capturing of such data may result in privacy
issues, so users generally need to be involved. In order to allow
certain users/system integrators/... to disable the feature at all,
introduce a Kconfig option to override the drivers that would like
to have the feature.
For now, this provides two ways of dumping data:
1) with a vmalloc'ed area, that is then given to the subsystem
and freed after retrieval or timeout
2) with a generalized reader/free function method
We could/should add more options, e.g. a list of pages, since the
vmalloc area is very limited on some architectures.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-09-12 15:01:56 +08:00
|
|
|
config WANT_DEV_COREDUMP
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Drivers should "select" this option if they desire to use the
|
|
|
|
|
device coredump mechanism.
|
|
|
|
|
|
2014-10-30 17:00:35 +08:00
|
|
|
config ALLOW_DEV_COREDUMP
|
|
|
|
|
bool "Allow device coredump" if EXPERT
|
2014-10-16 23:49:49 +08:00
|
|
|
default y
|
device coredump: add new device coredump class
Many devices run firmware and/or complex hardware, and most of that
can have bugs. When it misbehaves, however, it is often much harder
to debug than software running on the host.
Introduce a "device coredump" mechanism to allow dumping internal
device/firmware state through a generalized mechanism. As devices
are different and information needed can vary accordingly, this
doesn't prescribe a file format - it just provides mechanism to
get data to be able to capture it in a generalized way (e.g. in
distributions.)
The dumped data will be readable in sysfs in the virtual device's
data file under /sys/class/devcoredump/devcd*/. Writing to it will
free the data and remove the device, as does a 5-minute timeout.
Note that generalized capturing of such data may result in privacy
issues, so users generally need to be involved. In order to allow
certain users/system integrators/... to disable the feature at all,
introduce a Kconfig option to override the drivers that would like
to have the feature.
For now, this provides two ways of dumping data:
1) with a vmalloc'ed area, that is then given to the subsystem
and freed after retrieval or timeout
2) with a generalized reader/free function method
We could/should add more options, e.g. a list of pages, since the
vmalloc area is very limited on some architectures.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-09-12 15:01:56 +08:00
|
|
|
help
|
2014-10-16 23:49:49 +08:00
|
|
|
This option controls if the device coredump mechanism is available or
|
|
|
|
|
not; if disabled, the mechanism will be omitted even if drivers that
|
|
|
|
|
can use it are enabled.
|
|
|
|
|
Say 'N' for more sensitive systems or systems that don't want
|
|
|
|
|
to ever access the information to not have the code, nor keep any
|
|
|
|
|
data.
|
device coredump: add new device coredump class
Many devices run firmware and/or complex hardware, and most of that
can have bugs. When it misbehaves, however, it is often much harder
to debug than software running on the host.
Introduce a "device coredump" mechanism to allow dumping internal
device/firmware state through a generalized mechanism. As devices
are different and information needed can vary accordingly, this
doesn't prescribe a file format - it just provides mechanism to
get data to be able to capture it in a generalized way (e.g. in
distributions.)
The dumped data will be readable in sysfs in the virtual device's
data file under /sys/class/devcoredump/devcd*/. Writing to it will
free the data and remove the device, as does a 5-minute timeout.
Note that generalized capturing of such data may result in privacy
issues, so users generally need to be involved. In order to allow
certain users/system integrators/... to disable the feature at all,
introduce a Kconfig option to override the drivers that would like
to have the feature.
For now, this provides two ways of dumping data:
1) with a vmalloc'ed area, that is then given to the subsystem
and freed after retrieval or timeout
2) with a generalized reader/free function method
We could/should add more options, e.g. a list of pages, since the
vmalloc area is very limited on some architectures.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-09-12 15:01:56 +08:00
|
|
|
|
2014-10-16 23:49:49 +08:00
|
|
|
If unsure, say Y.
|
device coredump: add new device coredump class
Many devices run firmware and/or complex hardware, and most of that
can have bugs. When it misbehaves, however, it is often much harder
to debug than software running on the host.
Introduce a "device coredump" mechanism to allow dumping internal
device/firmware state through a generalized mechanism. As devices
are different and information needed can vary accordingly, this
doesn't prescribe a file format - it just provides mechanism to
get data to be able to capture it in a generalized way (e.g. in
distributions.)
The dumped data will be readable in sysfs in the virtual device's
data file under /sys/class/devcoredump/devcd*/. Writing to it will
free the data and remove the device, as does a 5-minute timeout.
Note that generalized capturing of such data may result in privacy
issues, so users generally need to be involved. In order to allow
certain users/system integrators/... to disable the feature at all,
introduce a Kconfig option to override the drivers that would like
to have the feature.
For now, this provides two ways of dumping data:
1) with a vmalloc'ed area, that is then given to the subsystem
and freed after retrieval or timeout
2) with a generalized reader/free function method
We could/should add more options, e.g. a list of pages, since the
vmalloc area is very limited on some architectures.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-09-12 15:01:56 +08:00
|
|
|
|
|
|
|
|
config DEV_COREDUMP
|
|
|
|
|
bool
|
|
|
|
|
default y if WANT_DEV_COREDUMP
|
2014-10-30 17:00:35 +08:00
|
|
|
depends on ALLOW_DEV_COREDUMP
|
device coredump: add new device coredump class
Many devices run firmware and/or complex hardware, and most of that
can have bugs. When it misbehaves, however, it is often much harder
to debug than software running on the host.
Introduce a "device coredump" mechanism to allow dumping internal
device/firmware state through a generalized mechanism. As devices
are different and information needed can vary accordingly, this
doesn't prescribe a file format - it just provides mechanism to
get data to be able to capture it in a generalized way (e.g. in
distributions.)
The dumped data will be readable in sysfs in the virtual device's
data file under /sys/class/devcoredump/devcd*/. Writing to it will
free the data and remove the device, as does a 5-minute timeout.
Note that generalized capturing of such data may result in privacy
issues, so users generally need to be involved. In order to allow
certain users/system integrators/... to disable the feature at all,
introduce a Kconfig option to override the drivers that would like
to have the feature.
For now, this provides two ways of dumping data:
1) with a vmalloc'ed area, that is then given to the subsystem
and freed after retrieval or timeout
2) with a generalized reader/free function method
We could/should add more options, e.g. a list of pages, since the
vmalloc area is very limited on some architectures.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-09-12 15:01:56 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config DEBUG_DRIVER
|
|
|
|
|
bool "Driver Core verbose debug messages"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want the Driver core to produce a bunch of
|
|
|
|
|
debug messages to the system log. Select this if you are having a
|
|
|
|
|
problem with the driver core and want to see more of what is
|
|
|
|
|
going on.
|
|
|
|
|
|
|
|
|
|
If you are unsure about this, say N here.
|
|
|
|
|
|
devres: device resource management
Implement device resource management, in short, devres. A device
driver can allocate arbirary size of devres data which is associated
with a release function. On driver detach, release function is
invoked on the devres data, then, devres data is freed.
devreses are typed by associated release functions. Some devreses are
better represented by single instance of the type while others need
multiple instances sharing the same release function. Both usages are
supported.
devreses can be grouped using devres group such that a device driver
can easily release acquired resources halfway through initialization
or selectively release resources (e.g. resources for port 1 out of 4
ports).
This patch adds devres core including documentation and the following
managed interfaces.
* alloc/free : devm_kzalloc(), devm_kzfree()
* IO region : devm_request_region(), devm_release_region()
* IRQ : devm_request_irq(), devm_free_irq()
* DMA : dmam_alloc_coherent(), dmam_free_coherent(),
dmam_declare_coherent_memory(), dmam_pool_create(),
dmam_pool_destroy()
* PCI : pcim_enable_device(), pcim_pin_device(), pci_is_managed()
* iomap : devm_ioport_map(), devm_ioport_unmap(), devm_ioremap(),
devm_ioremap_nocache(), devm_iounmap(), pcim_iomap_table(),
pcim_iomap(), pcim_iounmap()
Signed-off-by: Tejun Heo <htejun@gmail.com>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-01-20 15:00:26 +08:00
|
|
|
config DEBUG_DEVRES
|
|
|
|
|
bool "Managed device resources verbose debug messages"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
This option enables kernel parameter devres.log. If set to
|
|
|
|
|
non-zero, devres debug messages are printed. Select this if
|
|
|
|
|
you are having a problem with devres or want to debug
|
|
|
|
|
resource management for a managed device. devres.log can be
|
|
|
|
|
switched on and off from sysfs node.
|
|
|
|
|
|
|
|
|
|
If you are unsure about this, Say N here.
|
|
|
|
|
|
2016-08-11 23:20:58 +08:00
|
|
|
config DEBUG_TEST_DRIVER_REMOVE
|
2016-10-08 00:09:30 +08:00
|
|
|
bool "Test driver remove calls during probe (UNSTABLE)"
|
2016-08-11 23:20:58 +08:00
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want the Driver core to test driver remove functions
|
|
|
|
|
by calling probe, remove, probe. This tests the remove path without
|
|
|
|
|
having to unbind the driver or unload the driver module.
|
|
|
|
|
|
2016-10-08 00:09:30 +08:00
|
|
|
This option is expected to find errors and may render your system
|
|
|
|
|
unusable. You should say N here unless you are explicitly looking to
|
|
|
|
|
test this functionality.
|
2016-08-11 23:20:58 +08:00
|
|
|
|
2016-09-29 23:13:14 +08:00
|
|
|
source "drivers/base/test/Kconfig"
|
|
|
|
|
|
2006-05-09 18:53:49 +08:00
|
|
|
config SYS_HYPERVISOR
|
|
|
|
|
bool
|
|
|
|
|
default n
|
2006-10-29 01:38:55 +08:00
|
|
|
|
2012-01-10 11:04:32 +08:00
|
|
|
config GENERIC_CPU_DEVICES
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
2014-02-08 20:34:09 +08:00
|
|
|
config GENERIC_CPU_AUTOPROBE
|
|
|
|
|
bool
|
|
|
|
|
|
2012-02-07 03:22:22 +08:00
|
|
|
config SOC_BUS
|
|
|
|
|
bool
|
2016-09-21 14:57:19 +08:00
|
|
|
select GLOB
|
2012-02-07 03:22:22 +08:00
|
|
|
|
2011-05-12 01:59:58 +08:00
|
|
|
source "drivers/base/regmap/Kconfig"
|
|
|
|
|
|
dma-buf: Introduce dma buffer sharing mechanism
This is the first step in defining a dma buffer sharing mechanism.
A new buffer object dma_buf is added, with operations and API to allow easy
sharing of this buffer object across devices.
The framework allows:
- creation of a buffer object, its association with a file pointer, and
associated allocator-defined operations on that buffer. This operation is
called the 'export' operation.
- different devices to 'attach' themselves to this exported buffer object, to
facilitate backing storage negotiation, using dma_buf_attach() API.
- the exported buffer object to be shared with the other entity by asking for
its 'file-descriptor (fd)', and sharing the fd across.
- a received fd to get the buffer object back, where it can be accessed using
the associated exporter-defined operations.
- the exporter and user to share the scatterlist associated with this buffer
object using map_dma_buf and unmap_dma_buf operations.
Atleast one 'attach()' call is required to be made prior to calling the
map_dma_buf() operation.
Couple of building blocks in map_dma_buf() are added to ease introduction
of sync'ing across exporter and users, and late allocation by the exporter.
For this first version, this framework will work with certain conditions:
- *ONLY* exporter will be allowed to mmap to userspace (outside of this
framework - mmap is not a buffer object operation),
- currently, *ONLY* users that do not need CPU access to the buffer are
allowed.
More details are there in the documentation patch.
This is based on design suggestions from many people at the mini-summits[1],
most notably from Arnd Bergmann <arnd@arndb.de>, Rob Clark <rob@ti.com> and
Daniel Vetter <daniel@ffwll.ch>.
The implementation is inspired from proof-of-concept patch-set from
Tomasz Stanislawski <t.stanislaws@samsung.com>, who demonstrated buffer sharing
between two v4l2 devices. [2]
[1]: https://wiki.linaro.org/OfficeofCTO/MemoryManagement
[2]: http://lwn.net/Articles/454389
Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
Signed-off-by: Sumit Semwal <sumit.semwal@ti.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Dave Airlie <airlied@redhat.com>
Reviewed-and-Tested-by: Rob Clark <rob.clark@linaro.org>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2011-12-26 17:23:15 +08:00
|
|
|
config DMA_SHARED_BUFFER
|
2012-01-13 17:05:14 +08:00
|
|
|
bool
|
dma-buf: Introduce dma buffer sharing mechanism
This is the first step in defining a dma buffer sharing mechanism.
A new buffer object dma_buf is added, with operations and API to allow easy
sharing of this buffer object across devices.
The framework allows:
- creation of a buffer object, its association with a file pointer, and
associated allocator-defined operations on that buffer. This operation is
called the 'export' operation.
- different devices to 'attach' themselves to this exported buffer object, to
facilitate backing storage negotiation, using dma_buf_attach() API.
- the exported buffer object to be shared with the other entity by asking for
its 'file-descriptor (fd)', and sharing the fd across.
- a received fd to get the buffer object back, where it can be accessed using
the associated exporter-defined operations.
- the exporter and user to share the scatterlist associated with this buffer
object using map_dma_buf and unmap_dma_buf operations.
Atleast one 'attach()' call is required to be made prior to calling the
map_dma_buf() operation.
Couple of building blocks in map_dma_buf() are added to ease introduction
of sync'ing across exporter and users, and late allocation by the exporter.
For this first version, this framework will work with certain conditions:
- *ONLY* exporter will be allowed to mmap to userspace (outside of this
framework - mmap is not a buffer object operation),
- currently, *ONLY* users that do not need CPU access to the buffer are
allowed.
More details are there in the documentation patch.
This is based on design suggestions from many people at the mini-summits[1],
most notably from Arnd Bergmann <arnd@arndb.de>, Rob Clark <rob@ti.com> and
Daniel Vetter <daniel@ffwll.ch>.
The implementation is inspired from proof-of-concept patch-set from
Tomasz Stanislawski <t.stanislaws@samsung.com>, who demonstrated buffer sharing
between two v4l2 devices. [2]
[1]: https://wiki.linaro.org/OfficeofCTO/MemoryManagement
[2]: http://lwn.net/Articles/454389
Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
Signed-off-by: Sumit Semwal <sumit.semwal@ti.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Dave Airlie <airlied@redhat.com>
Reviewed-and-Tested-by: Rob Clark <rob.clark@linaro.org>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2011-12-26 17:23:15 +08:00
|
|
|
default n
|
|
|
|
|
select ANON_INODES
|
|
|
|
|
help
|
|
|
|
|
This option enables the framework for buffer-sharing between
|
|
|
|
|
multiple drivers. A buffer is associated with a file using driver
|
|
|
|
|
APIs extension; the file's descriptor can then be passed on to other
|
|
|
|
|
driver.
|
|
|
|
|
|
2016-10-25 20:00:45 +08:00
|
|
|
config DMA_FENCE_TRACE
|
|
|
|
|
bool "Enable verbose DMA_FENCE_TRACE messages"
|
fence: dma-buf cross-device synchronization (v18)
A fence can be attached to a buffer which is being filled or consumed
by hw, to allow userspace to pass the buffer without waiting to another
device. For example, userspace can call page_flip ioctl to display the
next frame of graphics after kicking the GPU but while the GPU is still
rendering. The display device sharing the buffer with the GPU would
attach a callback to get notified when the GPU's rendering-complete IRQ
fires, to update the scan-out address of the display, without having to
wake up userspace.
A driver must allocate a fence context for each execution ring that can
run in parallel. The function for this takes an argument with how many
contexts to allocate:
+ fence_context_alloc()
A fence is transient, one-shot deal. It is allocated and attached
to one or more dma-buf's. When the one that attached it is done, with
the pending operation, it can signal the fence:
+ fence_signal()
To have a rough approximation whether a fence is fired, call:
+ fence_is_signaled()
The dma-buf-mgr handles tracking, and waiting on, the fences associated
with a dma-buf.
The one pending on the fence can add an async callback:
+ fence_add_callback()
The callback can optionally be cancelled with:
+ fence_remove_callback()
To wait synchronously, optionally with a timeout:
+ fence_wait()
+ fence_wait_timeout()
When emitting a fence, call:
+ trace_fence_emit()
To annotate that a fence is blocking on another fence, call:
+ trace_fence_annotate_wait_on(fence, on_fence)
A default software-only implementation is provided, which can be used
by drivers attaching a fence to a buffer when they have no other means
for hw sync. But a memory backed fence is also envisioned, because it
is common that GPU's can write to, or poll on some memory location for
synchronization. For example:
fence = custom_get_fence(...);
if ((seqno_fence = to_seqno_fence(fence)) != NULL) {
dma_buf *fence_buf = seqno_fence->sync_buf;
get_dma_buf(fence_buf);
... tell the hw the memory location to wait ...
custom_wait_on(fence_buf, seqno_fence->seqno_ofs, fence->seqno);
} else {
/* fall-back to sw sync * /
fence_add_callback(fence, my_cb);
}
On SoC platforms, if some other hw mechanism is provided for synchronizing
between IP blocks, it could be supported as an alternate implementation
with it's own fence ops in a similar way.
enable_signaling callback is used to provide sw signaling in case a cpu
waiter is requested or no compatible hardware signaling could be used.
The intention is to provide a userspace interface (presumably via eventfd)
later, to be used in conjunction with dma-buf's mmap support for sw access
to buffers (or for userspace apps that would prefer to do their own
synchronization).
v1: Original
v2: After discussion w/ danvet and mlankhorst on #dri-devel, we decided
that dma-fence didn't need to care about the sw->hw signaling path
(it can be handled same as sw->sw case), and therefore the fence->ops
can be simplified and more handled in the core. So remove the signal,
add_callback, cancel_callback, and wait ops, and replace with a simple
enable_signaling() op which can be used to inform a fence supporting
hw->hw signaling that one or more devices which do not support hw
signaling are waiting (and therefore it should enable an irq or do
whatever is necessary in order that the CPU is notified when the
fence is passed).
v3: Fix locking fail in attach_fence() and get_fence()
v4: Remove tie-in w/ dma-buf.. after discussion w/ danvet and mlankorst
we decided that we need to be able to attach one fence to N dma-buf's,
so using the list_head in dma-fence struct would be problematic.
v5: [ Maarten Lankhorst ] Updated for dma-bikeshed-fence and dma-buf-manager.
v6: [ Maarten Lankhorst ] I removed dma_fence_cancel_callback and some comments
about checking if fence fired or not. This is broken by design.
waitqueue_active during destruction is now fatal, since the signaller
should be holding a reference in enable_signalling until it signalled
the fence. Pass the original dma_fence_cb along, and call __remove_wait
in the dma_fence_callback handler, so that no cleanup needs to be
performed.
v7: [ Maarten Lankhorst ] Set cb->func and only enable sw signaling if
fence wasn't signaled yet, for example for hardware fences that may
choose to signal blindly.
v8: [ Maarten Lankhorst ] Tons of tiny fixes, moved __dma_fence_init to
header and fixed include mess. dma-fence.h now includes dma-buf.h
All members are now initialized, so kmalloc can be used for
allocating a dma-fence. More documentation added.
v9: Change compiler bitfields to flags, change return type of
enable_signaling to bool. Rework dma_fence_wait. Added
dma_fence_is_signaled and dma_fence_wait_timeout.
s/dma// and change exports to non GPL. Added fence_is_signaled and
fence_enable_sw_signaling calls, add ability to override default
wait operation.
v10: remove event_queue, use a custom list, export try_to_wake_up from
scheduler. Remove fence lock and use a global spinlock instead,
this should hopefully remove all the locking headaches I was having
on trying to implement this. enable_signaling is called with this
lock held.
v11:
Use atomic ops for flags, lifting the need for some spin_lock_irqsaves.
However I kept the guarantee that after fence_signal returns, it is
guaranteed that enable_signaling has either been called to completion,
or will not be called any more.
Add contexts and seqno to base fence implementation. This allows you
to wait for less fences, by testing for seqno + signaled, and then only
wait on the later fence.
Add FENCE_TRACE, FENCE_WARN, and FENCE_ERR. This makes debugging easier.
An CONFIG_DEBUG_FENCE will be added to turn off the FENCE_TRACE
spam, and another runtime option can turn it off at runtime.
v12:
Add CONFIG_FENCE_TRACE. Add missing documentation for the fence->context
and fence->seqno members.
v13:
Fixup CONFIG_FENCE_TRACE kconfig description.
Move fence_context_alloc to fence.
Simplify fence_later.
Kill priv member to fence_cb.
v14:
Remove priv argument from fence_add_callback, oops!
v15:
Remove priv from documentation.
Explicitly include linux/atomic.h.
v16:
Add trace events.
Import changes required by android syncpoints.
v17:
Use wake_up_state instead of try_to_wake_up. (Colin Cross)
Fix up commit description for seqno_fence. (Rob Clark)
v18:
Rename release_fence to fence_release.
Move to drivers/dma-buf/.
Rename __fence_is_signaled and __fence_signal to *_locked.
Rename __fence_init to fence_init.
Make fence_default_wait return a signed long, and fix wait ops too.
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Signed-off-by: Thierry Reding <thierry.reding@gmail.com> #use smp_mb__before_atomic()
Acked-by: Sumit Semwal <sumit.semwal@linaro.org>
Acked-by: Daniel Vetter <daniel@ffwll.ch>
Reviewed-by: Rob Clark <robdclark@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-07-01 18:57:14 +08:00
|
|
|
depends on DMA_SHARED_BUFFER
|
|
|
|
|
help
|
2016-10-25 20:00:45 +08:00
|
|
|
Enable the DMA_FENCE_TRACE printks. This will add extra
|
fence: dma-buf cross-device synchronization (v18)
A fence can be attached to a buffer which is being filled or consumed
by hw, to allow userspace to pass the buffer without waiting to another
device. For example, userspace can call page_flip ioctl to display the
next frame of graphics after kicking the GPU but while the GPU is still
rendering. The display device sharing the buffer with the GPU would
attach a callback to get notified when the GPU's rendering-complete IRQ
fires, to update the scan-out address of the display, without having to
wake up userspace.
A driver must allocate a fence context for each execution ring that can
run in parallel. The function for this takes an argument with how many
contexts to allocate:
+ fence_context_alloc()
A fence is transient, one-shot deal. It is allocated and attached
to one or more dma-buf's. When the one that attached it is done, with
the pending operation, it can signal the fence:
+ fence_signal()
To have a rough approximation whether a fence is fired, call:
+ fence_is_signaled()
The dma-buf-mgr handles tracking, and waiting on, the fences associated
with a dma-buf.
The one pending on the fence can add an async callback:
+ fence_add_callback()
The callback can optionally be cancelled with:
+ fence_remove_callback()
To wait synchronously, optionally with a timeout:
+ fence_wait()
+ fence_wait_timeout()
When emitting a fence, call:
+ trace_fence_emit()
To annotate that a fence is blocking on another fence, call:
+ trace_fence_annotate_wait_on(fence, on_fence)
A default software-only implementation is provided, which can be used
by drivers attaching a fence to a buffer when they have no other means
for hw sync. But a memory backed fence is also envisioned, because it
is common that GPU's can write to, or poll on some memory location for
synchronization. For example:
fence = custom_get_fence(...);
if ((seqno_fence = to_seqno_fence(fence)) != NULL) {
dma_buf *fence_buf = seqno_fence->sync_buf;
get_dma_buf(fence_buf);
... tell the hw the memory location to wait ...
custom_wait_on(fence_buf, seqno_fence->seqno_ofs, fence->seqno);
} else {
/* fall-back to sw sync * /
fence_add_callback(fence, my_cb);
}
On SoC platforms, if some other hw mechanism is provided for synchronizing
between IP blocks, it could be supported as an alternate implementation
with it's own fence ops in a similar way.
enable_signaling callback is used to provide sw signaling in case a cpu
waiter is requested or no compatible hardware signaling could be used.
The intention is to provide a userspace interface (presumably via eventfd)
later, to be used in conjunction with dma-buf's mmap support for sw access
to buffers (or for userspace apps that would prefer to do their own
synchronization).
v1: Original
v2: After discussion w/ danvet and mlankhorst on #dri-devel, we decided
that dma-fence didn't need to care about the sw->hw signaling path
(it can be handled same as sw->sw case), and therefore the fence->ops
can be simplified and more handled in the core. So remove the signal,
add_callback, cancel_callback, and wait ops, and replace with a simple
enable_signaling() op which can be used to inform a fence supporting
hw->hw signaling that one or more devices which do not support hw
signaling are waiting (and therefore it should enable an irq or do
whatever is necessary in order that the CPU is notified when the
fence is passed).
v3: Fix locking fail in attach_fence() and get_fence()
v4: Remove tie-in w/ dma-buf.. after discussion w/ danvet and mlankorst
we decided that we need to be able to attach one fence to N dma-buf's,
so using the list_head in dma-fence struct would be problematic.
v5: [ Maarten Lankhorst ] Updated for dma-bikeshed-fence and dma-buf-manager.
v6: [ Maarten Lankhorst ] I removed dma_fence_cancel_callback and some comments
about checking if fence fired or not. This is broken by design.
waitqueue_active during destruction is now fatal, since the signaller
should be holding a reference in enable_signalling until it signalled
the fence. Pass the original dma_fence_cb along, and call __remove_wait
in the dma_fence_callback handler, so that no cleanup needs to be
performed.
v7: [ Maarten Lankhorst ] Set cb->func and only enable sw signaling if
fence wasn't signaled yet, for example for hardware fences that may
choose to signal blindly.
v8: [ Maarten Lankhorst ] Tons of tiny fixes, moved __dma_fence_init to
header and fixed include mess. dma-fence.h now includes dma-buf.h
All members are now initialized, so kmalloc can be used for
allocating a dma-fence. More documentation added.
v9: Change compiler bitfields to flags, change return type of
enable_signaling to bool. Rework dma_fence_wait. Added
dma_fence_is_signaled and dma_fence_wait_timeout.
s/dma// and change exports to non GPL. Added fence_is_signaled and
fence_enable_sw_signaling calls, add ability to override default
wait operation.
v10: remove event_queue, use a custom list, export try_to_wake_up from
scheduler. Remove fence lock and use a global spinlock instead,
this should hopefully remove all the locking headaches I was having
on trying to implement this. enable_signaling is called with this
lock held.
v11:
Use atomic ops for flags, lifting the need for some spin_lock_irqsaves.
However I kept the guarantee that after fence_signal returns, it is
guaranteed that enable_signaling has either been called to completion,
or will not be called any more.
Add contexts and seqno to base fence implementation. This allows you
to wait for less fences, by testing for seqno + signaled, and then only
wait on the later fence.
Add FENCE_TRACE, FENCE_WARN, and FENCE_ERR. This makes debugging easier.
An CONFIG_DEBUG_FENCE will be added to turn off the FENCE_TRACE
spam, and another runtime option can turn it off at runtime.
v12:
Add CONFIG_FENCE_TRACE. Add missing documentation for the fence->context
and fence->seqno members.
v13:
Fixup CONFIG_FENCE_TRACE kconfig description.
Move fence_context_alloc to fence.
Simplify fence_later.
Kill priv member to fence_cb.
v14:
Remove priv argument from fence_add_callback, oops!
v15:
Remove priv from documentation.
Explicitly include linux/atomic.h.
v16:
Add trace events.
Import changes required by android syncpoints.
v17:
Use wake_up_state instead of try_to_wake_up. (Colin Cross)
Fix up commit description for seqno_fence. (Rob Clark)
v18:
Rename release_fence to fence_release.
Move to drivers/dma-buf/.
Rename __fence_is_signaled and __fence_signal to *_locked.
Rename __fence_init to fence_init.
Make fence_default_wait return a signed long, and fix wait ops too.
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Signed-off-by: Thierry Reding <thierry.reding@gmail.com> #use smp_mb__before_atomic()
Acked-by: Sumit Semwal <sumit.semwal@linaro.org>
Acked-by: Daniel Vetter <daniel@ffwll.ch>
Reviewed-by: Rob Clark <robdclark@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-07-01 18:57:14 +08:00
|
|
|
spam to the console log, but will make it easier to diagnose
|
|
|
|
|
lockup related problems for dma-buffers shared across multiple
|
|
|
|
|
devices.
|
|
|
|
|
|
2013-07-02 13:45:15 +08:00
|
|
|
config DMA_CMA
|
|
|
|
|
bool "DMA Contiguous Memory Allocator"
|
|
|
|
|
depends on HAVE_DMA_CONTIGUOUS && CMA
|
2011-12-29 20:09:51 +08:00
|
|
|
help
|
|
|
|
|
This enables the Contiguous Memory Allocator which allows drivers
|
|
|
|
|
to allocate big physically-contiguous blocks of memory for use with
|
|
|
|
|
hardware components that do not support I/O map nor scatter-gather.
|
|
|
|
|
|
2014-10-10 06:29:41 +08:00
|
|
|
You can disable CMA by specifying "cma=0" on the kernel's command
|
|
|
|
|
line.
|
|
|
|
|
|
2011-12-29 20:09:51 +08:00
|
|
|
For more information see <include/linux/dma-contiguous.h>.
|
|
|
|
|
If unsure, say "n".
|
|
|
|
|
|
2013-07-02 13:45:15 +08:00
|
|
|
if DMA_CMA
|
2011-12-29 20:09:51 +08:00
|
|
|
comment "Default contiguous memory area size:"
|
|
|
|
|
|
|
|
|
|
config CMA_SIZE_MBYTES
|
|
|
|
|
int "Size in Mega Bytes"
|
|
|
|
|
depends on !CMA_SIZE_SEL_PERCENTAGE
|
2014-12-11 07:43:14 +08:00
|
|
|
default 0 if X86
|
2011-12-29 20:09:51 +08:00
|
|
|
default 16
|
|
|
|
|
help
|
|
|
|
|
Defines the size (in MiB) of the default memory area for Contiguous
|
2014-12-11 07:43:14 +08:00
|
|
|
Memory Allocator. If the size of 0 is selected, CMA is disabled by
|
|
|
|
|
default, but it can be enabled by passing cma=size[MG] to the kernel.
|
|
|
|
|
|
2011-12-29 20:09:51 +08:00
|
|
|
|
|
|
|
|
config CMA_SIZE_PERCENTAGE
|
|
|
|
|
int "Percentage of total memory"
|
|
|
|
|
depends on !CMA_SIZE_SEL_MBYTES
|
2014-12-11 07:43:14 +08:00
|
|
|
default 0 if X86
|
2011-12-29 20:09:51 +08:00
|
|
|
default 10
|
|
|
|
|
help
|
|
|
|
|
Defines the size of the default memory area for Contiguous Memory
|
|
|
|
|
Allocator as a percentage of the total memory in the system.
|
2014-12-11 07:43:14 +08:00
|
|
|
If 0 percent is selected, CMA is disabled by default, but it can be
|
|
|
|
|
enabled by passing cma=size[MG] to the kernel.
|
2011-12-29 20:09:51 +08:00
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Selected region size"
|
2012-10-18 15:29:44 +08:00
|
|
|
default CMA_SIZE_SEL_MBYTES
|
2011-12-29 20:09:51 +08:00
|
|
|
|
|
|
|
|
config CMA_SIZE_SEL_MBYTES
|
|
|
|
|
bool "Use mega bytes value only"
|
|
|
|
|
|
|
|
|
|
config CMA_SIZE_SEL_PERCENTAGE
|
|
|
|
|
bool "Use percentage value only"
|
|
|
|
|
|
|
|
|
|
config CMA_SIZE_SEL_MIN
|
|
|
|
|
bool "Use lower value (minimum)"
|
|
|
|
|
|
|
|
|
|
config CMA_SIZE_SEL_MAX
|
|
|
|
|
bool "Use higher value (maximum)"
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config CMA_ALIGNMENT
|
|
|
|
|
int "Maximum PAGE_SIZE order of alignment for contiguous buffers"
|
2014-06-05 07:10:01 +08:00
|
|
|
range 4 12
|
2011-12-29 20:09:51 +08:00
|
|
|
default 8
|
|
|
|
|
help
|
|
|
|
|
DMA mapping framework by default aligns all buffers to the smallest
|
|
|
|
|
PAGE_SIZE order which is greater than or equal to the requested buffer
|
|
|
|
|
size. This works well for buffers up to a few hundreds kilobytes, but
|
|
|
|
|
for larger buffers it just a memory waste. With this parameter you can
|
|
|
|
|
specify the maximum PAGE_SIZE order for contiguous buffers. Larger
|
|
|
|
|
buffers will be aligned only to this specified order. The order is
|
|
|
|
|
expressed as a power of two multiplied by the PAGE_SIZE.
|
|
|
|
|
|
|
|
|
|
For example, if your system defaults to 4KiB pages, the order value
|
|
|
|
|
of 8 means that the buffers will be aligned up to 1MiB only.
|
|
|
|
|
|
|
|
|
|
If unsure, leave the default value "8".
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
2006-10-29 01:38:55 +08:00
|
|
|
endmenu
|