Home
last modified time | relevance | path

Searched +full:configuration +full:- +full:space (Results 1 – 25 of 1118) sorted by relevance

12345678910>>...45

/kernel/linux/linux-6.6/include/linux/
Drio_drv.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
46 * rio_local_read_config_32 - Read 32 bits from local configuration space
48 * @offset: Offset into local configuration space
52 * device's configuration space.
61 * rio_local_write_config_32 - Write 32 bits to local configuration space
63 * @offset: Offset into local configuration space
67 * device's configuration space.
76 * rio_local_read_config_16 - Read 16 bits from local configuration space
78 * @offset: Offset into local configuration space
82 * device's configuration space.
[all …]
/kernel/linux/linux-5.10/include/linux/
Drio_drv.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
46 * rio_local_read_config_32 - Read 32 bits from local configuration space
48 * @offset: Offset into local configuration space
52 * device's configuration space.
61 * rio_local_write_config_32 - Write 32 bits to local configuration space
63 * @offset: Offset into local configuration space
67 * device's configuration space.
76 * rio_local_read_config_16 - Read 16 bits from local configuration space
78 * @offset: Offset into local configuration space
82 * device's configuration space.
[all …]
/kernel/linux/linux-6.6/drivers/rapidio/
Drio-access.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * RapidIO configuration space access support
15 * Wrappers for all RIO configuration access functions. They just check
16 * alignment and call the low-level functions pointed to by rio_mport->ops.
24 * RIO_LOP_READ - Generate rio_local_read_config_* functions
25 * @size: Size of configuration space read (8, 16, 32 bits)
27 * @len: Length of configuration space read (1, 2, 4 bytes)
30 * configuration space registers on the local device.
39 res = mport->ops->lcread(mport, mport->id, offset, len, &data); \
45 * RIO_LOP_WRITE - Generate rio_local_write_config_* functions
[all …]
/kernel/linux/linux-5.10/drivers/rapidio/
Drio-access.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * RapidIO configuration space access support
15 * Wrappers for all RIO configuration access functions. They just check
16 * alignment and call the low-level functions pointed to by rio_mport->ops.
24 * RIO_LOP_READ - Generate rio_local_read_config_* functions
25 * @size: Size of configuration space read (8, 16, 32 bits)
27 * @len: Length of configuration space read (1, 2, 4 bytes)
30 * configuration space registers on the local device.
39 res = mport->ops->lcread(mport, mport->id, offset, len, &data); \
45 * RIO_LOP_WRITE - Generate rio_local_write_config_* functions
[all …]
/kernel/linux/linux-6.6/arch/arm/mach-pxa/
Dsmemc.h1 /* SPDX-License-Identifier: GPL-2.0-only */
15 #define MDCNFG (SMEMC_VIRT + 0x00) /* SDRAM Configuration Register 0 */
20 #define MECR (SMEMC_VIRT + 0x14) /* Expansion Memory (PCMCIA/Compact Flash) Bus Configuration */
21 #define SXLCR (SMEMC_VIRT + 0x18) /* LCR value to be written to SDRAM-Timing Synchronous Flash */
24 #define MCMEM0 (SMEMC_VIRT + 0x28) /* Card interface Common Memory Space Socket 0 Timing */
25 #define MCMEM1 (SMEMC_VIRT + 0x2C) /* Card interface Common Memory Space Socket 1 Timing */
26 …ine MCATT0 (SMEMC_VIRT + 0x30) /* Card interface Attribute Space Socket 0 Timing Configuration */
27 …ine MCATT1 (SMEMC_VIRT + 0x34) /* Card interface Attribute Space Socket 1 Timing Configuration */
28 #define MCIO0 (SMEMC_VIRT + 0x38) /* Card interface I/O Space Socket 0 Timing Configuration */
29 #define MCIO1 (SMEMC_VIRT + 0x3C) /* Card interface I/O Space Socket 1 Timing Configuration */
[all …]
/kernel/linux/linux-5.10/arch/arm/mach-pxa/include/mach/
Dsmemc.h1 /* SPDX-License-Identifier: GPL-2.0-only */
15 #define MDCNFG (SMEMC_VIRT + 0x00) /* SDRAM Configuration Register 0 */
20 #define MECR (SMEMC_VIRT + 0x14) /* Expansion Memory (PCMCIA/Compact Flash) Bus Configuration */
21 #define SXLCR (SMEMC_VIRT + 0x18) /* LCR value to be written to SDRAM-Timing Synchronous Flash */
24 #define MCMEM0 (SMEMC_VIRT + 0x28) /* Card interface Common Memory Space Socket 0 Timing */
25 #define MCMEM1 (SMEMC_VIRT + 0x2C) /* Card interface Common Memory Space Socket 1 Timing */
26 …ine MCATT0 (SMEMC_VIRT + 0x30) /* Card interface Attribute Space Socket 0 Timing Configuration */
27 …ine MCATT1 (SMEMC_VIRT + 0x34) /* Card interface Attribute Space Socket 1 Timing Configuration */
28 #define MCIO0 (SMEMC_VIRT + 0x38) /* Card interface I/O Space Socket 0 Timing Configuration */
29 #define MCIO1 (SMEMC_VIRT + 0x3C) /* Card interface I/O Space Socket 1 Timing Configuration */
[all …]
/kernel/linux/linux-6.6/drivers/pci/
Dpci-bridge-emul.h1 /* SPDX-License-Identifier: GPL-2.0 */
7 /* PCI configuration space of a PCI-to-PCI bridge. */
42 /* PCI configuration space of the PCIe capabilities */
78 * configuration space. Return PCI_BRIDGE_EMUL_HANDLED when the
82 * in-memory copy of the configuration space.
88 * Same as ->read_base(), except it is for reading from the
89 * PCIe capability configuration space.
95 * Same as ->read_base(), except it is for reading from the
96 * PCIe extended capability configuration space.
102 * Called when writing to the regular PCI bridge configuration
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pci/
Ddesignware-pcie.txt4 - compatible:
5 "snps,dw-pcie" for RC mode;
6 "snps,dw-pcie-ep" for EP mode;
7 - reg: For designware cores version < 4.80 contains the configuration
8 address space. For designware core version >= 4.80, contains
9 the configuration and ATU address space
10 - reg-names: Must be "config" for the PCIe configuration space and "atu" for
11 the ATU address space.
12 (The old way of getting the configuration address space from "ranges"
15 - #address-cells: set to <3>
[all …]
/kernel/linux/linux-5.10/drivers/pci/
Dpci-bridge-emul.h1 /* SPDX-License-Identifier: GPL-2.0 */
7 /* PCI configuration space of a PCI-to-PCI bridge. */
42 /* PCI configuration space of the PCIe capabilities */
78 * configuration space. Return PCI_BRIDGE_EMUL_HANDLED when the
82 * in-memory copy of the configuration space.
88 * Same as ->read_base(), except it is for reading from the
89 * PCIe capability configuration space.
94 * Called when writing to the regular PCI bridge configuration
95 * space. old is the current value, new is the new value being
103 * Same as ->write_base(), except it is for writing from the
[all …]
/kernel/liteos_a/kernel/common/
Dlos_config.h2 * Copyright (c) 2013-2019 Huawei Technologies Co., Ltd. All rights reserved.
3 * Copyright (c) 2020-2022 Huawei Device Co., Ltd. All rights reserved.
33 * @defgroup los_config System configuration items
64 /****************************** System clock module configuration ****************************/
131 * External configuration item for timer tailoring
136 /****************************** Hardware interrupt module configuration ***************************…
139 * Configuration item for hardware interrupt tailoring
165 /****************************** Task module configuration ********************************/
235 * Configuration item for task (stack) monitoring module tailoring
241 /****************************** Semaphore module configuration ******************************/
[all …]
/kernel/linux/linux-5.10/Documentation/PCI/
Dacpi-info.rst1 .. SPDX-License-Identifier: GPL-2.0
12 method for accessing PCI config space below it, the address space windows
33 reserving address space. The static tables are for things the OS needs to
39 If the OS is expected to manage a non-discoverable device described via
45 describe all the address space they consume.  This includes all the windows
50 These are all device-specific, non-architected things, so the only way a
52 the device-specific details.  The host bridge registers also include ECAM
53 space, since it is consumed by the host bridge.
58 spec defines Consumer/Producer only for the Extended Address Space
60 Address Space descriptors. Consequently, OSes have to assume all
[all …]
/kernel/linux/linux-6.6/Documentation/PCI/
Dacpi-info.rst1 .. SPDX-License-Identifier: GPL-2.0
12 method for accessing PCI config space below it, the address space windows
33 reserving address space. The static tables are for things the OS needs to
39 If the OS is expected to manage a non-discoverable device described via
45 describe all the address space they consume. This includes all the windows
50 These are all device-specific, non-architected things, so the only way a
52 the device-specific details. The host bridge registers also include ECAM
53 space, since it is consumed by the host bridge.
58 spec defines Consumer/Producer only for the Extended Address Space
60 Address Space descriptors. Consequently, OSes have to assume all
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/powerpc/fsl/
Ddcsr.txt17 debug blocks defined within this memory space.
21 - compatible
24 Definition: Must include "fsl,dcsr" and "simple-bus".
25 The DCSR space exists in the memory-mapped bus.
27 - #address-cells
33 - #size-cells
40 - ranges
42 Value type: <prop-encoded-array>
44 range of the DCSR space.
48 #address-cells = <1>;
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/fsl/
Ddcsr.txt17 debug blocks defined within this memory space.
21 - compatible
24 Definition: Must include "fsl,dcsr" and "simple-bus".
25 The DCSR space exists in the memory-mapped bus.
27 - #address-cells
33 - #size-cells
40 - ranges
42 Value type: <prop-encoded-array>
44 range of the DCSR space.
48 #address-cells = <1>;
[all …]
/kernel/linux/linux-6.6/include/uapi/linux/
Dvduse.h1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
23 * struct vduse_dev_config - basic configuration of a VDUSE device
31 * @config_size: the size of the configuration space
32 * @config: the buffer of the configuration space
61 * struct vduse_iotlb_entry - entry of IOTLB to describe one IOVA region [start, last]
81 * and return the corresponding file descriptor. Return -EINVAL means the
94 * struct vduse_config_data - data used to update configuration space
95 * @offset: the offset from the beginning of configuration space
96 * @length: the length to write to configuration space
100 * configuration space.
[all …]
/kernel/linux/linux-5.10/drivers/media/platform/atmel/
Datmel-isc-regs.h1 /* SPDX-License-Identifier: GPL-2.0 */
21 /* ISC Parallel Front End Configuration 0 Register */
43 /* ISC Parallel Front End Configuration 1 Register */
51 /* ISC Parallel Front End Configuration 2 Register */
71 /* ISC Clock Configuration Register */
96 /* ISC White Balance Configuration Register */
114 /* ISC Color Filter Array Configuration Register */
156 /* Color Space Conversion Control Register */
159 /* Color Space Conversion YR YG Register */
162 /* Color Space Conversion YB OY Register */
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/pci/
Dsnps,dw-pcie.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
16 # Please create a separate DT-schema for your DWC PCIe Root Port controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie
23 - compatible
[all …]
Dsnps,dw-pcie-common.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
22 DWC PCIe CSR space is normally accessed over the dedicated Data Bus
23 Interface - DBI. In accordance with the reference manual the register
24 configuration space belongs to the Configuration-Dependent Module (CDM)
25 and is split up into several sub-parts Standard PCIe configuration
[all …]
/kernel/linux/linux-6.6/Documentation/usb/
Dfunctionfs.rst6 unique behaviour. It may be added to an USB configuration only after
7 the user space driver has registered by writing descriptors and
8 strings (the user space program has to provide the same information
10 the configuration).
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
28 numbers and changing of the configuration (which means that
30 configuration changes to (say) endpoint 2)). "ep0" is used
42 where the last two are implemented via FunctionFS. On user space
46 $ mkdir /dev/ffs-mtp && mount -t functionfs mtp /dev/ffs-mtp
[all …]
/kernel/linux/linux-5.10/Documentation/usb/
Dfunctionfs.rst6 unique behaviour. It may be added to an USB configuration only after
7 the user space driver has registered by writing descriptors and
8 strings (the user space program has to provide the same information
10 the configuration).
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
28 numbers and changing of the configuration (which means that
30 configuration changes to (say) endpoint 2)). "ep0" is used
42 where the last two are implemented via FunctionFS. On user space
46 $ mkdir /dev/ffs-mtp && mount -t functionfs mtp /dev/ffs-mtp
[all …]
/kernel/linux/linux-5.10/Documentation/userspace-api/media/mediactl/
Drequest-api.rst1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
4 .. _media-request-api:
12 the same pipeline to reconfigure and collaborate closely on a per-frame basis.
14 to specific frames (aka 'per-frame controls') in order to be used efficiently.
16 While the initial use-case was V4L2, it can be extended to other subsystems
20 it is, it is terribly inefficient: user-space would have to flush all activity
22 be processed with that configuration, and wait until they are all available for
26 The Request API allows a specific configuration of the pipeline (media
27 controller topology + configuration for each media entity) to be associated with
28 specific buffers. This allows user-space to schedule several tasks ("requests")
[all …]
/kernel/linux/linux-6.6/Documentation/userspace-api/media/mediactl/
Drequest-api.rst1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
4 .. _media-request-api:
12 the same pipeline to reconfigure and collaborate closely on a per-frame basis.
14 to specific frames (aka 'per-frame controls') in order to be used efficiently.
16 While the initial use-case was V4L2, it can be extended to other subsystems
20 it is, it is terribly inefficient: user-space would have to flush all activity
22 be processed with that configuration, and wait until they are all available for
26 The Request API allows a specific configuration of the pipeline (media
27 controller topology + configuration for each media entity) to be associated with
28 specific buffers. This allows user-space to schedule several tasks ("requests")
[all …]
/kernel/linux/linux-5.10/include/misc/
Docxl.h1 // SPDX-License-Identifier: GPL-2.0+
10 * device configuration space, adding a Process Element to the Shared
14 * reuse common code. A bit like a in-kernel library.
32 u8 pp_mmio_bar; /* per-process MMIO area */
52 OCXL_BIG_ENDIAN = 0, /**< AFU data is big-endian */
53 OCXL_LITTLE_ENDIAN = 1, /**< AFU data is little-endian */
65 * ocxl_function_open() - Open an OpenCAPI function on an OpenCAPI device
73 * ocxl_function_afu_list() - Get the list of AFUs associated with a PCI function device
81 * ocxl_function_fetch_afu() - Fetch an AFU instance from an OpenCAPI function
92 * ocxl_afu_get() - Take a reference to an AFU
[all …]
/kernel/linux/linux-6.6/include/misc/
Docxl.h1 // SPDX-License-Identifier: GPL-2.0+
10 * device configuration space, adding a Process Element to the Shared
14 * reuse common code. A bit like a in-kernel library.
32 u8 pp_mmio_bar; /* per-process MMIO area */
52 OCXL_BIG_ENDIAN = 0, /**< AFU data is big-endian */
53 OCXL_LITTLE_ENDIAN = 1, /**< AFU data is little-endian */
65 * ocxl_function_open() - Open an OpenCAPI function on an OpenCAPI device
73 * ocxl_function_afu_list() - Get the list of AFUs associated with a PCI function device
81 * ocxl_function_fetch_afu() - Fetch an AFU instance from an OpenCAPI function
92 * ocxl_afu_get() - Take a reference to an AFU
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/rapidio/
Drapidio.rst5 The RapidIO standard is a packet-based fabric interconnect standard designed for
8 is publicly available for download from the RTA web-site [1].
17 into the kernel similarly to other buses by defining RapidIO-specific device and
21 architecture-specific interfaces that provide support for common RapidIO
33 ---------------
50 ----------
54 structure. Devices form one global device list and per-network device lists
58 ----------
68 specific switch drivers that are designed to provide hardware-specific
72 -----------
[all …]

12345678910>>...45