Searched +full:image +full:- +full:specific (Results 1 – 25 of 140) sorted by relevance
123456
| /Documentation/arch/powerpc/ |
| D | bootwrapper.rst | 7 PowerPC image targets compresses and wraps the kernel image (vmlinux) with
10 be adaptable for each kind of image that needs to be built.
13 Makefile in that directory has targets for all the available image types.
14 The different image types are used to support all of the various firmware
17 others. U-Boot is typically found on embedded PowerPC hardware, but there
19 firmware interface requires a different image format.
23 image. The details of the build system is discussed in the next section.
24 Currently, the following image format targets exist:
28 U-Boot (for versions that don't understand the device
29 tree). This image embeds a device tree blob inside
[all …]
|
| D | cxl.rst | 28 +----------+ +---------+
34 +----------+ +---------+
36 | +------+ | PSL |
37 | | CAPP |<------>| |
38 +---+------+ PCIE +---------+
47 (AFU). The AFU is used to implement specific functionality behind
65 - POWER8 and PSL Version 8 are compliant to the CAIA Version 1.0.
66 - POWER9 and PSL Version 9 are compliant to the CAIA Version 2.0.
91 applications may use the accelerator (although specific AFUs may
123 The WED is a 64-bit parameter passed to the AFU when a context is
[all …]
|
| /Documentation/arch/arm/google/ |
| D | chromebook-boot-flow.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 Image`_ which contains an OS image as well as a collection of device trees. It
10 is up to depthcharge_ to pick the right device tree from the `FIT Image`_ and
16 - Board name, specified at depthcharge_ compile time. This is $(BOARD) below.
17 - Board revision number, determined at runtime (perhaps by reading GPIO
19 - SKU number, read from GPIO strappings at boot time. This is $(SKU) below.
23 - google,$(BOARD)-rev$(REV)-sku$(SKU)
24 - google,$(BOARD)-rev$(REV)
25 - google,$(BOARD)-sku$(SKU)
26 - google,$(BOARD)
[all …]
|
| /Documentation/driver-api/fpga/ |
| D | fpga-mgr.rst | 5 --------
8 an image. The API is manufacturer agnostic. All manufacturer specifics are
10 The FPGA image data itself is very manufacturer specific, but for our purposes
13 The FPGA image to be programmed can be in a scatter gather list, a single
18 The particulars for programming the image are presented in a structure (struct
20 FPGA image as well as image-specific particulars such as whether the image was
24 --------------------------------
39 struct device *dev = &pdev->dev;
46 return -ENOMEM;
79 The ops will implement whatever device specific register writes are needed to
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-image-process.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _image-process-controls:
6 Image Process Control Reference
9 The Image Process control class is intended for low-level control of
10 image processing functions. Unlike ``V4L2_CID_IMAGE_SOURCE_CLASS``, the
11 controls in this class affect processing the image, and do not control
15 .. _image-process-control-id:
17 Image Process Control IDs
23 .. _v4l2-cid-link-freq:
26 The frequency of the data bus (e.g. parallel or CSI-2).
[all …]
|
| D | pixfmt-v4l2.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 Single-planar format structure
13 .. flat-table:: struct v4l2_pix_format
14 :header-rows: 0
15 :stub-columns: 0
18 * - __u32
19 - ``width``
20 - Image width in pixels.
21 * - __u32
22 - ``height``
[all …]
|
| D | ext-ctrls-jpeg.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _jpeg-controls:
15 .. _jpeg-control-id:
27 input image is sampled, in respect to maximum sample rate in each
28 spatial dimension. See :ref:`itu-t81`, clause A.1.1. for more
31 image from RGB to Y'CbCr color space.
35 .. flat-table::
36 :header-rows: 0
37 :stub-columns: 0
39 * - ``V4L2_JPEG_CHROMA_SUBSAMPLING_444``
[all …]
|
| D | pixfmt-intro.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 Standard Image Formats
8 necessary to have standard image data formats which both sides will
11 image data formats in V4L2.
13 V4L2 drivers are not limited to these formats, however. Driver-specific
23 specification would not be complete without well-defined standard
28 bottom. The first byte of data in the image buffer is always for the
40 :ref:`four character (FourCC) codes <v4l2-fourcc>` which are also
46 and are referred to as "multi-planar formats". For example, a
47 :ref:`YUV422 <V4L2-PIX-FMT-YUV422M>` frame is normally stored in one
[all …]
|
| D | dev-meta.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
9 Metadata refers to any non-image data that supplements video frames with
10 additional information. This may include statistics computed over the image,
11 frame capture parameters supplied by the image source or device specific
52 devices can typically also :ref:`capture image data <capture>`. This primarily
60 .. flat-table:: struct v4l2_meta_format
61 :header-rows: 0
62 :stub-columns: 0
65 * - __u32
66 - ``dataformat``
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | st,stm32-dma2d.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/st,stm32-dma2d.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: STMicroelectronics STM32 Chrom-Art Accelerator DMA2D
10 Chrom-ART Accelerator(DMA2D), graphical hardware accelerator
15 - Filling a part or the whole of a destination image with a specific color.
16 - Copying a part or the whole of a source image into a part or the whole of
17 a destination image.
18 - Copying a part or the whole of a source image into a part or the whole of
[all …]
|
| /Documentation/networking/devlink/ |
| D | iosm.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 The ``iosm`` driver implements the following driver-specific parameters.
15 .. list-table:: Driver-specific parameters implemented
18 * - Name
19 - Type
20 - Mode
21 - Description
22 * - ``erase_full_flash``
23 - u8
24 - runtime
[all …]
|
| D | devlink-reload.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 ``devlink-reload`` provides mechanism to reinit driver entities, applying
8 ``devlink-params`` and ``devlink-resources`` new values. It also provides
17 .. list-table:: Possible reload actions
20 * - Name
21 - Description
22 * - ``driver-reinit``
23 - Devlink driver entities re-initialization, including applying
27 * ``devlink-params`` in configuration mode ``driverinit``
28 * ``devlink-resources``
[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/devicetree/bindings/fpga/ |
| D | fpga-region.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/fpga/fpga-region.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Michal Simek <michal.simek@amd.com>
14 - Introduction
15 - Terminology
16 - Sequence
17 - FPGA Region
18 - Supported Use Models
[all …]
|
| /Documentation/arch/arm/ |
| D | arm.rst | 9 ---------------------
21 If you wish to cross-compile, then alter the following lines in the top
36 CROSS_COMPILE=<your-path-to-your-compiler-without-gcc>
40 CROSS_COMPILE=arm-linux-
42 Do a 'make config', followed by 'make Image' to build the kernel
43 (arch/arm/boot/Image). A compressed image can be built by doing a
44 'make zImage' instead of 'make Image'.
48 ---------------
54 Bug reports should be sent to linux-arm-kernel@lists.arm.linux.org.uk,
64 -------------
[all …]
|
| /Documentation/admin-guide/media/ |
| D | ipu3.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Intel Image Processing Unit 3 (IPU3) Imaging Unit (ImgU) driver
14 This file documents the Intel IPU3 (3rd generation Image Processing Unit)
23 frames in a format that is specific to the IPU3 (for consumption by the IPU3
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
[all …]
|
| /Documentation/admin-guide/ |
| D | efi-stub.rst | 6 as a PE/COFF image, thereby convincing EFI firmware loaders to load
8 along with the EFI-specific entry point that the firmware loader
10 arch/x86/boot/header.S and drivers/firmware/efi/libstub/x86-stub.c,
12 arch/arm/boot/compressed/efi-header.S and
13 drivers/firmware/efi/libstub/arm32-stub.c. EFI stub code that is shared
16 For arm64, there is no compressed kernel support, so the Image itself
17 masquerades as a PE/COFF image and the EFI stub is linked into the
19 and drivers/firmware/efi/libstub/arm64-stub.c.
30 --------------------------
38 may not need to be renamed. Similarly for arm64, arch/arm64/boot/Image
[all …]
|
| /Documentation/driver-api/mtd/ |
| D | spi-intel.rst | 2 Upgrading BIOS using spi-intel
6 controller which is used to hold BIOS and other platform specific data.
12 allows upgrading the BIOS image directly from an OS.
14 The spi-intel driver makes it possible to read and write the SPI serial
16 any of them set, the whole MTD device is made read-only to prevent
18 contents as read-only but it can be changed from kernel command line,
21 Please keep in mind that overwriting the BIOS image on SPI serial flash
28 1) Download and extract the latest Minnowboard MAX BIOS SPI image
29 [1]. At the time writing this the latest image is v92.
31 2) Install mtd-utils package [2]. We need this in order to erase the SPI
[all …]
|
| /Documentation/admin-guide/LSM/ |
| D | LoadPin.rst | 5 LoadPin is a Linux Security Module that ensures all kernel-loaded files
7 the expectation that such a filesystem is backed by a read-only device
8 such as dm-verity or CDROM. This allows systems that have a verified
12 The LSM is selectable at build-time with ``CONFIG_SECURITY_LOADPIN``, and
13 can be controlled at boot-time with the kernel command line option
18 block device backing the filesystem is not read-only, a sysctl is
23 It's also possible to exclude specific file types from LoadPin using kernel
26 as "``loadpin.exclude=kernel-module,kexec-image``". This allows to use
28 ``CONFIG_KEXEC_VERIFY_SIG`` to verify kernel module and kernel image while
|
| /Documentation/arch/arm64/ |
| D | booting.rst | 13 (EL0 - EL3), with EL0, EL1 and EL2 having a secure and a non-secure
28 3. Decompress the kernel image
29 4. Call the kernel image
33 ---------------------------
46 -------------------------
50 The device tree blob (dtb) must be placed on an 8-byte boundary and must
53 any 2M region which must be mapped with any specific attributes.
56 the 512 MB region starting at text_offset bytes below the kernel Image.
58 3. Decompress the kernel image
59 ------------------------------
[all …]
|
| /Documentation/driver-api/pm/ |
| D | devices.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 management (PM) code is also driver-specific. Most drivers will do very
22 This writeup gives an overview of how drivers interact with system-wide
25 background for the domain-specific work you'd do with any specific driver.
31 Drivers will use one or both of these models to put devices into low-power
36 Drivers can enter low-power states as part of entering system-wide
37 low-power states like "suspend" (also known as "suspend-to-RAM"), or
39 "suspend-to-disk").
42 by implementing various role-specific suspend and resume methods to
[all …]
|
| /Documentation/power/ |
| D | pci.rst | 11 This document only covers the aspects of power management specific to PCI
13 power management refer to Documentation/driver-api/pm/devices.rst and
27 1.1. Native and Platform-Based Power Management
28 -----------------------------------------------
31 devices into states in which they draw less power (low-power states) at the
34 Usually, a device is put into a low-power state when it is underutilized or
36 again, it has to be put back into the "fully functional" state (full-power
41 PCI devices may be put into low-power states in two ways, by using the device
46 specific value into one of its standard configuration registers. The second
53 to put the device that sent it into the full-power state. However, the PCI Bus
[all …]
|
| /Documentation/userspace-api/ |
| D | dma-buf-alloc-exchange.rst | 1 .. SPDX-License-Identifier: GPL-2.0
2 .. Copyright 2021-2023 Collabora Ltd.
9 support for sharing pixel-buffer allocations between processes, devices, and
12 approach this sharing for two-dimensional image data.
24 image:
25 Conceptually a two-dimensional array of pixels. The pixels may be stored
30 A span along a single y-axis value, e.g. from co-ordinates (0,100) to
37 A span along a single x-axis value, e.g. from co-ordinates (100,0) to
46 A two-dimensional array of some or all of an image's color and alpha
56 of a pixel or an image. The data for one pixel may be spread over several
[all …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | reboot-mode.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/reboot-mode.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andy Yan <andy.yan@rock-chips.com>
18 All mode properties are vendor specific, it is a indication to tell
20 as mode-xxx = <magic> (xxx is mode name, magic should be a non-zero value).
23 - normal: Normal reboot mode, system reboot with command "reboot".
24 - recovery: Android Recovery mode, it is a mode to format the device or update a new image.
25 …- bootloader: Android fastboot mode, it's a mode to re-flash partitions on the Android based devic…
[all …]
|
| /Documentation/doc-guide/ |
| D | sphinx.rst | 12 .. _Sphinx: http://www.sphinx-doc.org/
16 documentation comments, or kernel-doc comments, from source files. Usually these
18 kernel-doc comments have some special structure and formatting, but beyond that
34 :ref:`sphinx-pre-install` for further details.
42 Sphinx inside a virtual environment, using ``virtualenv-3``
56 (sphinx_latest) $ pip install -r Documentation/sphinx/requirements.txt
63 Image output
64 ------------
75 --------------------
86 ------------------------
[all …]
|
123456