Searched +full:os +full:- +full:data +full:- +full:offset (Results 1 – 25 of 39) sorted by relevance
12
| /Documentation/devicetree/bindings/gpu/host1x/ |
| D | nvidia,tegra234-nvdec.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpu/host1x/nvidia,tegra234-nvdec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
15 - Thierry Reding <treding@gmail.com>
16 - Mikko Perttunen <mperttunen@nvidia.com>
20 pattern: "^nvdec@[0-9a-f]*$"
24 - nvidia,tegra234-nvdec
32 clock-names:
34 - const: nvdec
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | chromeos-acpi-device.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Chrome OS ACPI Device
7 Hardware functionality specific to Chrome OS is exposed through a Chrome OS ACPI device.
8 The plug and play ID of a Chrome OS ACPI device is GGL0001 and the hardware ID is
11 .. flat-table:: Supported ACPI Objects
13 :header-rows: 1
15 * - Object
16 - Description
18 * - CHSW
19 - Chrome OS switch positions
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-chromeos-acpi | 32 Returns switch position for Chrome OS specific hardware
56 Returns firmware version for the read-only portion of the
72 Returns type of the GPIO signal for the Chrome OS specific
121 Returns the SHA-1 or SHA-256 hash that is read out of the
123 is exported via ACPI so the OS can verify that the Management
132 Returns offset in CMOS bank 0 of the verified boot non-volatile
134 (that is, 'offset = 0' is the byte following the 14 bytes of
135 clock data).
142 Return the size in bytes of the verified boot non-volatile
150 Returns the verified boot data block shared between the
|
| /Documentation/devicetree/bindings/cache/ |
| D | l2c2x0.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
16 models (Note 1). Some of the properties that are just prefixed "cache-*" are
22 cache controllers as found in e.g. Cortex-A15/A7/A57/A53. These
28 - $ref: /schemas/cache-controller.yaml#
33 - enum:
34 - arm,pl310-cache
35 - arm,l220-cache
[all …]
|
| /Documentation/core-api/ |
| D | this_cpu_ops.rst | 14 this_cpu operations add a per cpu variable offset to the processor
19 the offset and the operation on the data. Therefore it is not
22 the operation on the data.
24 Read-modify-write operations are of particular interest. Frequently
33 data specific to the currently executing processor. Only the current
65 ------------------------------------
109 Note that these operations can only be used on per cpu data that is
113 guarantee that the OS will not move the process directly before or
128 ------------------
134 Takes the offset of a per cpu variable (&x !) and returns the address
[all …]
|
| /Documentation/block/ |
| D | data-integrity.rst | 2 Data Integrity
8 Modern filesystems feature checksumming of data and metadata to
9 protect against data corruption. However, the detection of the
11 after the data was written. At that point the original data that the
16 protocols (SBC Data Integrity Field, SCC protection proposal) as well
35 2. The Data Integrity Extensions
45 The SCSI Data Integrity Field works by appending 8 bytes of protection
46 information to each sector. The data + integrity metadata is stored
47 in 520 byte sectors on disk. Data + IMD are interleaved when
53 encouraged them to allow separation of the data and integrity metadata
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | verity.rst | 2 dm-verity
5 Device-Mapper's "verity" target provides transparent integrity checking of
7 This target is read-only.
21 This is the type of the on-disk hash format.
23 0 is the original format used in the Chromium OS.
32 This is the device containing data, the integrity of which needs to be
37 This is the device that supplies the hash tree data. It may be
40 dm-verity device.
43 The block size on a data device in bytes.
50 The number of data blocks on the data device. Additional blocks are
[all …]
|
| /Documentation/userspace-api/media/drivers/ |
| D | uvcvideo.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 This file documents some driver-specific aspects of the UVC driver, such as
7 driver-specific ioctls and implementation notes.
10 linux-media@vger.kernel.org.
14 ---------------------------
19 The UVC specification allows for vendor-specific extensions through extension
23 - through mappings of XU controls to V4L2 controls
24 - through a driver-specific ioctl interface
30 The second mechanism requires uvcvideo-specific knowledge for the application to
40 The UVC driver provides an API for user space applications to define so-called
[all …]
|
| /Documentation/driver-api/thermal/ |
| D | intel_dptf.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 ------------
31 ----------------------------
43 "42A441D6-AE6A-462b-A84B-4A8CE79027D3" : Passive 1
45 "3A95C389-E4B8-4629-A526-C52C88626BAE" : Active
47 "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" : Critical
49 "63BE270F-1C11-48FD-A6F7-3AF253FF3E2D" : Adaptive performance
51 "5349962F-71E6-431D-9AE8-0A635B710AEE" : Emergency call
53 "9E04115A-AE87-4D1C-9500-0F3E340BFE75" : Passive 2
55 "F5A35014-C209-46A4-993A-EB56DE7530A1" : Power Boss
[all …]
|
| /Documentation/admin-guide/kdump/ |
| D | vmcoreinfo.rst | 10 values, field offsets, etc. These data are packed into an ELF note
11 section and used by user-space tools like crash and makedumpfile to
18 ------------------------
25 ---------
27 The size of a page. It is the smallest unit of data used by the memory
32 -----------
36 data structure used to store information returned by the uname(2) system
39 User-space tools can get the kernel name, host name, kernel release
40 number, kernel version, architecture name and OS type from it.
43 ---------------------
[all …]
|
| /Documentation/filesystems/ |
| D | ext2.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 for NetBSD, FreeBSD, the GNU HURD, Windows 95/98/NT, OS/2 and RISC OS.
18 set using tune2fs(8). Kernel-determined defaults are indicated by (*).
34 errors=remount-ro Remount the filesystem read-only on an error.
40 nouid32 Use 16-bit UIDs and GIDs.
84 ------
93 ------------
97 of consecutive data. Information about each block group is kept in a
105 as the inode table for that block group and the remainder are the data
106 blocks. The block allocation algorithm attempts to allocate data blocks
[all …]
|
| D | zonefs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ZoneFS - Zone filesystem for Zoned block devices
11 as a file. Unlike a regular POSIX-compliant file system with native zoned block
18 than to a full-featured POSIX file system. The goal of zonefs is to simplify
22 example of this approach is the implementation of LSM (log-structured merge)
31 -------------------
62 by sub-directories. This file structure is built entirely using zone information
63 provided by the device and so does not require any complex on-disk metadata
66 On-disk metadata
67 ----------------
[all …]
|
| D | coda.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Coda Kernel-Venus Interface
10 Coda -- this document describes the client kernel-Venus interface.
35 level filesystem code needed for the operation of the Coda file sys-
51 4.1 Data structures shared by the kernel and Venus
109 return codes, and other data related to the request. Optionally the
117 will be given with the format of the data they handle. We shall also
123 the parameters and returned data is very similar to the BSD VFS. This
124 leads to an almost natural environment for implementing a kernel-level
142 traps to the OS kernel. Examples of such calls trapping to the kernel
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-block | 7 with 4KB physical sectors exposing 512-byte logical
10 offset from the disk's natural alignment.
21 device is offset from the internal allocation unit's
35 power-of-two and atomic_write_unit_max_bytes may also be
37 This parameter - along with atomic_write_unit_min_bytes
38 and atomic_write_unit_max_bytes - will not be larger than
50 atomic_write_unit_min. This value must be a power-of-two.
60 be a power-of-two. This value will not be larger than
72 power-of-two and at least the size as in
74 Any attempt to merge atomic write I/Os must not result in a
[all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra186-gpio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpio/nvidia,tegra186-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
33 GPIO data does not need access to these registers.
52 port, and the mapping from port name to register offset within a
53 controller, are both extremely non-linear. The header file
54 <dt-bindings/gpio/tegra186-gpio.h> describes the port-level mapping. In
[all …]
|
| /Documentation/arch/powerpc/ |
| D | firmware-assisted-dump.rst | 2 Firmware-Assisted Dump
7 The goal of firmware-assisted dump is to enable the dump of
8 a crashed system, and to do so from a fully-reset system, and
12 - Firmware-Assisted Dump (FADump) infrastructure is intended to replace
14 - Fadump uses the same firmware interfaces and memory reservation model
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore
19 - Unlike phyp dump, userspace tool does not need to refer any sysfs
21 - Unlike phyp dump, FADump allows user to release all the memory reserved
23 - Once enabled through kernel boot parameter, FADump can be
28 Comparing with kdump or other strategies, firmware-assisted
[all …]
|
| D | vas-api.rst | 1 .. SPDX-License-Identifier: GPL-2.0
2 .. _VAS-API:
12 allows both userspace and kernel communicate to co-processor
14 unit comprises of one or more hardware engines or co-processor types
21 Requests to the GZIP engine must be formatted as a co-processor Request
38 /dev/crypto/nx-gzip device node implemented by the VAS/NX device driver.
39 An application must open the /dev/crypto/nx-gzip device to obtain a file
58 NX-GZIP Device Node
61 There is one /dev/crypto/nx-gzip node in the system and it provides
63 /dev/crypto/nx-gzip are:
[all …]
|
| /Documentation/virt/ |
| D | ne_overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 For example, an application that processes sensitive data and runs in a VM,
29 1. An enclave abstraction process - a user space process running in the primary
42 2. The enclave itself - a VM running on the same host as the primary VM that
58 using virtio-vsock [5]. The primary VM has virtio-pci vsock emulated device,
59 while the enclave VM has a virtio-mmio vsock emulated device. The vsock device
60 uses eventfd for signaling. The enclave VM sees the usual interfaces - local
61 APIC and IOAPIC - to get interrupts from virtio-vsock device. The virtio-mmio
65 image together with the OS ( e.g. kernel, ramdisk, init ) that will run in the
82 The enclave image (EIF) is loaded in the enclave memory at offset 8 MiB. The
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | driver.rst | 25 number, sometime also referred to as ``offset``, which is a unique number
26 between 0 and n-1, n being the number of GPIOs managed by the chip.
29 example if a system uses a memory-mapped set of I/O-registers where 32 GPIO
30 lines are handled by one bit per line in a 32-bit register, it makes sense to
44 So for example one platform could use global numbers 32-159 for GPIOs, with a
46 global numbers 0..63 with one set of GPIO controllers, 64-79 with another type
47 of GPIO controller, and on one particular board 80-95 with an FPGA. The legacy
49 2000-2063 to identify GPIO lines in a bank of I2C GPIO expanders.
60 - methods to establish GPIO line direction
61 - methods used to access GPIO line values
[all …]
|
| /Documentation/staging/ |
| D | remoteproc.rst | 10 of operating system, whether it's Linux or any other flavor of real-time OS.
12 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
13 In a typical configuration, the dual cortex-A9 is running Linux in a SMP
22 platform-specific remoteproc drivers only need to provide a few low-level
24 (for more information about the virtio-based rpmsg bus and its drivers,
118 name of this remote processor, platform-specific ops handlers,
120 length of private data needed by the allocating rproc driver (in bytes).
154 This is called by the platform-specific rproc implementation, whenever
180 Returns 0 on success and -EINVAL if @rproc isn't valid.
190 non-remoteproc driver. This function can be called from atomic/interrupt
[all …]
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | iavf.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 2013-2018 Intel Corporation.
13 - Overview
14 - Identifying Your Adapter
15 - Additional Configurations
16 - Known Issues/Troubleshooting
17 - Support
30 The guest OS loading the iavf driver must support MSI-X interrupts.
53 ---------------------
58 # dmesg -n 8
[all …]
|
| D | ice.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 2018-2021 Intel Corporation.
13 - Overview
14 - Identifying Your Adapter
15 - Important Notes
16 - Additional Features & Configurations
17 - Performance Optimization
28 This driver supports XDP (Express Data Path) and AF_XDP zero-copy. Note that
43 -------------------------------------------
54 1) Make sure that your system's physical memory is in a high-performance
[all …]
|
| /Documentation/filesystems/iomap/ |
| D | operations.rst | 1 .. SPDX-License-Identifier: GPL-2.0
35 linked lists of buffer heads instead of the per-folio bitmaps that iomap
42 -----------------------------------
61 --------------------------
63 The ``->iomap_begin`` function for pagecache operations may set the
67 .. code-block:: c
79 - ``get_folio``: Called to allocate and return an active reference to
83 This could be used to `set up per-folio filesystem state
84 <https://lore.kernel.org/all/20190429220934.10415-5-agruenba@redhat.com/>`_
87 - ``put_folio``: Called to unlock and put a folio after a pagecache
[all …]
|
| /Documentation/devicetree/bindings/thermal/ |
| D | thermal-zones.yaml | 1 # SPDX-License-Identifier: (GPL-2.0)
4 ---
5 $id: http://devicetree.org/schemas/thermal/thermal-zones.yaml#
6 $schema: http://devicetree.org/meta-schemas/base.yaml#
11 - Daniel Lezcano <daniel.lezcano@linaro.org>
20 - thermal-sensor: device that measures temperature, has SoC-specific bindings
21 - cooling-device: device used to dissipate heat either passively or actively
22 - thermal-zones: a container of the following node types used to describe all
23 thermal data for the platform
25 This binding describes the thermal-zones.
[all …]
|
| /Documentation/scsi/ |
| D | aic79xx.rst | 1 .. SPDX-License-Identifier: GPL-2.0
28 AIC-7901A Single Channel 64-bit PCI-X 133MHz to
30 AIC-7901B Single Channel 64-bit PCI-X 133MHz to
32 AIC-7902A4 Dual Channel 64-bit PCI-X 133MHz to
34 AIC-7902B Dual Channel 64-bit PCI-X 133MHz to
41 Adaptec SCSI Card 39320 Dual Channel 64-bit PCI-X 133MHz to 7902A4/7902B
43 68-pin, two internal 68-pin)
44 Adaptec SCSI Card 39320A Dual Channel 64-bit PCI-X 133MHz to 7902B
46 68-pin, two internal 68-pin)
47 Adaptec SCSI Card 39320D Dual Channel 64-bit PCI-X 133MHz to 7902A4
[all …]
|
12