| /Linux-v4.19/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-v4.19/Documentation/arm/Samsung/ |
| D | Overview.txt | 23 deals with the architecture and drivers specific to these devices.
26 on the implementation details and specific support.
35 s5pc110_defconfig - S5PC110 specific default configuration
36 s5pv210_defconfig - S5PV210 specific default configuration
43 several platform directories and then the machine specific directories
48 specific information. It contains the base clock, GPIO and device definitions
51 plat-s3c24xx is for s3c24xx specific builds, see the S3C24XX docs.
53 plat-s5p is for s5p specific builds, and contains common support for the
54 S5P specific systems. Not all S5Ps use all the features in this directory
|
| D | GPIO.txt | 8 specific calls provided alongside the drivers/gpio core.
23 specific calls for the items that require Samsung specific handling, such
32 Pin configuration is specific to the Samsung architecture, with each SoC
|
| /Linux-v4.19/drivers/gpu/drm/rockchip/ |
| D | Kconfig | 22 bool "Rockchip specific extensions for Analogix DP driver"
24 This selects support for Rockchip SoC specific extensions
32 This selects support for Rockchip SoC specific extensions
38 bool "Rockchip specific extensions for Synopsys DW HDMI"
40 This selects support for Rockchip SoC specific extensions
46 bool "Rockchip specific extensions for Synopsys DW MIPI DSI"
48 This selects support for Rockchip SoC specific extensions
54 bool "Rockchip specific extensions for Innosilicon HDMI"
56 This selects support for Rockchip SoC specific extensions
|
| /Linux-v4.19/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-v4.19/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-v4.19/arch/x86/configs/ |
| D | xen.config | 1 # global x86 required specific stuff
15 # x86 xen specific config options
22 # x86 specific backend drivers
24 # x86 specific frontend drivers
|
| /Linux-v4.19/Documentation/devicetree/bindings/mmc/ |
| D | exynos-dw-mshc.txt | 1 * Samsung Exynos specific extensions to the Synopsys Designware Mobile
7 by synopsys-dw-mshc.txt and the properties used by the Samsung Exynos specific
14 specific extensions.
16 specific extensions.
18 specific extensions.
20 specific extensions.
22 specific extensions.
24 specific extensions having an SMU.
69 The MSHC controller node can be split into two portions, SoC specific and
70 board specific portions as listed below.
|
| D | samsung-sdhci.txt | 30 Note: This example shows both SoC specific and board specific properties
32 into SoC specific node and board specific node.
|
| 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.
16 - "hisilicon,hi4511-dw-mshc": for controllers with hi4511 specific extensions.
17 - "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-v4.19/Documentation/sh/ |
| D | new-machine.txt | 16 of the board-specific code (with the exception of stboards) ended up
17 in arch/sh/kernel/ directly, with board-specific headers ending up in
22 Board-specific code:
29 | | `-- board-specific files
31 | | `-- board-specific files
38 | `-- board-specific headers
40 | `-- board-specific headers
51 `-- cchip-specific files
54 board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the
55 hd64461-specific headers.
[all …]
|
| /Linux-v4.19/Documentation/driver-model/ |
| D | driver.txt | 42 model because the bus they belong to has a bus-specific structure with
43 bus-specific fields that cannot be generalized.
48 completely bus-specific. Defining them as bus-specific entities would
49 sacrifice type-safety, so we keep bus-specific structures around.
51 Bus-specific drivers should include a generic struct device_driver in
52 the definition of the bus-specific driver. Like this:
59 A definition that included bus-specific fields would look like
83 no bus-specific fields (i.e. don't have a bus-specific driver
87 Most drivers, however, will have a bus-specific structure and will
103 define generic callbacks that forward the call to the bus-specific
[all …]
|
| /Linux-v4.19/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-v4.19/Documentation/hwmon/ |
| D | pmbus-core | 28 device specific extensions in addition to the core PMBus driver, since it is
29 simply unknown what new device specific functionality PMBus device developers
32 To make device specific extensions as scalable as possible, and to avoid having
34 split into core, generic, and device specific code. The core code (in
36 provides support for generic PMBus devices. Device specific code is responsible
37 for device specific initialization and, if needed, maps device specific
51 For this reason, it often makes sense to provide a device specific driver if not
64 The API between core and device specific PMBus code is defined in
83 than 0xff). Support for virtual PMBus commands is device specific and thus has
84 to be implemented in device specific code.
[all …]
|
| /Linux-v4.19/Documentation/devicetree/bindings/arm/ |
| D | atmel-at91.txt | 12 the specific SoC family or compatible:
16 o "atmel,at91sam9x5" for the 5 series, shall be extended with the specific
28 * "atmel,sama5" for SoCs using a Cortex-A5, shall be extended with the specific
30 o "atmel,sama5d2" shall be extended with the specific SoC compatible:
32 o "atmel,sama5d3" shall be extended with the specific SoC compatible:
38 o "atmel,sama5d4" shall be extended with the specific SoC compatible:
44 * "atmel,samv7" for MCUs using a Cortex-M7, shall be extended with the specific
46 o "atmel,sams70" shall be extended with the specific MCU compatible:
56 o "atmel,samv70" shall be extended with the specific MCU compatible:
63 o "atmel,samv71" shall be extended with the specific MCU compatible:
[all …]
|
| /Linux-v4.19/arch/arm/mach-imx/ |
| D | Kconfig | 91 Include support for MX21ADS platform. This includes specific
106 Include support for MX27ADS platform. This includes specific
126 Include support for MX27PDK platform. This includes specific
143 This includes specific configurations for the board and its
163 includes specific configurations for the module and its peripherals.
186 Include support for MX31ADS platform. This includes specific
209 specific configurations for the board and its peripherals.
224 Include support for MX31 LITEKIT platform. This includes specific
242 specific configurations for the board and its peripherals.
271 Include support for MX31PDK (3DS) platform. This includes specific
[all …]
|
| /Linux-v4.19/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_vmd()`.
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
60 NOTE: The SVID specific pin configuration values must always start from
69 An example of working definitions for SVID specific pin configurations would
|
| /Linux-v4.19/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-v4.19/Documentation/media/v4l-drivers/ |
| D | davinci-vpbe.rst | 47 board specific settings (specified in board-xxx-evm.c). This allows
50 API to set timings in VENC for a specific display resolution. As of this
58 is connected, the timings for a specific standard/preset is retrieved from
59 the board specific table and the values are used to set the timings in
65 add the available outputs as a board specific entry (i.e add the "LogicPD"
67 supported can be maintained in the board specific setup file to support
73 OSD module implements all OSD layer management and hardware specific
|
| /Linux-v4.19/Documentation/devicetree/bindings/net/nfc/ |
| D | nfcmrvl.txt | 9 Optional SoC specific properties:
15 Optional UART-based chip specific properties:
17 - break-control: Specifies that the chip needs specific break management.
19 Optional I2C-based chip specific properties:
|
| /Linux-v4.19/drivers/pci/controller/dwc/ |
| D | Kconfig | 34 host-specific features PCI_DRA7XX_HOST must be selected and in order
35 to enable device-specific features PCI_DRA7XX_EP must be selected.
49 host-specific features PCI_DRA7XX_HOST must be selected and in order
50 to enable device-specific features PCI_DRA7XX_EP must be selected.
66 host-specific features PCIE_DW_PLAT_HOST must be selected and in
67 order to enable device-specific features PCI_DW_PLAT_EP must be
81 host-specific features PCIE_DW_PLAT_HOST must be selected and in
82 order to enable device-specific features PCI_DW_PLAT_EP must be
142 PCIe controller uses the DesignWare core plus Qualcomm-specific
|
| /Linux-v4.19/Documentation/networking/ |
| D | xfrm_proc.txt | 27 Transformation protocol specific error
30 Transformation mode specific error
67 Transformation protocol specific error
69 Transformation mode specific error
|
| /Linux-v4.19/Documentation/rapidio/ |
| D | rapidio.txt | 17 into the kernel similarly to other buses by defining RapidIO-specific device and
21 architecture-specific interfaces that provide support for common RapidIO
37 by a rio_mport data structure. This structure contains master port specific
42 RapidIO master ports are serviced by subsystem specific mport device drivers
45 includes rio_ops data structure which contains pointers to hardware specific
61 data structure, which contains switch specific information such as copy of the
62 routing table and pointers to switch specific functions.
65 specific switch drivers that are designed to provide hardware-specific
78 RapidIO device-specific drivers follow Linux Kernel Driver Model and are
79 intended to support specific RapidIO devices attached to the RapidIO network.
[all …]
|
| D | mport_cdev.txt | 47 - Configure/Map mport's outbound requests window(s) for specific size,
50 - Configure/Map mport's inbound requests window(s) for specific size,
71 At this moment the most common limitation is availability of RapidIO-specific
72 DMA engine framework for specific mport device. Users should verify available
78 specific DMA engine support and therefore DMA data transfers mport_cdev driver
89 bit masks that correspond to the specific functional blocks.
106 - Add memory mapped DMA data transfers as an option when RapidIO-specific DMA
|
