Home
last modified time | relevance | path

Searched refs:specific (Results 1 – 200 of 1368) sorted by relevance

1234567

/linux-4.4.14/Documentation/devicetree/bindings/hwlock/
Dhwlock.txt4 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:
Dsirf,hwspinlock.txt10 - #hwlock-cells : hwlock users only use the hwlock id to represent a specific
/linux-4.4.14/Documentation/arm/Samsung/
DOverview.txt23 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
DGPIO.txt8 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-4.4.14/drivers/edac/
Di5000_edac.c465 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 …]
Di7300_edac.c359 const char *specific; in i7300_process_error_global() local
371 specific = GET_ERR_FROM_TABLE(ferr_global_hi_name, errnum); in i7300_process_error_global()
387 specific = GET_ERR_FROM_TABLE(ferr_global_lo_name, errnum); in i7300_process_error_global()
400 is_fatal ? "Fatal" : "NOT fatal", specific); in i7300_process_error_global()
418 const char *specific; in i7300_process_fbd_error() local
430 specific = GET_ERR_FROM_TABLE(ferr_fat_fbd_name, errnum); in i7300_process_fbd_error()
450 bank, ras, cas, errors, specific); in i7300_process_fbd_error()
466 specific = GET_ERR_FROM_TABLE(ferr_nf_fbd_name, errnum); in i7300_process_fbd_error()
496 bank, ras, cas, errors, specific); in i7300_process_fbd_error()
/linux-4.4.14/drivers/bcma/
DREADME2 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
DKconfig6 menu "Broadcom specific AMBA"
13 Bus driver for Broadcom specific Advanced Microcontroller Bus
68 Driver for the Broadcom MIPS core attached to Broadcom specific
88 specific Advanced Microcontroller Bus.
/linux-4.4.14/arch/x86/configs/
Dxen.config1 # global x86 required specific stuff
15 # x86 xen specific config options
22 # x86 specific backend drivers
24 # x86 specific frontend drivers
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dexynos-dw-mshc.txt1 * 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.
Dsamsung-sdhci.txt30 Note: This example shows both SoC specific and board specific properties
32 into SoC specific node and board specific node.
Dk3-dw-mshc.txt1 * Hisilicon specific extensions to the Synopsys Designware Mobile
9 by synopsys-dw-mshc.txt and the properties used by the Hisilicon specific
15 - "hisilicon,hi4511-dw-mshc": for controllers with hi4511 specific extensions.
16 - "hisilicon,hi6220-dw-mshc": for controllers with hi6220 specific extensions.
Dsocfpga-dw-mshc.txt1 * Altera SOCFPGA specific extensions to the Synopsys Designware Mobile
7 by synopsys-dw-mshc.txt and the properties used by the Altera SOCFPGA specific
Dimg-dw-mshc.txt1 * Imagination specific extensions to the Synopsys Designware Mobile Storage
7 by synopsys-dw-mshc.txt and the properties used by the Imagination specific
Dsynopsys-dw-mshc.txt15 # Slots: The slot specific information are contained within child-nodes with
78 * dmas: List of DMA specifiers with the controller specific format as described
91 The MSHC controller node can be split into two portions, SoC specific and
92 board specific portions as listed below.
104 [board specific internal DMA resources]
119 [board specific generic DMA request binding]
Drockchip-dw-mshc.txt1 * Rockchip specific extensions to the Synopsys Designware Mobile
7 by synopsys-dw-mshc.txt and the properties used by the Rockchip specific
/linux-4.4.14/Documentation/sh/
Dnew-machine.txt16 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-4.4.14/Documentation/driver-model/
Ddriver.txt42 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 …]
Dporting.txt20 be embedded in larger, bus-specific objects. Fields in these generic
21 objects can replace fields in the bus-specific objects.
95 - Embed a struct device in the bus-specific device type.
130 the bus. The format of this string is bus-specific. This is
177 device's release method, then free the bus-specific object.
232 - Embed a struct device_driver in the bus-specific driver.
289 forward call to the bus-specific drivers. For instance:
336 bus-specific, so the generic model does attempt to generalize them.
440 fields in the bus-specific representations of these objects. Feel free
441 to remove the bus-specific ones and favor the generic ones. Note
[all …]
Dbus.txt44 them are inherently bus-specific. Drivers typically declare an array
45 of device IDs of devices they support that reside in a bus-specific
51 particular device, without sacrificing bus-specific functionality or
66 lists as they please, but conversion to the bus-specific type may be
Doverview.txt14 bus-specific drivers for bridges and devices by consolidating a set of data
41 and sometimes by the device-specific drivers.
117 A device-specific driver may also export files in its directory to expose
118 device-specific data or tunable interfaces.
/linux-4.4.14/Documentation/devicetree/bindings/clock/ti/
Dinterface.txt19 "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
Dgate.txt21 "ti,dss-gate-clock" - gate clock with DSS specific hardware handling
22 "ti,am35xx-gate-clock" - gate clock with AM35xx specific hardware handling
26 "ti,hsdiv-gate-clock" - gate clock with OMAP36xx specific hardware handling,
/linux-4.4.14/Documentation/hwmon/
Dpmbus-core28 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 …]
Dab850017 See also Documentation/hwmon/abx500. This is the ST-Ericsson AB8500 specific
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dmpic.txt39 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
Dpamu.txt11 First entry is a version-specific string, such as
50 connected to a specific PAMU device should have a "fsl,pamu-phandle" property
51 that links to the corresponding specific child PAMU controller.
80 Phandle to the single, specific PAMU controller node to which
91 the specific LIODN register is located.
Dscfg.txt3 SCFG is the supplemental configuration unit, that provides SoC specific
/linux-4.4.14/Documentation/devicetree/bindings/display/bridge/
Ddw_hdmi.txt4 - compatible: platform specific such as:
13 the clocks are soc specific, the clock-names should be "iahb", "isfr"
14 -port@[X]: SoC specific port nodes with endpoint definitions as defined
16 please refer to the SoC specific binding document:
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dsyscon.txt5 represent as any specific type of device. The typical use-case is for
6 some other node's driver, or platform-specific code, to acquire a
8 using a specific compatible value), interrogate the node (or associated
/linux-4.4.14/Documentation/networking/
Dxfrm_proc.txt25 Transformation protocol specific error
28 Transformation mode specific error
61 Transformation protocol specific error
63 Transformation mode specific error
DLICENSE.qla3xxx5 distributed with QLogic hardware specific firmware binary file.
10 You may redistribute the hardware specific firmware binary file
24 without specific prior written permission
Dnfc.txt77 * NFC_CMD_GET_DEVICE - get specific device info or dump the device list
78 * NFC_CMD_START_POLL - setup a specific device to polling for targets
79 * NFC_CMD_STOP_POLL - stop the polling operation in a specific device
80 * NFC_CMD_GET_TARGET - dump the list of targets found by a specific device
De1000e.txt123 be platform-specific. If CPU utilization is not a concern, use
133 properly tuned for specific network traffic. Increasing this value adds
155 along with RxIntDelay, may improve traffic throughput in specific network
165 efficiency if properly tuned for specific network traffic. If the
178 along with TxIntDelay, may improve traffic throughput in specific
216 recompile. If the driver load fails to enable a specific interrupt mode, the
311 kernel with a supported adapter, email the specific information related
/linux-4.4.14/arch/arm/mach-imx/
DKconfig144 Include support for MX21ADS platform. This includes specific
159 Include support for MX27ADS platform. This includes specific
179 Include support for MX27PDK platform. This includes specific
196 This includes specific configurations for the board and its
216 includes specific configurations for the module and its peripherals.
239 Include support for MX31ADS platform. This includes specific
262 specific configurations for the board and its peripherals.
277 Include support for MX31 LITEKIT platform. This includes specific
295 specific configurations for the board and its peripherals.
324 Include support for MX31PDK (3DS) platform. This includes specific
[all …]
/linux-4.4.14/Documentation/video4linux/
DREADME.davinci-vpbe47 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
Duvcvideo.txt4 This file documents some driver-specific aspects of the UVC driver, such as
5 driver-specific ioctls and implementation notes.
16 The UVC specification allows for vendor-specific extensions through extension
21 - through a driver-specific ioctl interface
27 The second mechanism requires uvcvideo-specific knowledge for the application to
53 3. Driver specific XU control interface
57 access XU controls is provided in the form of a driver-specific ioctl, namely
/linux-4.4.14/Documentation/devicetree/bindings/net/nfc/
Dnfcmrvl.txt9 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-4.4.14/Documentation/mn10300/
Dcompartmentalisation.txt12 Processor-specific header files are divided among directories in a similar
28 Unit-specific header files are divided among directories in a similar way
29 to the CPU level; not only that, but specific sources may also be
60 compilation process; all other unit-specific directories will be ignored.
/linux-4.4.14/Documentation/rapidio/
Dsysfs.txt40 (see 4.1 for switch specific details)
58 Currently Linux RapidIO subsystem does not create any endpoint specific sysfs
60 drivers will add their device-specific sysfs attributes but such attributes are
67 common and device-specific sysfs attributes for switches. Because switches are
69 device-specific sysfs attributes by specifying a callback function that may be
85 4.2 Device-specific Switch Attributes
87 Device-specific switch attributes are listed for each RapidIO switch driver
97 RapidIO bus subdirectory /sys/bus/rapidio implements the following bus-specific
102 process on specific mport device, a user needs to write mport_ID (not
125 following device-specific attributes:
Drapidio.txt17 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 …]
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Datmel-at91.txt12 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:
152 Special Function Registers (SFR) manage specific aspects of the integrated
Dste-u300.txt3 For various board the "board" node may contain specific properties
4 that pertain to this particular board, such as board-specific GPIOs
21 This contains the board-specific information.
Dprimecell.txt9 - compatible : should be a specific name for the peripheral and
10 "arm,primecell". The specific name will match the ARM
17 pclk. Additional clocks are optional and specific to those peripherals.
Dste-nomadik.txt3 For various board the "board" node may contain specific properties
4 that pertain to this particular board, such as board-specific GPIOs.
Dmarvell,kirkwood.txt9 In addition, the above compatible shall be extended with the specific
19 And in addition, the compatible shall be extended with the specific
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Domap-usb.txt7 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-4.4.14/Documentation/devicetree/bindings/clock/
Dlpc1850-ccu.txt23 from the CGU to the specific CCU. See mapping of base clocks
27 from the CGU to the specific CCU. Valid CCU clock names:
36 specific LPC part. Check the user manual for your specific part.
Dalphascale,acc.txt13 It is encouraged to use dt-binding for clock index definitions. SoC specific
21 All clock specific details can be found in the SoC documentation.
Dhi3620-clock.txt10 - "hisilicon,hi3620-mmc-clock" - controller specific for Hi3620 mmc.
Dnvidia,tegra124-car.txt13 the 32 KHz "32k_in", and the board-specific oscillator "osc".
19 (for Tegra124-specific clocks).
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-opal.txt4 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-4.4.14/Documentation/devicetree/bindings/power_supply/ab8500/
Dchargalg.txt7 - battery = Shall be battery specific information
15 For information on battery specific node, Ref:
Dbtemp.txt7 - battery = Shall be battery specific information
15 For information on battery specific node, Ref:
Dcharger.txt5 - battery = Shall be battery specific information
24 For information on battery specific node, Ref:
/linux-4.4.14/Documentation/powerpc/
Dbootwrapper.txt34 cuImages are platform specific. Each specific
37 from the platform specific bd_info file. The platform
38 specific cuImage platform init code can be found in
40 cuImage init code for a specific board can be found in
49 dtbImages have platform specific code for extracting
54 specific initialization code is typically found in a
72 specific initialization code to the start of the bootup
75 is enabled. Platform specific initialization code is
136 middle of the script. This is also the place where platform specific fixups
140 wrapper bits are very board specific and care should be taken to make sure
Ddscr.txt39 CPU specific DSCR default: /sys/devices/system/cpu/cpuN/dscr
42 specific DSCR defaults immediately in their PACA structures. Again if
47 Changing the CPU specific DSCR default value in the sysfs does exactly
/linux-4.4.14/Documentation/arm64/
Dacpi_object_usage.txt283 _BBN 6.5.5 Use as needed; PCI-specific.
332 _DSW 7.2.1 Use as needed; power management specific.
340 _FIX 6.2.7 x86 specific, not used on arm64.
357 _HPP 6.2.8 Optional, PCI specific.
359 _HPX 6.2.9 Optional, PCI specific.
368 _IRC 7.2.15 Use as needed; power management specific.
389 \_SB._OSC), or it may be associated with a specific
393 a device-specific method, the process described for
396 submit the device-specific _OSC usage description as
425 _PRW 7.2.13 Use as needed; power management specific.
[all …]
/linux-4.4.14/Documentation/x86/x86_64/
D00-INDEX4 - AMD64-specific boot options.
10 - Context-specific per-processor interrupt stacks.
Dmachinecheck10 of the banks and subevent is CPU specific.
27 64bit Hex bitmask enabling/disabling specific subevents for bank N
31 Note that BIOS maintain another mask to disable specific events
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Ddma.txt12 specific information. See DMA client binding below for
43 - #dma-cells: Must be at least 1. Used to provide DMA router specific
66 followed by DMA controller specific data.
73 containing DMA controller specific information. This
78 the dmas property. The specific strings that can be used
Dzxdma.txt10 have specific request line
27 Use specific request line passing from dmax
Dk3dma.txt12 have specific request line
30 Use specific request line passing from dmax
Dmmp-dma.txt22 * Each channel has specific irq
64 /* each channel has specific irq */
Dfsl-edma.txt5 specific DMA request source can only be multiplexed by any channel of certain
23 Specific request source can only be multiplexed by specific channels
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dv3-v360epc-pci.txt5 Integrator-specific notes:
11 V360 EPC specific notes:
Dsamsung,exynos5440-pcie.txt15 SoC specific DT Entry:
57 Board specific DT Entry:
Dxgene-pci.txt28 SoC specific DT Entry:
54 Board specific DT Entry:
/linux-4.4.14/drivers/net/ethernet/neterion/
DKconfig15 your specific card in the following questions.
25 More specific information on configuring the driver is in
38 More specific information on configuring the driver is in
/linux-4.4.14/drivers/sn/
DKconfig2 # Miscellaneous SN-specific devices
13 controller card. This option does not enable any specific
/linux-4.4.14/Documentation/virtual/kvm/
D00-INDEX6 - KVM-specific cpuid leaves (x86).
16 - KVM-specific MSRs (x86).
Ds390-diag.txt31 DIAGNOSE function codes not specific to KVM, please refer to the
47 specific value.
/linux-4.4.14/arch/mips/
DKbuild2 # -Werror can be disabled for specific files using:
6 # platform specific definitions
DKbuild.platforms38 # include the platform specific files
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dmarvell,mvebu-pinctrl.txt4 (mpp) to a specific function. For each SoC family there is a SoC specific
12 be used for a specific device or function. Each node requires one or more
Dfsl,imx-pinctrl.txt15 used for a specific device or function. This node represents both mux and config
41 Please refer to each fsl,<soc>-pinctrl,txt binding doc for SoC specific part
48 2. The pin configuration node intends to work on a specific function should
49 to be defined under that specific function node.
Dpinctrl-sirf.txt42 For a specific board, if it wants to use uart2 without hardware flow control,
43 it can add the following to its board-specific .dts file.
Dpinctrl-atlas7.txt97 For a specific board, if it wants to use sd1,
98 it can add the following to its board-specific .dts file.
/linux-4.4.14/Documentation/devicetree/bindings/leds/
Dleds-lp55xx.txt14 Each child has own specific current settings
21 - pwr-sel: LP8501 specific property. Power selection for output channels.
27 Alternatively, each child can have a specific channel name and trigger:
61 9 LED channels with specific name. Internal clock used.
166 9 channels are defined. The 'pwr-sel' is LP8501 specific property.
/linux-4.4.14/Documentation/ABI/testing/
Dconfigfs-usb-gadget47 This group contains subdirectories for language-specific
69 This group contains "Feature Descriptors" specific for one
82 This group contains "Extended Property Descriptors" specific for one
103 This group contains subdirectories for language-specific
Dsysfs-bus-coresight-devices-etb1013 Description: (R) List various control and status registers. The specific
14 layout and content is driver specific.
Dima_policy9 the policy can be constrained based on LSM specific data.
37 lsm: are LSM specific
86 Examples of LSM specific definitions:
Dsysfs-class-led26 scheduler is chosen. Trigger specific parameters can appear in
34 Invert the LED on/off state. This parameter is specific to
Dsysfs-bus-css23 Note: This is an I/O-subchannel specific attribute.
34 Note: This is an I/O-subchannel specific attribute.
Dsysfs-class-led-flash59 has exceeded the limit specific to the flash controller
68 supply has exceeded the limit specific to the flash
73 LED has been below the minimum limit specific to
Dsysfs-memory-page-offline13 The offlining is done in kernel specific granuality.
38 The offlining is done in kernel specific granuality.
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-isku35 capslock key for a specific profile. Profile number is included
45 easyzone keys for a specific profile. Profile number is included
55 function keys for a specific profile. Profile number is included
65 keys for a specific profile. Profile number is included in
75 keys for a specific profile. Profile number is included in
85 thumbster keys for a specific profile. Profile number is included
103 a specific profile. Profile number is included in written data.
114 keystrokes for a specific button for a specific profile.
Dsysfs-driver-hid-roccat-ryos25 a specific profile. Profile index is included in written data.
35 function keys for a specific profile. Profile index is included
45 keys for a specific profile. Profile index is included in
55 thumbster keys for a specific profile. Profile index is included
65 capslock and function keys for a specific profile. Profile index
75 easyzone keys for a specific profile. Profile index is included
96 a specific profile. Profile index is included in written data.
107 keystrokes for a specific button for a specific profile.
/linux-4.4.14/drivers/gpu/drm/rockchip/
DKconfig20 tristate "Rockchip specific extensions for Synopsys DW HDMI"
24 This selects support for Rockchip SoC specific extensions
/linux-4.4.14/Documentation/devicetree/bindings/display/
Dsimple-framebuffer-sunxi.txt1 Sunxi specific Simple Framebuffer bindings
3 This binding documents sunxi specific extensions to the simple-framebuffer
Dmipi-dsi-bus.txt8 This document describes DSI bus-specific properties only or defines existing
37 to define additional, device-specific properties.
/linux-4.4.14/Documentation/usb/
Dgadget-testing.txt30 Function-specific configfs interface
59 Function-specific configfs interface
92 Function-specific configfs interface
125 Function-specific configfs interface
158 Function-specific configfs interface
181 Function-specific configfs interface
227 Function-specific configfs interface
247 Function-specific configfs interface
300 Function-specific configfs interface
383 Function-specific configfs interface
[all …]
Dhotplug.txt17 be driver-specific actions.
78 modules, and can invoke driver-specific setup scripts. The newest ones
92 specific criteria are identified by bits set in "match_flags", paired
105 A short example, for a driver that supports several specific USB devices
/linux-4.4.14/Documentation/i2c/
Dfault-codes25 some positive number indicating a non-fault return. The specific
35 specific to their host bus (such as PCI, or the platform bus).
65 specific fault code when you can.
69 performing an I/O operation. Use a more specific fault
74 specific than ENXIO, implying the problem isn't with the
111 or SMBus (or chip-specific) protocol specifications. One
/linux-4.4.14/Documentation/
Dclk.txt24 The second half of the interface is comprised of the hardware-specific
26 hardware-specific structures needed to model a particular clock. For
28 clk_ops, such as .enable or .set_rate, implies the hardware-specific
31 hardware-specific bits for the hypothetical "foo" hardware.
60 clk_ops pointer in struct clk to perform the hardware-specific parts of
95 which abstract the details of struct clk from the hardware-specific bits, and
106 struct clk_gate contains struct clk_hw hw as well as hardware-specific
163 ... hardware specific data goes here ...
220 Finally, register your clock at run-time with a hardware-specific
Dremoteproc.txt19 platform-specific remoteproc drivers only need to provide a few low-level
92 name of this remote processor, platform-specific ops handlers,
116 This is called by the platform-specific rproc implementation, whenever
128 This function should be called when the platform specific rproc
141 platform specific rproc implementation. This should not be called from a
147 These callbacks should be provided by platform-specific remoteproc
151 * struct rproc_ops - platform-specific device handlers
167 device and boot it (use rproc->priv to access platform-specific private data).
249 of specific remoteproc configuration. Other entries require the host to
282 For more details regarding a specific resource type, please see its
[all …]
DSM501.txt15 drivers which manage the specific hardware blocks. These services
24 peripheral set as platform devices for the specific drivers.
35 the specific set of resources that peripheral requires in order to
Dhwspinlock.txt45 - assign a specific hwspinlock id and return its address, or NULL
47 be calling this function in order to reserve specific hwspinlock
52 - retrieve the global lock id for an OF phandle-based specific lock.
54 to get the global lock id of a specific hwspinlock, so that it can
208 * assign a specific hwspinlock id - this should be called early
242 - to be called from the underlying platform-specific implementation, in
249 - to be called from the underlying vendor-specific implementation, in order
265 * @ops: platform-specific hwspinlock handlers
285 * @priv: private data, owned by the underlying platform-specific hwspinlock drv
/linux-4.4.14/Documentation/fb/
Dinternals.txt20 a specific video mode. This can be obtained using the FBIOGET_FSCREENINFO
26 specific video mode. This can be obtained using the FBIOGET_VSCREENINFO
40 Generic information, API and low level information about a specific frame
Dmetronomefb.txt13 which is then delivered to the AMLCD interface by a host specific method.
16 Metronomefb is platform independent and depends on a board specific driver
/linux-4.4.14/drivers/scsi/device_handler/
DKconfig10 SCSI Device Handlers provide device specific support for
12 select support for specific hardware.
/linux-4.4.14/Documentation/devicetree/bindings/c6x/
Dclocks.txt11 May also have SoC-specific value to support SoC-specific initialization
Dsoc.txt13 - model: specific SoC model
/linux-4.4.14/drivers/scsi/ufs/
DKconfig75 tristate "QCOM specific hooks to UFS controller platform driver"
79 This selects the QCOM specific additions to UFSHCD platform driver.
80 UFS host on QCOM needs some vendor specific configuration before
82 specific registers.
/linux-4.4.14/Documentation/leds/
Dleds-lp55xx.txt45 To support device specific configurations, special structure
50 Chip specific initialization
54 Additional device specific attributes
121 However pattern data is specific.
146 But each device has own specific register addresses for commands.
150 Chip specific commands for loading and updating program memory.
/linux-4.4.14/Documentation/dmaengine/
Dclient.txt15 2. Set slave and controller specific parameters
24 controller only and even in some cases a specific channel is desired.
35 slave and cyclic channels as they typically need to obtain a specific
48 2. Set slave and controller specific parameters
50 Next step is always to pass some specific information to the DMA
58 specific structure. That gives flexibility to client to pass more
193 completion of a specific DMA transaction.
/linux-4.4.14/drivers/misc/lis3lv02d/
DKconfig19 will be called lis3lv02d and a specific module for the SPI transport
36 will be called lis3lv02d and a specific module for the I2C transport
/linux-4.4.14/Documentation/scsi/
Dhpsa.txt37 HPSA specific entries in /sys
43 HPSA specific host attributes:
81 HPSA specific disk attributes:
99 HPSA specific ioctls:
113 hpsa specific host "rescan" attribute.
/linux-4.4.14/Documentation/s390/
Dcds.txt34 some of them are ESA/390 platform specific.
75 routine determines the interrupt status and calls the device specific
83 describes the input to the device specific interrupt handler.
93 Linux/390 common device support (CDS) provides to allow for device specific
96 implementation to allow to drive a specific hardware device on the ESA/390
97 platform. Some of the interface routines are specific to Linux/390 and some
100 can be found in the architecture specific C header file
106 interrupt lines managed by a specific interrupt controller and bus systems
138 imply specific I/O commands (channel command words - CCWs) in order to operate
148 ccw_device_start() interface that takes a device specific channel program (one
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-dsp-keystone.txt10 Keystone 2 DSP GPIO controller has specific features:
19 access device state control registers and the offset of device's specific
/linux-4.4.14/Documentation/devicetree/bindings/board/
Dfsl-board.txt25 - compatible: should be a board-specific string followed by a string
87 - compatible: Should be a board-specific string followed by a string
103 - compatible: Should be a board-specific string like "fsl,<board>-cpld"
/linux-4.4.14/Documentation/sound/alsa/soc/
Dmachine.txt9 The machine driver can contain codec and platform specific code. It registers
40 probe/remove are optional. Do any machine specific probe here.
93 Machine specific audio mixer controls can be added in the DAI init function.
Doverview.txt17 machine specific code to re-route audio, enable amps, etc., after such an
49 * Machine specific controls: Allow machines to add controls to the sound card
67 "sound card device". It handles any machine specific controls and
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-class-tpm5 Description: The device/ directory under a specific TPM instance exposes
27 TPM vendor specific cancel operation.
44 is manufacturer specific.
50 Description: The "durations" property shows the 3 vendor-specific values
168 from a temp_deactivated state is platform specific.
174 Description: The "timeouts" property shows the 4 vendor-specific values
Dsyscalls8 that Linux supports. Please see the architecture-specific
/linux-4.4.14/drivers/staging/olpc_dcon/
DKconfig23 communicates with the DCON using model-specific code. If you
33 communicates with the DCON using model-specific code. If you
/linux-4.4.14/Documentation/backlight/
Dlp855x-driver.txt33 For supporting platform specific data, the lp855x platform data can be used.
38 * period_ns : Platform specific PWM period value. unit is nano.
/linux-4.4.14/Documentation/devicetree/bindings/input/
Dbrcm,bcm-keypad.txt69 /* Required SoC specific properties */
72 /* Required Board specific properties */
102 /* Optional board specific properties */
/linux-4.4.14/Documentation/virtual/kvm/devices/
DREADME1 This directory contains specific device bindings for KVM_CAP_DEVICE_CTRL.
/linux-4.4.14/drivers/net/ethernet/dlink/
DKconfig15 your specific card in the following questions.
41 More specific information and updates are available from
/linux-4.4.14/Documentation/devicetree/bindings/bus/
Dsimple-pm-bus.txt20 vendor-specific compatible values.
24 Optional platform-specific properties for clock or PM domain control (at least
Drenesas,bsc.txt19 - compatible: Must contain an SoC-specific value, and "renesas,bsc" and
21 SoC-specific values can be:
/linux-4.4.14/include/asm-generic/
Dspinlock.h8 #error need an architecture specific asm/spinlock.h
Dpgalloc.h7 #error need to implement an architecture specific asm/pgalloc.h
Dtlbflush.h9 #error need to implement an architecture specific asm/tlbflush.h
/linux-4.4.14/Documentation/fmc/
Dfmc-chardev.txt10 identifiers nor bus_id, a more specific fmc-0400 if the device has a
11 bus-specific address but no associated name, or something like
46 is not specific to FMC at all, it just uses lseek, read and write.
Dcarrier.txt88 * device_id: a slot-specific unique integer number.
183 parameters (in a carrier-specific way) the file loaded will match
192 Interrupt management is carrier-specific, so it is abstracted as
197 but fmc-specific flags may be added in the future. You'll most
216 same address space is carrier-specific and should only be used
228 configuration of specific signals within the carrier needs at least
229 some knowledge of the carrier itself. For this reason, the specific
230 driver can request to configure carrier-specific GPIO pins, numbered
256 If, however, your GPIO pin has a specific known role, you can pass a
281 the order used by the specific carrier driver in assigning leds and
Dmezzanine.txt4 An FMC driver is concerned with the specific mezzanine and associated
24 In even more special cases, the driver may access carrier-specific
32 expected to be performed by the driver. If you depend on specific
82 The parameters are carrier-specific, in that they rely on the busid
92 This is an array of integers, listing carrier-specific
/linux-4.4.14/Documentation/networking/dsa/
Ddsa.txt34 using upstream and downstream Ethernet links between switches. These specific
44 which is a hardware feature making the switch insert a specific tag for each
45 Ethernet frames it received to/from specific ports to help the management
50 - how to send CPU originated traffic to specific ports
78 The exact format of the tag protocol is vendor specific, but in general, they
89 know whether DSA is enabled (e.g.: to enable/disable specific offload features),
101 switch specific tagging protocol. DSA accomplishes this by registering a
102 specific (and fake) Ethernet type (later becoming skb->protocol) with the
128 -> invoke switch tag specific protocol handler in
149 to/from specific switch ports
[all …]
Dbcm_sf2.txt20 The switch also supports specific congestion control features which allow MoCA
44 The SF2 switch is configured to enable a Broadcom specific 4-bytes switch tag
56 The DSA platform device driver is probed using a specific compatible string
81 MoCA interfaces are fairly specific and require the use of a firmware blob which
/linux-4.4.14/Documentation/devicetree/bindings/media/
Ds5p-mfc.txt35 SoC specific DT entry:
46 Board specific DT entry:
Dgpio-ir-receiver.txt8 - linux,rc-map-name: Linux specific remote control map name.
Dsamsung-mipi-csis.txt13 - bus-width : maximum number of data lanes supported (SoC specific);
31 media/video-interfaces.txt. The following are properties specific to those nodes.
Dsh_mobile_ceu.txt1 Bindings, specific for the sh_mobile_ceu_camera.c driver:
/linux-4.4.14/Documentation/block/
Dswitching-sched.txt19 set a specific device to use the deadline or noop schedulers - which
22 To set a specific scheduler, simply do this:
Dcapability.txt5 capability is a hex word indicating which capabilities a specific disk
Dnull_blk.txt52 2: Timer: Waits a specific period (completion_nsec) for each IO before
66 III: Multi-queue specific parameters
/linux-4.4.14/net/dccp/ccids/
DKconfig6 Enable CCID-2 specific debugging messages.
42 Enable CCID-3 specific debugging messages.
/linux-4.4.14/Documentation/arm/
DPorting119 by the architecture specific code later in the code (via the
126 Machine specific fixups, run before memory subsystems have been
130 Machine specific function to map IO areas (including the debug
134 Machine specific function to initialise interrupts.
DInterrupts5 major architecture-specific subsystems.
101 "simple", or your own specific handler if you need to do something special.
116 to be useful only to machine specific code. The last is recommended to
117 only be used by machine specific code, but may be used in drivers if
149 parent IRQ via the correct chip specific function. For instance, if
DREADME63 arch-* machine/platform specific header files
64 hardware driver-internal ARM specific data structures/definitions
65 mach descriptions of generic ARM to specific machine interfaces
75 machine-specific parts by directory. For this, the machine category is
181 specific supporting code.
186 machine specific "personality."
Dfirmware.txt1 Interface for registering and calling firmware-specific operations for ARM.
66 /* Call Exynos specific smc call */
/linux-4.4.14/Documentation/devicetree/bindings/rtc/
Dpxa-rtc.txt3 PXA specific RTC driver.
Disil,isl12057.txt8 ("wakeup-source") to handle the specific use-case found
14 get access to the 'wakealarm' sysfs entry, this specific property can
/linux-4.4.14/Documentation/arm/SPEAr/
Doverview.txt54 mach-spear13xx/spear13xx.c. mach-spear* also contain soc/machine specific
56 spear600.c. mach-spear* doesn't contains board specific files as they fully
/linux-4.4.14/Documentation/devicetree/bindings/misc/
Dsram.txt15 child node should use a 'reg' property to specify a specific range of
34 - compatible : standard definition, should contain a vendor specific string
/linux-4.4.14/drivers/staging/emxx_udc/
DTODO2 * break out board-specific VBUS GPIO to work with multiplatform
/linux-4.4.14/Documentation/w1/
D00-INDEX4 - Drivers that provide support for specific family codes.
/linux-4.4.14/arch/arm/mach-vexpress/
Ddcscb_setup.S33 2: @ Implementation-specific local CPU setup operations should go here,
/linux-4.4.14/Documentation/security/
DLSM.txt16 specific changes to system operation when these tweaks are not available
19 Without a specific LSM built into the kernel, the default LSM will be the
/linux-4.4.14/arch/arm64/
DKconfig.debug12 who are working in architecture specific areas of the kernel.
23 access to this is obviously disastrous, but specific access can
51 of TEXT_OFFSET and platforms must not require a specific
/linux-4.4.14/arch/arm/mach-mmp/
DKconfig119 Select code specific to PXA168
125 Select code specific to PXA910
131 Select code specific to MMP2. MMP2 is ARMv7 compatible.
/linux-4.4.14/Documentation/watchdog/
Dconvert_drivers_to_kernel_api.txt18 go. Only very few driver-specific details have to be moved to other functions.
22 close preparations) can simply go. Device specific stuff needs to go to the
23 driver specific start-function. Note that for some drivers, the start-function
83 Check the functions for device-specific stuff and keep it for later
121 here simply happens the direct hardware access. If you have device-specific
/linux-4.4.14/Documentation/devicetree/bindings/display/exynos/
Dexynos5433-decon.txt34 SoC specific DT entry:
61 Board specific DT entry:
Dexynos7-decon.txt45 SoC specific DT entry:
62 Board specific DT entry:
Dsamsung-fimd.txt77 in [2]. The following are properties specific to those nodes:
90 SoC specific DT entry:
104 Board specific DT entry:
/linux-4.4.14/drivers/staging/iio/Documentation/
Dring.txt5 specific information on a given buffer implementation, see the
17 These are used to perform device specific steps on either side
/linux-4.4.14/drivers/soc/
DKconfig1 menu "SOC (System On Chip) specific Drivers"
/linux-4.4.14/Documentation/timers/
Dtimers-howto.txt64 will obviously depend on your specific situation, but
92 delay / performance for your specific code path. Exact
93 tolerances here are very situation specific, thus it
/linux-4.4.14/Documentation/arm/nwfpe/
DREADME18 contain all operating system specific code in one module (fpmodule.*).
19 All the other files contain emulator specific code. This should allow
43 which instruction contains the bug. Small programs illustrating a specific
/linux-4.4.14/drivers/usb/mon/
DKconfig9 between peripheral-specific drivers and HC drivers will be built.
/linux-4.4.14/Documentation/device-mapper/
Dswitch.txt6 paths. The path used for any specific region can be switched
85 The block device that represents a specific path to the device.
88 The offset of the start of data on the specific <dev_path> (in units
90 forwarding the request to the specific path. Typically it is zero.
Ddm-uevent.txt29 Value: Device-mapper specific action that caused the uevent action.
36 Description: A sequence number for this specific device-mapper device.
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dbrcm,brcmnand.txt15 - compatible : May contain an SoC-specific compatibility string (see below)
16 to account for any SoC-specific hardware bits that may be
53 -- Additonal SoC-specific NAND controller properties --
66 - compatible: Can be one of several SoC-specific strings. Each SoC may have
/linux-4.4.14/tools/perf/
Ddesign.txt40 * specific (raw) counter configuration data, if unset, the next
80 machine-specific.
118 More hw_event_types are supported as well, but they are CPU-specific
234 counter to be specific to a task:
239 pid > 0: the counter is attached to a specific task (if the current task
244 The 'cpu' parameter allows a counter to be made specific to a CPU:
246 cpu >= 0: the counter is restricted to a specific CPU
327 NOTE: the hw-counter userspace bits are arch specific and are currently only
395 NOTE: PERF_RECORD_CALLCHAIN is arch specific and currently only implemented
/linux-4.4.14/Documentation/kbuild/
Dmakefiles.txt38 --- 6.5 Architecture-specific boot images
76 architecture-specific information to the top Makefile.
234 combined in a built-in.o for that specific directory.
370 Another example are the architecture-specific Makefiles which
453 as-instr checks if the assembler reports a specific instruction
520 cc-version is useful when a specific $(CC) version is faulty in one
551 One typical use-case is when a specific GCC version is broken.
552 cc-fullversion points out a more specific version than cc-version does.
561 In this example for a specific GCC version the build will error out
671 When compiling host programs, it is possible to set specific flags.
[all …]
/linux-4.4.14/drivers/net/ethernet/natsemi/
DKconfig14 you will be asked for your specific card in the following questions.
45 More specific information and updates are available from
/linux-4.4.14/Documentation/extcon/
Dporting-android-switch-class59 extcon_get_state(edev) if you intend to get a state of a specific
62 4. Use extcon_update_state() if you are updating specific bits of
86 (a) for a specific cable or (b) for every cable.
/linux-4.4.14/scripts/
Dchecksyscalls.sh102 /* i386-specific or historical system calls */
/linux-4.4.14/Documentation/gpio/
Dgpio-legacy.txt50 On a given board each GPIO is used for one specific purpose like monitoring
60 is not the main issue; GPIOs are often used for the kind of board-specific
63 functionality can be very portable. Other features are platform-specific,
98 for the GPIO lines so that board-specific setup code directly corresponds
101 board-specific pin configuration data (along with other board specific
121 Whether a platform supports multiple GPIO controllers is a platform-specific
186 Platform-specific implementations are encouraged to optimize the two
402 devices, by the board-specific initialization code. Note that IRQ trigger
487 this is highly chip-specific and nonportable. One platform might not need
499 platform-specific issue, as are models like (not) having a one-to-one
[all …]
/linux-4.4.14/drivers/net/ethernet/intel/
DKconfig14 your specific card in the following questions.
38 More specific information on configuring the driver is in
59 More specific information on configuring the driver is in
104 More specific information on configuring the driver is in
145 More specific information on configuring the driver is in
167 More specific information on configuring the driver is in
246 More specific information on configuring the driver is in
/linux-4.4.14/Documentation/devicetree/bindings/timer/
Dstericsson-u300-apptimer.txt9 adopted for EPOC/Symbian with two specific IRQs for these tasks,
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DCPUfreq.txt13 There are two forms of the driver depending on the specific CPU and
24 The code core manages the CPU specific drivers, any data that they
/linux-4.4.14/Documentation/wimax/
DREADME.i2400m88 generic driver and the bus-specific drivers. The bus generic driver
90 use to connect to the device. The bus specific drivers are just the
98 bus-specific driver. The reason for this breakup is to be able to
160 bus-specific i2400m-usb or i2400m-sdio controls).
226 packets in the sense of the device-specific protocol for communication
242 (bus specific) reset on the device.
/linux-4.4.14/Documentation/scheduler/
D00-INDEX4 - CPU Scheduler implementation hints for architecture specific code.
/linux-4.4.14/Documentation/thermal/
Dcpu-cooling-api.txt107 implementation specific processor support and characterisation
148 Circuit implementation specific factors include the chosen silicon
164 However, since both implementation specific and complex relationships
186 The platform specific callback can then use any combination of tables
190 specific.
/linux-4.4.14/Documentation/power/
Dpower_supply_class.txt15 power supply, specific monitoring hardware may not be able to provide them
25 AC/USB power supply online status. (Note that specific details of the
27 user and/or specific machine defaults, per design principles of LED
190 Q: I have some very specific attribute (e.g. battery color), should I add
204 directly measurable by the specific hardware available.
/linux-4.4.14/drivers/net/ethernet/cisco/
DKconfig15 your specific card in the following questions.
/linux-4.4.14/drivers/net/ethernet/emulex/
DKconfig15 your specific card in the following questions.
/linux-4.4.14/drivers/memstick/
DKconfig11 to the specific driver for your MemoryStick interface.
/linux-4.4.14/drivers/net/ethernet/stmicro/
DKconfig15 be asked for your specific card in the following questions.
/linux-4.4.14/Documentation/devicetree/bindings/extcon/
Dextcon-arizona.txt6 This document lists Extcon specific bindings, see the primary binding document:
/linux-4.4.14/drivers/staging/vt6656/
DTODO8 - abstract VT3184 chipset specific code
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Darizona-regulator.txt6 This document lists regulator specific bindings, see the primary binding
/linux-4.4.14/Documentation/vm/
Dhwpoison.txt83 arg1: PR_MCE_KILL_SET: arg2 defines thread specific mode
157 Architecture specific MCE injector
171 Test suite (hwpoison specific portable tests in tsrc)
174 x86 specific injector
/linux-4.4.14/drivers/net/ethernet/oki-semi/
DKconfig15 be asked for your specific card in the following questions.
/linux-4.4.14/arch/powerpc/boot/dts/
Do2i.dts26 /* o2i specific partitions */
Do2mnt.dts26 /* add o2mnt specific partitions */
/linux-4.4.14/drivers/net/ethernet/aurora/
DKconfig10 for your specific device in the following questions.
/linux-4.4.14/drivers/staging/vt6655/
DTODO8 - abstract VT3253 chipset specific code
/linux-4.4.14/drivers/net/irda/
DKconfig207 specification, and therefore needs its own specific driver. This
221 specification, and therefore needs its own specific driver. This
235 specification, and therefore needs its own specific driver. This
269 own specific driver. Those dongles support SIR and FIR (4Mbps)
361 to plug a specific 5 pins FIR IrDA dongle in the specific
377 This driver relies on platform specific helper routines so
391 own specific driver. Those dongles support SIR and FIR (4Mbps)
/linux-4.4.14/sound/sh/
DKconfig8 Support for sound devices specific to SUPERH architectures.
/linux-4.4.14/drivers/net/ethernet/brocade/
DKconfig15 asked for your specific card in the following questions.
/linux-4.4.14/drivers/net/ethernet/dec/
DKconfig15 your specific card in the following questions.
/linux-4.4.14/Documentation/devicetree/bindings/net/can/
Dsun4i_can.txt30 Board specific .dts file:
/linux-4.4.14/drivers/net/ethernet/tehuti/
DKconfig15 your specific card in the following questions.
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dmeson-dwmac.txt13 another one for the Amlogic specific configuration
Dmicrel-ksz90x1.txt5 micrel-specific properties to an Ethernet OF device node.
7 Note that these settings are applied after any phy-specific fixup from
/linux-4.4.14/Documentation/cgroups/
Dnet_prio.txt12 2) The priority of application traffic is often a site-specific administrative
25 Each net_prio cgroup contains two files that are subsystem specific
/linux-4.4.14/Documentation/fpga/
Dfpga-mgr.txt11 The FPGA image data itself is very manufacturer specific, but for our purposes
48 To register or unregister the low level FPGA-specific driver:
151 The ops will implement whatever device specific register writes are needed to

1234567