| /linux-6.1.9/drivers/ufs/host/ |
| D | Kconfig | 45 This selects the Cadence-specific additions to UFSHCD platform driver.
58 tristate "QCOM specific hooks to UFS controller platform driver"
63 This selects the QCOM specific additions to UFSHCD platform driver.
64 UFS host on QCOM needs some vendor specific configuration before
66 specific registers.
72 tristate "Mediatek specific hooks to UFS controller platform driver"
77 This selects the Mediatek specific additions to UFSHCD platform driver.
78 UFS host on Mediatek needs some vendor specific configuration before
80 specific registers.
87 tristate "Hisilicon specific hooks to UFS controller platform driver"
[all …]
|
| /linux-6.1.9/Documentation/devicetree/bindings/hwlock/ |
| D | hwlock.txt | 4 Generic bindings that are common to all the hwlock platform specific driver
7 Please also look through the individual platform specific hwlock binding
8 documentations for identifying any additional properties specific to that
16 specific lock.
21 Consumers that require specific hwlock(s) should specify them using the
34 use the hwlock-names to match and get a specific hwlock.
37 1. Example of a node using a single specific hwlock:
49 2. Example of a node using multiple specific hwlocks:
|
| /linux-6.1.9/Documentation/arm/samsung/ |
| D | overview.rst | 24 deals with the architecture and drivers specific to these devices.
27 on the implementation details and specific support.
37 - S5PC110 specific default configuration
39 - S5PV210 specific default configuration
46 several platform directories and then the machine specific directories
51 specific information. It contains the base clock, GPIO and device definitions
54 plat-s3c24xx is for s3c24xx specific builds, see the S3C24XX docs.
56 plat-s5p is for s5p specific builds, and contains common support for the
57 S5P specific systems. Not all S5Ps use all the features in this directory
|
| D | gpio.rst | 9 specific calls provided alongside the drivers/gpio core.
24 specific calls for the items that require Samsung specific handling, such
33 Pin configuration is specific to the Samsung architecture, with each SoC
|
| /linux-6.1.9/drivers/gpu/drm/rockchip/ |
| D | Kconfig | 38 bool "Rockchip specific extensions for Analogix DP driver"
43 This selects support for Rockchip SoC specific extensions
53 This selects support for Rockchip SoC specific extensions
59 bool "Rockchip specific extensions for Synopsys DW HDMI"
61 This selects support for Rockchip SoC specific extensions
67 bool "Rockchip specific extensions for Synopsys DW MIPI DSI"
70 This selects support for Rockchip SoC specific extensions
76 bool "Rockchip specific extensions for Innosilicon HDMI"
78 This selects support for Rockchip SoC specific extensions
103 bool "Rockchip specific extensions for RK3066 HDMI"
[all …]
|
| /linux-6.1.9/lib/crypto/ |
| D | Kconfig | 17 Declares whether the architecture provides an arch-specific
26 fallback, e.g., for SIMD implementations. If no arch specific
33 Declares whether the architecture provides an arch-specific
43 fallback, e.g., for SIMD implementations. If no arch specific
53 by either the generic implementation or an arch-specific one, if one
59 Declares whether the architecture provides an arch-specific
68 fallback, e.g., for SIMD implementations. If no arch specific
79 fulfilled by either the generic implementation or an arch-specific
95 Declares whether the architecture provides an arch-specific
104 fallback, e.g., for SIMD implementations. If no arch specific
[all …]
|
| /linux-6.1.9/drivers/edac/ |
| D | i5000_edac.c | 465 char *specific = NULL; in i5000_process_fatal_error_info() local
494 specific = "Alert on non-redundant retry or fast " in i5000_process_fatal_error_info()
498 specific = "Northbound CRC error on non-redundant " in i5000_process_fatal_error_info()
516 specific = ">Tmid Thermal event with intelligent " in i5000_process_fatal_error_info()
525 bank, ras, cas, allErrors, specific); in i5000_process_fatal_error_info()
546 char *specific = NULL; in i5000_process_nonfatal_error_info() local
588 specific = "Non-Aliased Uncorrectable Patrol Data ECC"; in i5000_process_nonfatal_error_info()
591 specific = "Non-Aliased Uncorrectable Spare-Copy " in i5000_process_nonfatal_error_info()
595 specific = "Non-Aliased Uncorrectable Mirrored Demand " in i5000_process_nonfatal_error_info()
599 specific = "Non-Aliased Uncorrectable Non-Mirrored " in i5000_process_nonfatal_error_info()
[all …]
|
| /linux-6.1.9/Documentation/sh/ |
| D | new-machine.rst | 18 of the board-specific code (with the exception of stboards) ended up
19 in arch/sh/kernel/ directly, with board-specific headers ending up in
24 Board-specific code::
31 | | `-- board-specific files
33 | | `-- board-specific files
40 | `-- board-specific headers
42 | `-- board-specific headers
54 `-- cchip-specific files
57 board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the
58 hd64461-specific headers.
[all …]
|
| /linux-6.1.9/drivers/bcma/ |
| D | README | 2 however from programming point of view there is nothing AMBA specific we use.
4 Standard AMBA drivers are platform specific, have hardcoded addresses and use
8 1) Broadcom specific AMBA device. It is put on AMBA bus, but can not be treated
12 devices is used for managing Broadcom specific core.
18 16 devices identified by Broadcom specific fields: manufacturer, id, revision
|
| /linux-6.1.9/arch/x86/configs/ |
| D | xen.config | 1 # global x86 required specific stuff
15 # x86 xen specific config options
21 # x86 specific backend drivers
23 # x86 specific frontend drivers
|
| /linux-6.1.9/Documentation/driver-api/ |
| D | vfio-pci-device-specific-driver-acceptance.rst | 3 Acceptance criteria for vfio-pci device specific driver variants
11 vfio-pci driver does include some device specific support, further
12 extensions for yet more advanced device specific features are not
15 requiring device specific knowledge, ex. saving and loading device
18 In support of such features, it's expected that some device specific
29 documentation for reviewers to understand the device specific
|
| /linux-6.1.9/Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 9 IP block-specific DT compatible strings are contained within the HDL,
26 match on these IP block-specific compatible strings.
29 continue to specify an SoC-specific compatible string value, such as
30 "sifive,fu540-c000-uart". This way, if SoC-specific
31 integration-specific bug fixes or workarounds are needed, the kernel
33 IP block-specific compatible string (such as "sifive,uart0") should
|
| /linux-6.1.9/Documentation/devicetree/bindings/mmc/ |
| D | k3-dw-mshc.txt | 1 * Hisilicon specific extensions to the Synopsys Designware Mobile
9 by synopsys-dw-mshc.txt and the properties used by the Hisilicon specific
15 - "hisilicon,hi3660-dw-mshc": for controllers with hi3660 specific extensions.
17 with hi3670 specific extensions.
18 - "hisilicon,hi4511-dw-mshc": for controllers with hi4511 specific extensions.
19 - "hisilicon,hi6220-dw-mshc": for controllers with hi6220 specific extensions.
|
| D | bluefield-dw-mshc.txt | 1 * Mellanox Bluefield SoC specific extensions to the Synopsys Designware
10 specific extensions to the Synopsys Designware Mobile Storage Host Controller.
16 specific extensions.
|
| /linux-6.1.9/Documentation/networking/devlink/ |
| D | octeontx2.rst | 13 The ``octeontx2 PF and VF`` drivers implement the following driver-specific parameters.
15 .. list-table:: Driver-specific parameters implemented
29 The ``octeontx2 AF`` driver implements the following driver-specific parameters.
31 .. list-table:: Driver-specific parameters implemented
|
| D | netdevsim.rst | 20 The ``netdevsim`` driver also implements the following driver-specific
23 .. list-table:: Driver-specific parameters implemented
33 - Test parameter used to show how a driver-specific devlink parameter
86 Driver-specific Traps
89 .. list-table:: List of Driver-specific Traps Registered by ``netdevsim``
|
| D | devlink-dpipe.rst | 46 modeled as a graph of match/action tables. Each table represents a specific
75 the actual content of a specific table.
77 The hardware pipeline is not port specific, but rather describes the whole
85 is hardware counting for a specific table.
111 and specific ASIC metadata. The protocol headers should be declared in the
112 ``devlink`` core API. On the other hand ASIC meta data is driver specific
113 and should be defined in the driver. Additionally, each driver-specific
114 devlink documentation file should document the driver-specific ``dpipe``
130 * ``field_exact``: Exact match on a specific field.
131 * ``field_exact_mask``: Exact match on a specific field after masking.
[all …]
|
| /linux-6.1.9/Documentation/driver-api/usb/ |
| D | typec_bus.rst | 10 The communication is SVID (Standard or Vendor ID) specific, i.e. specific for
29 specific commands from the alternate mode drivers to the partner, and from the
30 partners to the alternate mode drivers. No direct SVID specific communication is
47 will be used to deliver all the SVID specific commands from the partner to the
49 the SVID specific commands to each other using :c:func:`typec_altmode_vdm()`.
51 If the communication with the partner using the SVID specific commands results
54 passes the negotiated SVID specific pin configuration value to the function as
58 NOTE: The SVID specific pin configuration values must always start from
67 An example of working definitions for SVID specific pin configurations would
|
| /linux-6.1.9/Documentation/admin-guide/media/ |
| D | davinci-vpbe.rst | 29 board specific settings (specified in board-xxx-evm.c). This allows
32 API to set timings in VENC for a specific display resolution. As of this
41 is connected, the timings for a specific standard/preset is retrieved from
42 the board specific table and the values are used to set the timings in
48 add the available outputs as a board specific entry (i.e add the "LogicPD"
50 supported can be maintained in the board specific setup file to support
57 OSD module implements all OSD layer management and hardware specific
|
| /linux-6.1.9/Documentation/devicetree/bindings/clock/ti/ |
| D | interface.txt | 19 "ti,omap3-hsotgusb-interface-clock" - interface clock with USB specific HW
21 "ti,omap3-dss-interface-clock" - interface clock with DSS specific HW handling
22 "ti,omap3-ssi-interface-clock" - interface clock with SSI specific HW handling
23 "ti,am35xx-interface-clock" - interface clock with AM35xx specific HW handling
24 "ti,omap2430-interface-clock" - interface clock with OMAP2430 specific HW
|
| /linux-6.1.9/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-tx.rst | 27 step are driver-specific.
107 useconds. Step and range are driver-specific.
111 are driver-specific.
121 range and step are driver-specific.
125 value. The range and step are driver-specific.
129 value. The range and step are driver-specific.
133 useconds value. The range and step are driver-specific.
140 range and step are driver-specific.
144 step are driver-specific.
173 dBuV. Range and step are driver-specific.
[all …]
|
| /linux-6.1.9/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpic.txt | 39 specifiers do not contain the interrupt-type or type-specific
110 type-specific cell is undefined. The
123 the error interrupt. The type-specific
124 cell identifies the specific error
130 the MPIC IPI number. The type-specific
136 the MPIC timer number. The type-specific
139 <4th-cell> type-specific information
141 The type-specific cell is encoded as follows:
144 the type-specific cell contains the
223 * SoC interrupt number is 16 and the specific error
|
| /linux-6.1.9/Documentation/hwmon/ |
| D | pmbus-core.rst | 29 device specific extensions in addition to the core PMBus driver, since it is
30 simply unknown what new device specific functionality PMBus device developers
33 To make device specific extensions as scalable as possible, and to avoid having
35 split into core, generic, and device specific code. The core code (in
37 provides support for generic PMBus devices. Device specific code is responsible
38 for device specific initialization and, if needed, maps device specific
52 For this reason, it often makes sense to provide a device specific driver if not
65 The API between core and device specific PMBus code is defined in
84 than 0xff). Support for virtual PMBus commands is device specific and thus has
85 to be implemented in device specific code.
[all …]
|
| /linux-6.1.9/Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 17 into the kernel similarly to other buses by defining RapidIO-specific device and
21 architecture-specific interfaces that provide support for common RapidIO
38 by a rio_mport data structure. This structure contains master port specific
43 RapidIO master ports are serviced by subsystem specific mport device drivers
46 includes rio_ops data structure which contains pointers to hardware specific
64 data structure, which contains switch specific information such as copy of the
65 routing table and pointers to switch specific functions.
68 specific switch drivers that are designed to provide hardware-specific
83 RapidIO device-specific drivers follow Linux Kernel Driver Model and are
84 intended to support specific RapidIO devices attached to the RapidIO network.
[all …]
|
| D | mport_cdev.rst | 43 - Configure/Map mport's outbound requests window(s) for specific size,
46 - Configure/Map mport's inbound requests window(s) for specific size,
68 At this moment the most common limitation is availability of RapidIO-specific
69 DMA engine framework for specific mport device. Users should verify available
75 specific DMA engine support and therefore DMA data transfers mport_cdev driver
89 bit masks that correspond to the specific functional blocks.
109 - Add memory mapped DMA data transfers as an option when RapidIO-specific DMA
|