Searched +full:user +full:- +full:level (Results 1 – 25 of 341) sorted by relevance
12345678910>>...14
| /Documentation/ia64/ |
| D | fsys.rst | 2 Light-weight System Calls for IA-64
5 Started: 13-Jan-2003
7 Last update: 27-Sep-2003
9 David Mosberger-Tang
14 "fsys-mode". To recap, the normal states of execution are:
16 - kernel mode:
18 switched over to kernel memory. The user-level state is saved
19 in a pt-regs structure at the top of the kernel memory stack.
21 - user mode:
23 user memory. The user-level state is contained in the
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | video_extension.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 Export a sysfs interface for user space to control backlight level
26 Documentation/ABI/stable/sysfs-class-backlight.
32 get the brightness level the firmware thinks it is at;
36 on write, control method _BCM will run to set the requested brightness level;
70 as a "brightness level" indicator. Thus from the user space perspective
74 Notify user space about hotkey event
79 i) For some laptops, when user presses the hotkey, a scancode will be
80 generated and sent to user space through the input device created by
82 following key code will appear to user space::
[all …]
|
| /Documentation/networking/ |
| D | nfc.txt | 11 ---------------------
14 - NFC adapters management;
15 - Polling for targets;
16 - Low-level data exchange;
20 responsible for providing an interface to control operations and low-level
25 The low-level data exchange interface is provided by the new socket family
29 +--------------------------------------+
30 | USER SPACE |
31 +--------------------------------------+
33 | low-level | control
[all …]
|
| /Documentation/driver-api/thermal/ |
| D | x86_pkg_temperature_thermal.rst | 7 * x86: with package level thermal management
14 ---------
16 Intel® 64 and IA-32 Architectures Software Developer’s Manual (Jan, 2013):
17 Chapter 14.6: PACKAGE LEVEL THERMAL MANAGEMENT
20 -----------
22 This driver register CPU digital temperature package level sensor as a thermal
23 zone with maximum two user mode configurable trip points. Number of trip points
25 user mode can receive notification via thermal notification mechanism and can
30 --------------------
39 - trip_point_0_temp
[all …]
|
| D | intel_powerclamp.rst | 6 - Arjan van de Ven <arjan@linux.intel.com>
7 - Jacob Pan <jacob.jun.pan@linux.intel.com>
12 - Goals and Objectives
15 - Idle Injection
16 - Calibration
19 - Effectiveness and Limitations
20 - Power vs Performance
21 - Scalability
22 - Calibration
23 - Comparison with Alternative Techniques
[all …]
|
| /Documentation/scsi/ |
| D | megaraid.txt | 5 --------
8 user applications in a similar way. They understand the same firmware control
11 interfaces with the applications on one side and all the low level drivers
16 i. Avoid duplicate code from the low level drivers.
17 ii. Unburden the low level drivers from having to export the
21 multiple low level drivers.
24 ioctl commands. But this module is envisioned to handle all user space level
29 -------
36 - Jeff Garzik (jgarzik@pobox.com), 02.25.2004 LKML
38 "As Jeff hinted, if your userspace<->driver API is consistent between
[all …]
|
| D | scsi.txt | 5 http://www.tldp.org/HOWTO/SCSI-2.4-HOWTO . The LDP has single
8 http://web.archive.org/web/*/http://www.torque.net/scsi/SCSI-2.4-HOWTO
13 different ways depending upon the needs of the end user. To understand
16 The scsi-core (also known as the "mid level") contains the core of scsi
25 The individual upper and lower level drivers can be loaded in any order
29 level drivers to support the various assorted devices which can be
34 The lower level drivers are the ones that support the individual cards that
38 Adaptec. Almost all lower level drivers can be built either as modules or
|
| /Documentation/x86/x86_64/ |
| D | 5level-paging.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 5-level paging
9 Original x86-64 was limited by 4-level paing to 256 TiB of virtual address
14 5-level paging. It is a straight-forward extension of the current page
20 QEMU 2.9 and later support 5-level paging.
22 Virtual memory layout for 5-level paging is described in
26 Enabling 5-level paging
30 Kernel with CONFIG_X86_5LEVEL=y still able to boot on 4-level hardware.
31 In this case additional page table level -- p4d -- will be folded at
34 User-space and large virtual address space
[all …]
|
| /Documentation/admin-guide/ |
| D | thunderbolt.rst | 5 should be a userspace tool that handles all the low-level details, keeps
9 found in ``Documentation/ABI/testing/sysfs-bus-thunderbolt``.
13 ``/etc/udev/rules.d/99-local.rules``::
22 -----------------------------------
24 security levels available. Intel Titan Ridge added one more security level
33 All devices are automatically connected by the firmware. No user
37 user
38 User is asked whether the device is allowed to be connected.
40 ``/sys/bus/thunderbolt/devices``, the user then can make the decision.
44 User is asked whether the device is allowed to be connected. In
[all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | sodaville.txt | 14 - <1st cell>: The interrupt-number that identifies the interrupt source.
15 - <2nd cell>: The level-sense information, encoded as follows:
16 4 - active high level-sensitive
17 8 - active low level-sensitive
19 Example of the GPIO device and one user:
23 #gpio-cells = <2>;
24 #interrupt-cells = <2>;
34 interrupt-controller;
35 gpio-controller;
41 /* User the 11th GPIO line as an active high triggered
[all …]
|
| /Documentation/usb/ |
| D | functionfs.rst | 7 the user space driver has registered by writing descriptors and
8 strings (the user space program has to provide the same information
9 that kernel level composite functions provide when they are added to
15 From user space point of view it is a file system which when
16 mounted provides an "ep0" file. User space driver need to
42 where the last two are implemented via FunctionFS. On user space
43 level it would look like this::
46 $ mkdir /dev/ffs-mtp && mount -t functionfs mtp /dev/ffs-mtp
47 $ ( cd /dev/ffs-mtp && mtp-daemon ) &
48 $ mkdir /dev/ffs-hid && mount -t functionfs hid /dev/ffs-hid
[all …]
|
| /Documentation/driver-api/serial/ |
| D | serial-rs485.rst | 8 EIA-485, also known as TIA/EIA-485 or RS-485, is a standard defining the
15 2. Hardware-related Considerations
18 Some CPUs/UARTs (e.g., Atmel AT91 or 16C950 UART) contain a built-in
19 half-duplex mode capable of automatically controlling line direction by
21 half-duplex hardware like an RS485 transceiver or any RS232-connected
22 half-duplex devices like some modems.
26 available at user-level to allow switching from one mode to the other, and
46 4. Usage from user-level
49 From user-level, RS485 configuration can be get/set using the previous
68 /* Set logical level for RTS pin equal to 1 when sending: */
[all …]
|
| D | serial-iso7816.rst | 11 2. Hardware-related considerations
14 Some CPUs/UARTs (e.g., Microchip AT91) contain a built-in mode capable of
19 available at user-level to allow switching from one mode to the other, and
35 4. Usage from user-level
38 From user-level, ISO7816 configuration can be get/set using the previous
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-power | 5 Contact: linux-pm@vger.kernel.org
14 Contact: linux-pm@vger.kernel.org
23 Contact: linux-pm@vger.kernel.org
32 Contact: linux-pm@vger.kernel.org
43 Contact: linux-pm@vger.kernel.org
47 Valid values: 0 - 100 (percent)
51 Contact: linux-pm@vger.kernel.org
53 Maximum battery capacity trip-wire value where the supply will
54 notify user-space of the event. This is normally used for the
55 battery discharging scenario where user-space needs to know the
[all …]
|
| D | sysfs-driver-samsung-laptop | 4 Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
10 will show the current performance level. Writing to the
19 anything, other than making the user feel a bit better.
25 Description: Max battery charge level can be modified, battery cycle
27 level.
|
| D | sysfs-driver-bd9571mwv-regulator | 1 What: /sys/bus/i2c/devices/.../bd9571mwv-regulator.*.auto/backup_mode
12 B. With a toggle power switch (or level signal), the
16 wake-up switch,
23 DDR Backup Mode must be explicitly enabled by the user,
26 Users: User space applications for embedded boards equipped with a
|
| /Documentation/virt/kvm/devices/ |
| D | xive.txt | 29 - Interrupt Pending Buffer (IPB)
30 - Current Processor Priority (CPPR)
31 - Notification Source Register (NSR)
36 third (operating system) and the fourth (user level) are exposed the
46 3. Device pass-through
48 When a device is passed-through into the guest, the source
58 interrupt of the device being passed-through or the initial IPI ESB
63 helpers in KVM-PPC.
84 Interrupt source number (64-bit)
87 values: | unused | level | type
[all …]
|
| /Documentation/maintainer/ |
| D | configure-git.rst | 6 This chapter describes maintainer level git configuration.
8 Tagged branches used in :ref:`Documentation/maintainer/pull-requests.rst
10 tags can be created by passing the ``-u`` flag to ``git tag``. However,
15 git config user.signingkey "keyname"
20 [user]
|
| /Documentation/filesystems/ |
| D | 9p.txt | 21 http://xcpu.org/papers/xcpu-talk.pdf
25 http://xcpu.org/papers/cellfs-talk.pdf
28 * VirtFS: A Virtualization Aware File System pass-through
36 mount -t 9p 10.10.1.2 /mnt/9
38 For Plan 9 From User Space applications (http://swtch.com/plan9)
40 mount -t 9p `namespace`/acme /mnt/9 -o trans=unix,uname=$USER
44 mount -t 9p -o trans=virtio <mount_tag> /mnt/9
56 unix - specifying a named pipe mount point
57 tcp - specifying a normal TCP/IP connection
58 fd - used passed file descriptors for connection
[all …]
|
| /Documentation/admin-guide/wimax/ |
| D | wimax.rst | 7 :Copyright: |copy| 2008 Intel Corporation < linux-wimax@intel.com >
10 control API for WiMAX devices, usable from kernel and user space.
26 the user. As well, the stack provides API functions that the driver
29 The stack exports the API calls needed to control the device to user
32 convenience in libwimax (in the wimax-tools package).
48 -------------------------------------------------
53 The drivers will register debugfs entries that allow the user to tweak
61 ------------------------------
66 # find /sys/kernel/debug/wimax\:wmx0 -name \*dl_\*
80 level; by writing to it, you can set it.
[all …]
|
| /Documentation/x86/ |
| D | pti.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 countermeasure against attacks on the shared user/kernel address
18 switches back to user mode, the user copy is used again.
27 This approach helps to ensure that side-channel attacks leveraging
30 Once enabled at compile-time, it can be disabled at boot with the
31 'nopti' or 'pti=' kernel parameters (see kernel-parameters.txt).
41 Although _complete_, the user portion of the kernel page tables is
42 crippled by setting the NX bit in the top level. This ensures
43 that any missed kernel->user CR3 switch will immediately crash
49 each CPU's copy of the area a compile-time-fixed virtual address.
[all …]
|
| /Documentation/media/v4l-drivers/ |
| D | si4713.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 ----------------------------
17 Basically, it has transmission and signal noise level measurement features.
29 -------------------------
34 The I2C device driver exports a v4l2-subdev interface to the kernel.
36 using the v4l2-subdev calls (g_ext_ctrls, s_ext_ctrls).
38 The platform device driver exports a v4l2 radio device interface to user land.
39 So, it uses the I2C device driver as a sub device in order to send the user
48 ----------------------
51 Here is an output from v4l2-ctl util:
[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
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
38 kernel level.
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/misc-devices/ |
| D | apds990x.txt | 14 -----------
22 using clear channel only. Lux value and the threshold level on the HW
25 Driver makes necessary conversions to both directions so that user handles
27 channels. HW threshold level is calculated from the given lux value to match
45 -----
49 RO - shows detected chip type and version
52 RW - enable / disable chip. Uses counting logic
56 RO - measured lux value
60 RO - lux0_input max value. Actually never reaches since sensor tends
65 RW - measurement rate in Hz
[all …]
|
| /Documentation/sparc/oradax/ |
| D | oracle-dax.rst | 10 and data formats. A user space library provides high level services
11 and translates these into low level commands which are then passed
17 code sufficient to write user or kernel applications that use DAX
20 The user library is open source and available at:
25 the accompanying document, dax-hv-api.txt, which is a plain text
27 Specification" version 3.0.20+15, dated 2017-09-25.
30 High Level Overview
51 done at the user level, which results in almost zero latency between
60 architecture, as there is an additional level of memory virtualization
61 present. This intermediate level is called "real" memory, and the
[all …]
|
12345678910>>...14