Searched full:generic (Results 1 – 25 of 968) sorted by relevance
12345678910>>...39
| /Documentation/core-api/ |
| D | generic-radix-tree.rst | 2 Generic radix trees/sparse arrays
5 .. kernel-doc:: include/linux/generic-radix-tree.h
6 :doc: Generic radix trees/sparse arrays
8 generic radix tree functions
11 .. kernel-doc:: include/linux/generic-radix-tree.h
|
| D | genericirq.rst | 4 Linux generic IRQ handling
13 The generic interrupt handling layer is designed to provide a complete
16 drivers use generic API functions to request, enable, disable and free
23 generic IRQ handling layer.
68 reveals that most of them can use a generic set of 'irq flow' methods
75 which is normally one of the generic implementations. (This high-level
80 The separation makes the generic interrupt handling layer more flexible
81 and extensible. For example, an (sub)architecture can use a generic
119 into the generic interrupt code by calling desc->handle_irq(). This
157 The generic layer provides a set of pre-defined irq-flow methods:
[all …]
|
| /Documentation/networking/ |
| D | ppp_generic.rst | 4 PPP Generic Driver and Channel Interface
12 The generic PPP driver in linux-2.4 provides an implementation of the
25 For sending and receiving PPP frames, the generic PPP driver calls on
29 has a very simple interface with the generic PPP code: it merely has
37 be linked to each ppp network interface unit. The generic layer is
46 functions used to communicate between the generic PPP layer and PPP
49 Each channel has to provide two functions to the generic PPP layer,
52 * start_xmit() is called by the generic layer when it has a frame to
56 later time when it can accept frames again, and the generic layer
66 The generic PPP layer provides seven functions to channels:
[all …]
|
| D | generic_netlink.rst | 4 Generic Netlink
7 A wiki document on how to use Generic Netlink can be found here:
|
| D | segmentation-offloads.rst | 18 * Generic Segmentation Offload - GSO
19 * Generic Receive Offload - GRO
20 * Partial Generic Segmentation Offload - GSO_PARTIAL
107 Generic Segmentation Offload
110 Generic segmentation offload is a pure software offload that is meant to
121 Generic Receive Offload
124 Generic receive offload is the complement to GSO. Ideally any frame
133 Partial Generic Segmentation Offload
136 Partial generic segmentation offload is a hybrid between TSO and GSO. What
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb-xhci.txt | 6 - "generic-xhci" for generic XHCI device
13 When compatible with the generic version, nodes must list the
15 followed by the generic version.
39 compatible = "generic-xhci";
|
| D | usb-uhci.txt | 1 Generic Platform UHCI Controller
5 - compatible : "generic-uhci" (deprecated: "platform-uhci")
15 compatible = "generic-uhci";
|
| D | aspeed,usb-vhub.yaml | 20 and 15 generic endpoints, while AST2600 Virtual Hub supports 7 downstream
21 devices and 21 generic endpoints.
46 aspeed,vhub-generic-endpoints:
47 description: Number of generic endpoints supported by the Virtual Hub
106 - aspeed,vhub-generic-endpoints
119 aspeed,vhub-generic-endpoints = <15>;
|
| D | brcm,bcm3384-usb.txt | 6 These currently use the generic-ohci and generic-ehci drivers. On some
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | ptn3460.txt | 11 | 0 | 1024x768 | NXP Generic |
12 | 1 | 1920x1080 | NXP Generic |
13 | 2 | 1920x1080 | NXP Generic |
16 | 5 | 1366x768 | NXP Generic |
|
| /Documentation/driver-api/driver-model/ |
| D | porting.rst | 21 be embedded in larger, bus-specific objects. Fields in these generic
24 The generic objects must be registered with the driver model core. By
102 struct device dev; /* Generic device interface */
106 It is recommended that the generic device not be the first item in
109 should be created to convert from the generic object type::
128 bus driver should initialize the generic device. The most important
167 Once the generic device has been initialized, it can be registered
244 - Initialize the generic driver structure.
253 After the generic driver has been initialized, call::
281 Step 4: Define Generic Methods for Drivers.
[all …]
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-ath79.txt | 8 - #address-cells: <1>, as required by generic SPI binding.
9 - #size-cells: <0>, also as required by generic SPI binding.
11 Child nodes as per the generic SPI binding.
|
| D | spi-bcm63xx.txt | 9 - #address-cells: <1>, as required by generic SPI binding.
10 - #size-cells: <0>, also as required by generic SPI binding.
16 Child nodes as per the generic SPI binding.
|
| D | spi-bcm63xx-hsspi.txt | 9 - #address-cells: <1>, as required by generic SPI binding.
10 - #size-cells: <0>, also as required by generic SPI binding.
16 Child nodes as per the generic SPI binding.
|
| D | spi-octeon.txt | 7 - #address-cells : <1>, as required by generic SPI binding.
8 - #size-cells : <0>, also as required by generic SPI binding.
10 Child nodes as per the generic SPI binding.
|
| /Documentation/hwmon/ |
| D | pwm-fan.rst | 5 generic PWM interface thus it is hardware independent. It can be used on
7 the generic PWM API.
15 a PWM output. It uses the generic PWM interface, thus it can be used with
|
| /Documentation/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 20 GPMC generic timing calculation:
29 generic timing routine was developed to achieve above requirements.
31 Generic routine provides a generic method to calculate gpmc timings
40 field as required by peripheral, educate generic timing routine to
45 Generic timing routine has been verified to work properly on
48 A word of caution: generic timing routine has been developed based
|
| /Documentation/networking/devlink/ |
| D | devlink-params.rst | 12 This document describes a number of generic parameters that are supported
15 whether generic or not.
46 Generic configuration parameters
48 The following is a list of generic configuration parameters that drivers may
49 add. Use of generic parameters is preferred over each driver creating their
52 .. list-table:: List of generic parameters
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | sbsa-gwdt.txt | 1 * SBSA (Server Base System Architecture) Generic Watchdog
3 The SBSA Generic Watchdog Timer is used to force a reset of the system
18 Peripheral Interrupt) number of SBSA Generic Watchdog.
|
| /Documentation/devicetree/bindings/i2c/ |
| D | renesas,iic.txt | 26 - "renesas,rcar-gen2-iic" (generic R-Car Gen2 or RZ/G1
28 - "renesas,rcar-gen3-iic" (generic R-Car Gen3 or RZ/G2
30 - "renesas,rmobile-iic" (generic device)
32 When compatible with a generic R-Car version, nodes
34 the platform first followed by the generic R-Car
|
| D | renesas,i2c.txt | 29 "renesas,rcar-gen1-i2c" for a generic R-Car Gen1 compatible device.
30 "renesas,rcar-gen2-i2c" for a generic R-Car Gen2 or RZ/G1 compatible
32 "renesas,rcar-gen3-i2c" for a generic R-Car Gen3 or RZ/G2 compatible
36 When compatible with the generic version, nodes must list the
38 by the generic version.
|
| /Documentation/admin-guide/media/ |
| D | technisat.rst | 58 #) => ``Generic I2C PLL based tuners``
63 #) => ``Generic I2C PLL based tuners``
80 #) => ``Generic I2C PLL based tuners``
85 #) => ``Generic I2C PLL based tuners``
94 #) => ``Generic I2C PLL based tuners``
|
| D | dvb-usb-af9035-cardlist.rst | 45 * - ITE 9135 Generic
47 * - ITE 9135(9005) Generic
49 * - ITE 9135(9006) Generic
51 * - ITE 9303 Generic
|
| /Documentation/devicetree/bindings/regulator/ |
| D | sky81452-regulator.txt | 5 - any required generic properties defined in regulator.txt
8 - any available generic properties defined in regulator.txt
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | mscc,ocelot-pinctrl.txt | 16 The ocelot-pinctrl driver uses the generic pin multiplexing and generic pin
19 The following generic properties are supported:
|
12345678910>>...39