Searched +full:user +full:- +full:defined (Results 1 – 25 of 451) sorted by relevance
12345678910>>...19
| /Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 6 ------- 21 $(CC) -o $(APP) $(SRC) 27 gcc -o foo foo.c 32 The idea is quite similar in Kconfig - it is possible to describe a Kconfig 38 def_bool $(shell, $(srctree)/scripts/gcc-check-foo.sh $(CC)) 46 Then, Kconfig moves onto the evaluation stage to resolve inter-symbol 47 dependency as explained in kconfig-language.rst. 51 --------- 56 $( ). The parentheses are required even for single-letter variable names; $X is 62 A simply expanded variable is defined using the := assignment operator. Its [all …]
|
| /Documentation/arch/riscv/ |
| D | hwprobe.rst | 1 .. SPDX-License-Identifier: GPL-2.0 3 RISC-V Hardware Probing Interface 4 --------------------------------- 6 The RISC-V hardware probing interface is based around a single syscall, which 7 is defined in <asm/hwprobe.h>:: 18 The arguments are split into three groups: an array of key-value pairs, a CPU 19 set, and some flags. The key-value pairs are supplied with a count. Userspace 22 will be cleared to -1, and its value set to 0. The CPU set is defined by 23 CPU_SET(3) with size ``cpusetsize`` bytes. For value-like keys (eg. vendor, 25 have the same value. Otherwise -1 will be returned. For boolean-like keys, the [all …]
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | dtx.rst | 1 .. SPDX-License-Identifier: GPL-2.0+ 10 User-Space DTX (Clipboard Detachment System) Interface 14 and re-attachment handling. To this end, it provides the ``/dev/surface/dtx`` 15 device file, through which it can interface with a user-space daemon. This 18 unloading/reloading the graphics-driver, user-notifications, etc. 24 change. Commands are always driver-initiated, whereas events are always 56 ------------ 60 the *open* state, the clipboard can be removed by a user. 65 being hot-unplugged while in use. More details can be found in the 70 -------------------- [all …]
|
| D | cdev.rst | 1 .. SPDX-License-Identifier: GPL-2.0+ 8 User-Space EC Interface (cdev) 11 The ``surface_aggregator_cdev`` module provides a misc-device for the SSAM 12 controller to allow for a (more or less) direct connection from user-space to 18 device-file. All functionality of this interface is provided via IOCTLs. 19 These IOCTLs and their respective input/output parameter structs are defined in 23 at https://github.com/linux-surface/surface-aggregator-module/tree/master/scripts/ssam. 31 Events can be received by reading from the device-file. The are represented by 37 interface, associated with a specific target category and device-file-instance. 43 notifiers work per-client (i.e. per-device-file-instance), events are enabled [all …]
|
| /Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 In order to support ACPI open-ended hardware configurations (e.g. development 19 user defined SSDT tables that contain the board specific information. 59 ASL Optimizing Compiler version 20140214-64 [Mar 29 2014] 60 Copyright (c) 2000 - 2014 Intel Corporation 62 ASL Input: minnomax.asl - 30 lines, 614 bytes, 7 keywords 63 AML Output: minnowmax.aml - 165 bytes, 6 named objects, 1 executable opcodes 73 This option allows loading of user defined SSDTs from initrd and it is useful 90 mkdir -p kernel/firmware/acpi 95 find kernel | cpio -H newc --create > /boot/instrumented_initrd [all …]
|
| /Documentation/watchdog/ |
| D | mlx-wdt.rst | 16 Actual HW timeout can be defined as a power of 2 msec. 19 Get time-left isn't supported 22 Actual HW timeout is defined in sec. and it's the same as 23 a user-defined timeout. 25 Get time-left is supported. 43 There are several actions that can be defined in the watchdog: 50 user space application. 54 This mlx-wdt driver supports both HW watchdog implementations. 58 Mellanox watchdog device, identity name (mlx-wdt-main or mlx-wdt-aux), 61 version - type1 or type2. [all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-acpi | 4 Contact: linux-acpi@vger.kernel.org 7 contains sub-groups corresponding to ACPI configurable options. 14 This group contains the configuration for user defined ACPI 15 tables. The attributes of a user define table are: 18 - a binary attribute that the user can use to 23 successful the user must check the error code 27 The rest of the attributes are read-only and are valid only 31 - ASCII table signature 34 - length of table in bytes, including the header 37 - ACPI Specification minor version number [all …]
|
| /Documentation/virt/kvm/devices/ |
| D | vm.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 struct kvm_device_attr as other devices, but targets VM-wide settings 21 ------------------------------------------- 24 :Returns: -EBUSY if a vcpu is already defined, otherwise 0 29 ---------------------------------------- 32 :Returns: -EINVAL if CMMA was not enabled; 39 ----------------------------------------- 41 :Parameters: in attr->addr the address for the new limit of guest memory 42 :Returns: -EFAULT if the given address is not accessible; 43 -EINVAL if the virtual machine is of type UCONTROL; [all …]
|
| /Documentation/kernel-hacking/ |
| D | hacking.rst | 20 this document, being grossly under-qualified, but I always wanted to 30 - not associated with any process, serving a hardware interrupt; 32 - not associated with any process, serving a softirq or tasklet; 34 - running in kernel space, associated with a process (user context); 36 - running a process in user space. 44 We'll see a number of ways that the user context can block interrupts, 45 to become truly non-preemptable. 47 User Context 48 ------------ 50 User context is when you are coming in from a system call or other trap: [all …]
|
| /Documentation/power/ |
| D | freezing-of-tasks.rst | 10 The freezing of tasks is a mechanism by which user space processes and some 11 kernel threads are controlled during hibernation or system-wide suspend (on some 17 There is one per-task flag (PF_NOFREEZE) and three per-task states 19 The tasks that have PF_NOFREEZE unset (all user space tasks and some kernel 23 to system-wide suspend too). 26 freeze_processes() (defined in kernel/power/process.c) is called. A system-wide 27 static key freezer_active (as opposed to a per-task flag or state) is used to 30 try_to_freeze_tasks() that sends a fake signal to all user space processes, and 32 calling try_to_freeze(), which results in a call to __refrigerator() (defined 36 referred to as 'the freezer' (these functions are defined in [all …]
|
| /Documentation/driver-api/rapidio/ |
| D | rio_cm.rst | 19 This driver (RIO_CM) provides to user-space applications shared access to 23 messaging mailboxes in case of multi-packet message (up to 4KB) and 24 up to 64 mailboxes if single-packet messages (up to 256 B) are used. In addition 30 capability to large number of user-space processes by introducing socket-like 39 Following ioctl commands are available to user-space applications: 41 - RIO_CM_MPORT_GET_LIST: 46 - RIO_CM_EP_GET_LIST_SIZE: 49 - RIO_CM_EP_GET_LIST: 53 - RIO_CM_CHAN_CREATE: 56 - RIO_CM_CHAN_BIND: [all …]
|
| D | mport_cdev.rst | 17 for user-space applications. Most of RapidIO operations are supported through 24 Using available set of ioctl commands user-space applications can perform 27 - Reads and writes from/to configuration registers of mport devices 29 - Reads and writes from/to configuration registers of remote RapidIO devices. 30 This operations are defined as RapidIO Maintenance reads/writes in RIO spec. 32 - Set RapidIO Destination ID for mport devices (RIO_MPORT_MAINT_HDID_SET) 33 - Set RapidIO Component Tag for mport devices (RIO_MPORT_MAINT_COMPTAG_SET) 34 - Query logical index of mport devices (RIO_MPORT_MAINT_PORT_IDX_GET) 35 - Query capabilities and RapidIO link configuration of mport devices 37 - Enable/Disable reporting of RapidIO doorbell events to user-space applications [all …]
|
| /Documentation/admin-guide/LSM/ |
| D | apparmor.rst | 10 from user space. Tasks on the system that do not have a profile defined for 34 policy must be loaded into the kernel from user space (see the Documentation 45 Mailing List - apparmor@lists.ubuntu.com 47 Wiki - http://wiki.apparmor.net 49 User space tools - https://gitlab.com/apparmor 51 Kernel module - git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor
|
| /Documentation/networking/devlink/ |
| D | devlink-region.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 ``devlink`` regions enable access to driver defined address regions using 22 address regions that are otherwise inaccessible to the user. 25 states, but see also Documentation/networking/devlink/devlink-health.rst 32 the snapshot information to user space. 39 structure. User space can request a direct read by using the 44 ------------- 56 pci/0000:00:05.0/cr-space: size 1048576 snapshot [1 2] max 8 57 pci/0000:00:05.0/fw-health: size 64 snapshot [1 2] max 8 60 $ devlink region del pci/0000:00:05.0/cr-space snapshot 1 [all …]
|
| /Documentation/networking/device_drivers/ethernet/altera/ |
| D | altera_tse.rst | 1 .. SPDX-License-Identifier: GPL-2.0 6 Altera Triple-Speed Ethernet MAC driver 9 Copyright |copy| 2008-2014 Altera Corporation 11 This is the driver for the Altera Triple-Speed Ethernet (TSE) controllers 24 The Triple-Speed Ethernet, SGDMA, and MSGDMA components are all soft IP 31 Triple-Speed Ethernet instance is using an SGDMA or MSGDMA component. The 36 The SGDMA component is to be deprecated in the near future (over the next 1-2 46 Scatter-gather DMA is not supported by the SGDMA or MSGDMA at this time. 47 Scatter-gather DMA will be added to a future maintenance update to this 60 Device Drivers ---> Network device support ---> Ethernet driver support ---> [all …]
|
| /Documentation/security/keys/ |
| D | ecryptfs.rst | 9 either in kernel space or in user space with a daemon called 'ecryptfsd'. In 11 using a key, the FEKEK, derived from a user prompted passphrase; in the latter 16 The data structure defined by eCryptfs to contain information required for the 18 kernel key of the 'user' type, inserted in the user's session specific keyring 20 'ecryptfs-utils'. 28 In order to avoid known-plaintext attacks, the datablob obtained through 42 keyctl add encrypted name "new ecryptfs key-type:master-key-name keylen" ring 44 keyctl update keyid "update key-type:master-key-name" 49 key-type:= 'trusted' | 'user' 56 'ecryptfs' and save it using a previously loaded user key "test":: [all …]
|
| /Documentation/filesystems/ |
| D | quota.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 and the second one hardlimit. A user can never exceed a hardlimit for any 12 resource (unless he has CAP_SYS_RESOURCE capability). User is allowed to exceed 14 period" or "grace time". When grace time is over, user is not able to allocate 20 For more details about quota design, see the documentation in quota-tools package 25 When user exceeds a softlimit, runs out of grace time or reaches hardlimit, 28 when user is using a graphical desktop he usually cannot see the message. 46 - type of quota being exceeded (one of USRQUOTA, GRPQUOTA) 48 - UID/GID (depends on quota type) of user / group whose limit 51 - UID of a user who caused the event [all …]
|
| D | relay.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 to userspace via user-defined 'relay channels'. 11 A 'relay channel' is a kernel->user data relay mechanism implemented 12 as a set of per-cpu kernel buffers ('channel buffers'), each 13 represented as a regular file ('relay file') in user space. Kernel 16 buffer. User space applications mmap() or read() from the relay files 25 filtering - this also is left to the kernel client. The purpose is to 30 functions in the relay interface code - please see that for details. 36 sub-buffers. Messages are written to the first sub-buffer until it is 38 the next (if available). Messages are never split across sub-buffers. [all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | davinci-evm-audio.txt | 4 - compatible : "ti,da830-evm-audio" : forDM365/DA8xx/OMAPL1x/AM33xx 5 - ti,model : The user-visible name of this sound complex. 6 - ti,audio-codec : The phandle of the TLV320AIC3x audio codec 7 - ti,mcasp-controller : The phandle of the McASP controller 8 - ti,audio-routing : A list of the connections between audio components. 14 - ti,codec-clock-rate : The Codec Clock rate (in Hz) applied to the Codec. 15 - clocks : Reference to the master clock 16 - clock-names : The clock should be named "mclk" 17 - Either codec-clock-rate or the codec-clock reference has to be defined. If 18 the both are defined the driver attempts to set referenced clock to the [all …]
|
| /Documentation/hwmon/ |
| D | occ.rst | 1 Kernel driver occ-hwmon 12 ----------- 14 This driver supports hardware monitoring for the On-Chip Controller (OCC) 20 manually if an "ibm,p8-occ-hwmon" compatible device is found under the 21 appropriate I2C bus node in the device-tree. 23 The P9 version of this driver is a client driver of the FSI-based OCC driver. 24 It will be probed automatically by the FSI-based OCC driver. 27 ------------- 29 The following attributes are supported. All attributes are read-only unless 35 to the device driver, which must therefore export the sensor ID as-is. [all …]
|
| /Documentation/scsi/ |
| D | st.rst | 1 .. SPDX-License-Identifier: GPL-2.0 21 1. Each user can specify the tape parameters he/she wants to use 23 flexible method and applicable to single-user workstations. However, 24 in a multiuser environment the next user finds the tape parameters in 25 state the previous user left them. 32 drive performs auto-detection of the tape format well (like some 33 QIC-drives). The result is that any tape can be read, writing can be 37 does not perform auto-detection well enough and there is a single 40 or not :-). 42 The user can override the parameters defined by the system [all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | mtd.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Miquel Raynal <miquel.raynal@bootlin.com> 11 - Richard Weinberger <richard@nod.at> 21 User-defined MTD device name. Can be used to assign user friendly 26 '#address-cells': 29 '#size-cells': 36 - compatible 39 "@[0-9a-f]+$": [all …]
|
| /Documentation/userspace-api/netlink/ |
| D | specs.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause 9 separating Netlink parsing from user space logic and minimize the amount of 17 - the C uAPI header 18 …- documentation of the protocol as a ReST file - see :ref:`Documentation/networking/netlink_spec/i… 19 - policy tables for input attribute validation 20 - operation tables 25 See :doc:`intro-specs` for a practical starting guide. 28 ``((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)`` 29 to allow for easy adoption in user space code. 37 user capable of parsing more complex ``genetlink`` schemas is also compatible [all …]
|
| /Documentation/admin-guide/media/ |
| D | ipu3.rst | 1 .. SPDX-License-Identifier: GPL-2.0 24 ImgU). The CIO2 driver is available as drivers/media/pci/intel/ipu3/ipu3-cio2* 36 Both of the drivers implement V4L2, Media Controller and V4L2 sub-device 38 MIPI CSI-2 interfaces through V4L2 sub-device sensor drivers. 44 interface to the user space. There is a video node for each CSI-2 receiver, 47 The CIO2 contains four independent capture channel, each with its own MIPI CSI-2 48 receiver and DMA engine. Each channel is modelled as a V4L2 sub-device exposed 49 to userspace as a V4L2 sub-device node and has two pads: 53 .. flat-table:: 54 :header-rows: 1 [all …]
|
| /Documentation/devicetree/bindings/spmi/ |
| D | spmi.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Stephen Boyd <sboyd@kernel.org> 13 The System Power Management (SPMI) controller is a 2-wire bus defined 17 bindings defined here, plus any bus controller specific properties, if 27 "#address-cells": 30 "#size-cells": 34 "@[0-9a-f]$": 41 - minItems: 1 [all …]
|
12345678910>>...19