| /linux/drivers/ufs/host/ |
| H A D | Kconfig | 45 This selects the Cadence-specific additions to UFSHCD platform driver.
58 tristate "QCOM specific hooks to UFS controller platform driver"
64 This selects the QCOM specific additions to UFSHCD platform driver.
65 UFS host on QCOM needs some vendor specific configuration before
67 specific registers.
73 tristate "Mediatek specific hooks to UFS controller platform driver"
79 This selects the Mediatek specific additions to UFSHCD platform driver.
80 UFS host on Mediatek needs some vendor specific configuration before
82 specific registers.
89 tristate "Hisilicon specific hooks to UFS controller platform driver"
[all …]
|
| /linux/Documentation/devicetree/bindings/hwlock/ |
| H A 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/Documentation/arch/sh/ |
| H A 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/drivers/bcma/ |
| H A 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
|
| H A D | Kconfig | 8 tristate "Broadcom specific AMBA"
11 Bus driver for Broadcom specific Advanced Microcontroller Bus
67 Driver for the Broadcom MIPS core attached to Broadcom specific
84 driver that implements ChipCommon specific interface communication.
98 specific Advanced Microcontroller Bus.
|
| /linux/arch/x86/configs/ |
| H A D | xen.config | 1 # global x86 required specific stuff
13 # x86 xen specific config options
18 # x86 specific backend drivers
20 # x86 specific frontend drivers
|
| /linux/Documentation/arch/arm/samsung/ |
| H A D | overview.rst | 26 - S5PC110 specific default configuration
28 - S5PV210 specific default configuration
35 several platform directories and then the machine specific directories
40 specific information. It contains the base clock, GPIO and device definitions
43 plat-s5p is for s5p specific builds, and contains common support for the
44 S5P specific systems. Not all S5Ps use all the features in this directory
|
| H A D | gpio.rst | 9 specific calls provided alongside the drivers/gpio core.
16 specific calls for the items that require Samsung specific handling, such
25 Pin configuration is specific to the Samsung architecture, with each SoC
|
| /linux/Documentation/driver-api/ |
| H A 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/Documentation/devicetree/bindings/sifive/ |
| H A 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/Documentation/devicetree/bindings/mmc/ |
| H A 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.
|
| H A 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/Documentation/driver-api/usb/ |
| H A 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/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-fm-tx.rst | 28 step are driver-specific.
108 microseconds. Step and range are driver-specific.
112 are driver-specific.
122 range and step are driver-specific.
126 value. The range and step are driver-specific.
130 value. The range and step are driver-specific.
134 microseconds value. The range and step are driver-specific.
141 range and step are driver-specific.
145 step are driver-specific.
167 dBuV. Range and step are driver-specific.
[all …]
|
| /linux/Documentation/networking/devlink/ |
| H A 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 …]
|
| H A 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``
|
| H A D | mlxsw.rst | 20 The ``mlxsw`` driver also implements the following driver-specific
23 .. list-table:: Driver-specific parameters implemented
85 Driver-specific Traps
88 .. list-table:: List of Driver-specific Traps Registered by ``mlxsw``
|
| /linux/Documentation/driver-api/rapidio/ |
| H A 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 …]
|
| H A 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
|
| /linux/Documentation/devicetree/bindings/usb/ |
| H A D | omap-usb.txt | 7 multipoint. This is a MUSB configuration-specific setting.
9 MUSB configuration-specific setting. Should be set to "16"
11 - interface-type : This is a board specific setting to describe the type of
27 SOC specific device node entry
39 Board specific device node entry
|
| /linux/drivers/net/ethernet/wangxun/ |
| H A D | Kconfig | 15 be asked for your specific card in the following questions.
37 More specific information on configuring the driver is in
61 More specific information on configuring the driver is in
79 More specific information on configuring the driver is in
95 More specific information on configuring the driver is in
|
| /linux/Documentation/driver-api/driver-model/ |
| H A D | driver.rst | 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
85 no bus-specific fields (i.e. don't have a bus-specific driver
89 Most drivers, however, will have a bus-specific structure and will
105 define generic callbacks that forward the call to the bus-specific
[all …]
|
| /linux/Documentation/driver-api/pldmfw/ |
| H A D | driver-ops.rst | 4 Driver-specific callbacks
8 specific behavior using the following operations.
25 The ``.send_package_data`` operation is used to send the device-specific
55 order to allow the device driver to perform any remaining device specific
|
| /linux/Documentation/devicetree/bindings/i2c/ |
| H A D | i2c-opal.txt | 4 Most of the device node and properties layout is specific to the firmware and
12 - ibm,opal-id: Refers to a specific bus and used to identify it when calling
22 and depend on the specific hardware implementation. The example below depicts
|
| /linux/Documentation/usb/ |
| H A D | functionfs-desc.rst | 20 most recent interface descriptor determines what type of class-specific
26 Class-specific descriptors are accepted only for the class/subclass of the
28 class-specific descriptors that are supported.
|