| /Documentation/devicetree/bindings/arm/ |
| D | arm,embedded-trace-extension.yaml | 18 The trace generated by the ETE could be stored via legacy CoreSight
21 legacy CoreSight components, a node must be listed per instance, along
41 Output connections from the ETE to legacy CoreSight trace bus.
45 description: Output connection from the ETE to legacy CoreSight Trace bus.
56 # An ETE node without legacy CoreSight connections
62 # An ETE node with legacy CoreSight connections
68 out-ports { /* legacy coresight connection */
|
| /Documentation/networking/devlink/ |
| D | devlink-eswitch-attr.rst | 7 Devlink E-Switch supports two modes of operation: legacy and switchdev.
8 Legacy mode operates based on traditional MAC/VLAN steering rules. Switching
38 * ``legacy`` operates based on traditional MAC/VLAN steering
46 matching and steering. Support for both switchdev mode and legacy mode.
55 and legacy mode. The mode can be one of the following:
75 # enable encap-mode with legacy mode
76 $ devlink dev eswitch set pci/0000:08:00.0 mode legacy inline-mode none encap-mode basic
|
| /Documentation/leds/ |
| D | well-known-leds.txt | 13 Legacy names are listed, too; in case you are writing application that
15 but then try the legacy ones, too.
38 Legacy: "shift-key-light" (Motorola Droid 4, capslock)
42 Legacy: "tpacpi::thinklight" (IBM/Lenovo Thinkpads)
43 Legacy: "lp5523:kb{1,2,3,4,5,6}" (Nokia N900)
47 Legacy: "button-backlight" (Motorola Droid 4)
62 Legacy: "status-led:{red,green,blue}" (Motorola Droid 4)
63 Legacy: "lp5523:{r,g,b}" (Nokia N900)
|
| /Documentation/gpu/ |
| D | vgaarbiter.rst | 6 modern devices allow relocation of such ranges, some "Legacy" VGA devices
10 Section 7, Legacy Devices.
13 the legacy VGA arbitration task (besides other bus management tasks) when more
14 than one legacy device co-exists on the same machine. But the problem happens
28 legacy instructions. Devices which do not want/need to use the arbiter may
71 set the legacy decoding attributes for the card
127 resources as locked. If the resources requested are "normal" (and not legacy)
128 resources, the arbiter will first check whether the card is doing legacy
130 legacy resource lock. The arbiter will first look for all VGA cards that
157 Indicates to the arbiter if the card decodes legacy VGA IOs, legacy VGA
[all …]
|
| /Documentation/PCI/ |
| D | boot-interrupts.rst | 14 given Core IO converts the legacy interrupt messages from PCI Express to
16 IO-APIC table entries), the messages are routed to the legacy PCH. This
20 protocol describes this in-band legacy wire-interrupt INTx mechanism for
29 When in-band legacy INTx messages are forwarded to the PCH, they in turn
74 The legacy interrupt forwarding mechanism exists today in a number of
104 Intel® Quick Data DMA/PCI Express ports are not routed to legacy
113 disabled, the Linux kernel will reroute the valid interrupt to its legacy
127 There is an overview of the legacy interrupt handling in several datasheets
147 2.15.2 PCI Express Legacy INTx Support and Boot Interrupt
151 If you have any legacy PCI interrupt questions that aren't answered, email me.
|
| D | sysfs-pci.rst | 98 Accessing legacy resources through sysfs
101 Legacy I/O port and ISA memory resources are also provided in sysfs if the
112 do legacy port I/O. The application should open the file, seek to the desired
117 to access legacy memory space.
136 Legacy resources are protected by the HAVE_PCI_LEGACY define. Platforms
137 wishing to support legacy functionality should define it and provide
|
| /Documentation/userspace-api/media/dvb/ |
| D | frontend_legacy_api.rst | 5 Frontend Legacy Data Types
20 Frontend Legacy Function Calls
38 fe-dishnetwork-send-legacy-cmd
|
| D | fe-dishnetwork-send-legacy-cmd.rst | 35 This is a very obscure legacy command, used only at stv0299
39 frontend, for Dish Network legacy switches.
42 dishes were already legacy in 2004.
|
| D | frontend_legacy_dvbv3_api.rst | 6 Digital TV Frontend legacy API (a. k. a. DVBv3)
11 incomplete information. This is kept only to support legacy
|
| /Documentation/netlink/ |
| D | genetlink-legacy.yaml | 4 $id: http://kernel.org/schemas/netlink/genetlink-legacy.yaml#
36 enum: [ genetlink, genetlink-c, genetlink-legacy ] # Trim
57 # Start genetlink-legacy
67 # End genetlink-legacy
121 # Start genetlink-legacy
151 # End genetlink-legacy
266 # Start genetlink-legacy
270 # End genetlink-legacy
323 # Start genetlink-legacy
330 # End genetlink-legacy
[all …]
|
| D | netlink-raw.yaml | 57 # Start genetlink-legacy
63 # End genetlink-legacy
117 # Start genetlink-legacy
172 # End genetlink-legacy
285 # Start genetlink-legacy
289 # End genetlink-legacy
390 # Start genetlink-legacy
397 # End genetlink-legacy
430 # Start genetlink-legacy
432 # End genetlink-legacy
[all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | rockchip-dw-pcie.yaml | 44 legacy-interrupt-controller:
45 description: Interrupt controller node for handling legacy PCI interrupts.
59 - description: combined legacy interrupt
106 interrupt-names = "sys", "pmc", "msg", "legacy", "err";
121 legacy-interrupt-controller {
|
| D | xlnx,nwl-pcie.yaml | 36 - description: interrupt asserted when a legacy interrupt is received
82 legacy-interrupt-controller:
83 description: Interrupt controller node for handling legacy PCI interrupts.
150 pcie_intc: legacy-interrupt-controller {
|
| /Documentation/PCI/endpoint/ |
| D | pci-test-function.rst | 44 Bit 0 raise legacy IRQ
82 This register contains the interrupt type (Legacy/MSI) triggered
83 for the READ/WRITE/COPY and raise IRQ (Legacy/MSI) commands.
88 Legacy 0
100 Legacy 0
|
| /Documentation/arch/sh/ |
| D | booting.rst | 7 address of the device tree blob in r4. Since legacy bootloaders did not
10 select a legacy board option (something other than CONFIG_SH_DEVICE_TREE)
|
| /Documentation/misc-devices/ |
| D | pci-endpoint-test.rst | 16 #) raise legacy IRQ
34 Tests legacy IRQ
43 should be passed as argument (0: Legacy, 1:MSI, 2:MSI-X).
|
| /Documentation/arch/x86/ |
| D | usb-legacy-support.rst | 5 USB Legacy support
42 in the kernel config or USB Legacy support in the BIOS. A BIOS update
48 Legacy support in the BIOS. If this alone doesn't help, try also adding
|
| /Documentation/networking/ |
| D | sriov.rst | 11 Legacy API
18 Since the legacy APIs do not integrate well with the rest of the stack
|
| /Documentation/devicetree/bindings/mmc/ |
| D | sdhci-am654.yaml | 61 ti,otap-del-sel-legacy:
62 description: Output tap delay for SD/MMC legacy timing
131 ti,itap-del-sel-legacy:
132 description: Input tap delay for SD/MMC legacy timing
210 - ti,otap-del-sel-legacy
232 ti,otap-del-sel-legacy = <0x0>;
237 ti,itap-del-sel-legacy = <0x10>;
|
| /Documentation/core-api/irq/ |
| D | irq-domain.rst | 157 Legacy section in Types of irq_domain mappings
167 The Legacy mapping is a special case for drivers that already have a
172 case the Linux IRQ numbers cannot be dynamically assigned and the legacy
178 in the legacy behaviour.
180 The legacy map assumes a contiguous range of IRQ numbers has already
187 The legacy map should only be used if fixed IRQ mappings must be
188 supported. For example, ISA controllers would use the legacy map for
192 Most users of legacy mappings should use irq_domain_add_simple() or
193 irq_domain_create_simple() which will use a legacy domain only if an IRQ range
|
| /Documentation/filesystems/nfs/ |
| D | rpc-server-gss.rst | 46 NFS Server Legacy Upcall Mechanism
78 suffer from the size limitations of the legacy protocol.
84 legacy mechanism. To switch to the new mechanism, gss-proxy must bind
90 locking into the legacy mechanisms, the above steps must be performed
|
| /Documentation/devicetree/bindings/ |
| D | incomplete-devices.yaml | 7 title: Rejected, Legacy or Incomplete Devices
36 - description: Legacy compatibles used on Macintosh devices
148 - description: Legacy compatibles used on other PowerPC devices
204 - description: Legacy compatibles used on SPARC devices
231 - description: Incomplete and/or legacy compatibles for unknown devices
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | nvidia,tegra20-ictlr.txt | 1 NVIDIA Legacy Interrupt Controller
3 All Tegra SoCs contain a legacy interrupt controller that routes
|
| /Documentation/devicetree/bindings/clock/ |
| D | fsl,qoriq-clock.yaml | 118 $ref: fsl,qoriq-clock-legacy.yaml
122 $ref: fsl,qoriq-clock-legacy.yaml
126 $ref: fsl,qoriq-clock-legacy.yaml
130 $ref: fsl,qoriq-clock-legacy.yaml
150 /* Legacy example */
|
| /Documentation/sound/designs/ |
| D | midi-2.0.rst | 9 more fine controls over the legacy MIDI 1.0. The fundamental changes
14 - Transparent conversions between UMP and legacy MIDI 1.0 byte stream
59 support for the legacy raw MIDI device for UMP Endpoints.
84 legacy applications accessing mistakenly to UMP devices.
106 (0-based) UMP Group. Legacy applications can access to the specified
175 either the legacy, UMP MIDI 1.0 or UMP MIDI 2.0 device, respectively.
176 The first, legacy client is the one that sends/receives the old
185 is treated as a legacy event as it was (with max 12 byte data
198 Client 14 : "Midi Through" [Kernel Legacy]
213 Here you can find two types of kernel clients, "Legacy" for client 14,
[all …]
|