| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | wii.txt | 11 - model : Should be "nintendo,wii" 12 - compatible : Should be "nintendo,wii" 21 - compatible : Should be "nintendo,hollywood" 30 - compatible : should be "nintendo,hollywood-vi","nintendo,flipper-vi" 31 - reg : should contain the VI registers location and length 32 - interrupts : should contain the VI interrupt 41 - compatible : should be "nintendo,hollywood-pi","nintendo,flipper-pi" 42 - reg : should contain the PI registers location and length 53 - compatible : should be "nintendo,flipper-pic" 63 - compatible : should be "nintendo,hollywood-dsp","nintendo,flipper-dsp" [all …]
|
| D | gamecube.txt | 12 - compatible : Should be "nintendo,flipper" 21 - compatible : should be "nintendo,flipper-vi" 22 - reg : should contain the VI registers location and length 23 - interrupts : should contain the VI interrupt 32 - compatible : should be "nintendo,flipper-pi" 33 - reg : should contain the PI registers location and length 43 - compatible : should be "nintendo,flipper-pic" 52 - compatible : should be "nintendo,flipper-dsp" 53 - reg : should contain the DSP registers location and length 54 - interrupts : should contain the DSP interrupt [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | wii.txt | 11 - model : Should be "nintendo,wii" 12 - compatible : Should be "nintendo,wii" 21 - compatible : Should be "nintendo,hollywood" 30 - compatible : should be "nintendo,hollywood-vi","nintendo,flipper-vi" 31 - reg : should contain the VI registers location and length 32 - interrupts : should contain the VI interrupt 41 - compatible : should be "nintendo,hollywood-pi","nintendo,flipper-pi" 42 - reg : should contain the PI registers location and length 53 - compatible : should be "nintendo,flipper-pic" 63 - compatible : should be "nintendo,hollywood-dsp","nintendo,flipper-dsp" [all …]
|
| D | gamecube.txt | 12 - compatible : Should be "nintendo,flipper" 21 - compatible : should be "nintendo,flipper-vi" 22 - reg : should contain the VI registers location and length 23 - interrupts : should contain the VI interrupt 32 - compatible : should be "nintendo,flipper-pi" 33 - reg : should contain the PI registers location and length 43 - compatible : should be "nintendo,flipper-pic" 52 - compatible : should be "nintendo,flipper-dsp" 53 - reg : should contain the DSP registers location and length 54 - interrupts : should contain the DSP interrupt [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | atmel-sysregs.txt | 4 - compatible: Should be "atmel,sama5d2-chipid" 5 - reg : Should contain registers location and length 8 - compatible: Should be "atmel,at91sam9260-pit" 9 - reg: Should contain registers location and length 10 - interrupts: Should contain interrupt for the PIT which is the IRQ line 14 - compatible: Should be "microchip,sam9x60-pit64b" 15 - reg: Should contain registers location and length 16 - interrupts: Should contain interrupt for PIT64B timer 17 - clocks: Should contain the available clock sources for PIT64B timer. 20 - compatible: Should be "atmel,at91rm9200-st", "syscon", "simple-mfd" [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/edac/ |
| D | socfpga-eccmgr.txt | 8 - compatible : Should be "altr,socfpga-ecc-manager" 11 - ranges : standard definition, should translate from local addresses 17 - compatible : Should be "altr,socfpga-l2-ecc" 19 - interrupts : Should be single bit error interrupt, then double bit error 24 - compatible : Should be "altr,socfpga-ocram-ecc" 27 - interrupts : Should be single bit error interrupt, then double bit error 58 - compatible : Should be "altr,socfpga-a10-ecc-manager" 63 - interrupts : Should be single bit error interrupt, then double bit error 67 - ranges : standard definition, should translate from local addresses 73 - compatible : Should be "altr,socfpga-a10-l2-ecc" [all …]
|
| /kernel/linux/linux-4.19/drivers/staging/axis-fifo/ |
| D | axis-fifo.txt | 17 - compatible: Should be "xlnx,axi-fifo-mm-s-4.1" 18 - interrupt-names: Should be "interrupt" 19 - interrupt-parent: Should be <&intc> 20 - interrupts: Should contain interrupts lines. 21 - reg: Should contain registers location and length. 22 - xlnx,axi-str-rxd-protocol: Should be "XIL_AXI_STREAM_ETH_DATA" 23 - xlnx,axi-str-rxd-tdata-width: Should be <0x20> 24 - xlnx,axi-str-txc-protocol: Should be "XIL_AXI_STREAM_ETH_CTRL" 25 - xlnx,axi-str-txc-tdata-width: Should be <0x20> 26 - xlnx,axi-str-txd-protocol: Should be "XIL_AXI_STREAM_ETH_DATA" [all …]
|
| /kernel/linux/linux-5.10/drivers/staging/axis-fifo/ |
| D | axis-fifo.txt | 17 - compatible: Should be "xlnx,axi-fifo-mm-s-4.1" 18 - interrupt-names: Should be "interrupt" 19 - interrupt-parent: Should be <&intc> 20 - interrupts: Should contain interrupts lines. 21 - reg: Should contain registers location and length. 22 - xlnx,axi-str-rxd-protocol: Should be "XIL_AXI_STREAM_ETH_DATA" 23 - xlnx,axi-str-rxd-tdata-width: Should be <0x20> 24 - xlnx,axi-str-txc-protocol: Should be "XIL_AXI_STREAM_ETH_CTRL" 25 - xlnx,axi-str-txc-tdata-width: Should be <0x20> 26 - xlnx,axi-str-txd-protocol: Should be "XIL_AXI_STREAM_ETH_DATA" [all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/edac/ |
| D | socfpga-eccmgr.txt | 8 - compatible : Should be "altr,socfpga-ecc-manager" 11 - ranges : standard definition, should translate from local addresses 17 - compatible : Should be "altr,socfpga-l2-ecc" 19 - interrupts : Should be single bit error interrupt, then double bit error 24 - compatible : Should be "altr,socfpga-ocram-ecc" 27 - interrupts : Should be single bit error interrupt, then double bit error 58 - compatible : Should be "altr,socfpga-a10-ecc-manager" 63 - interrupts : Should be single bit error interrupt, then double bit error 67 - ranges : standard definition, should translate from local addresses 73 - compatible : Should be "altr,socfpga-a10-l2-ecc" [all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/ |
| D | atmel-at91.txt | 75 - compatible: Should be "atmel,sama5d2-chipid" 76 - reg : Should contain registers location and length 79 - compatible: Should be "atmel,at91sam9260-pit" 80 - reg: Should contain registers location and length 81 - interrupts: Should contain interrupt for the PIT which is the IRQ line 85 - compatible: Should be "atmel,at91rm9200-st", "syscon", "simple-mfd" 86 - reg: Should contain registers location and length 87 - interrupts: Should contain interrupt for the ST which is the IRQ line 91 - watchdog: compatible should be "atmel,at91rm9200-wdt" 94 - compatible: Should be "atmel,<chip>-rstc". [all …]
|
| /kernel/linux/linux-4.19/drivers/staging/iio/Documentation/ |
| D | sysfs-bus-iio-light | 5 This should return the calculated lux from the light sensor. If 6 it comes back in SI units, it should also include _input else it 7 should include _raw to signify it is not in SI units. 14 in proximity mode. When this is enabled, then the device should 24 This property is supported by proximity sensors and should be 26 value is returned in SI units, it should also include _input 27 but if it is not, then it should include _raw. 34 sensing mode. This value should be the output from a reading 35 and if expressed in SI units, should include _input. If this 36 value is not in SI units, then it should include _raw. [all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/omap/ |
| D | l4.txt | 6 - compatible : Should be "ti,omap2-l4" for OMAP2 family l4 core bus 7 Should be "ti,omap2-l4-wkup" for OMAP2 family l4 wkup bus 8 Should be "ti,omap3-l4-core" for OMAP3 family l4 core bus 9 Should be "ti,omap4-l4-cfg" for OMAP4 family l4 cfg bus 10 Should be "ti,omap4-l4-per" for OMAP4 family l4 per bus 11 Should be "ti,omap4-l4-wkup" for OMAP4 family l4 wkup bus 12 Should be "ti,omap5-l4-cfg" for OMAP5 family l4 cfg bus 13 Should be "ti,omap5-l4-wkup" for OMAP5 family l4 wkup bus 14 Should be "ti,dra7-l4-cfg" for DRA7 family l4 cfg bus 15 Should be "ti,dra7-l4-wkup" for DRA7 family l4 wkup bus [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/omap/ |
| D | l4.txt | 6 - compatible : Should be "ti,omap2-l4" for OMAP2 family l4 core bus 7 Should be "ti,omap2-l4-wkup" for OMAP2 family l4 wkup bus 8 Should be "ti,omap3-l4-core" for OMAP3 family l4 core bus 9 Should be "ti,omap4-l4-cfg" for OMAP4 family l4 cfg bus 10 Should be "ti,omap4-l4-per" for OMAP4 family l4 per bus 11 Should be "ti,omap4-l4-wkup" for OMAP4 family l4 wkup bus 12 Should be "ti,omap5-l4-cfg" for OMAP5 family l4 cfg bus 13 Should be "ti,omap5-l4-wkup" for OMAP5 family l4 wkup bus 14 Should be "ti,dra7-l4-cfg" for DRA7 family l4 cfg bus 15 Should be "ti,dra7-l4-wkup" for DRA7 family l4 wkup bus [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/ |
| D | atmel-usb.txt | 6 - compatible: Should be "atmel,at91rm9200-ohci" for USB controllers 9 - interrupts: Should contain ohci interrupt 10 - clocks: Should reference the peripheral, host and system clocks 11 - clock-names: Should contain three strings 33 - compatible: Should be "atmel,at91sam9g45-ehci" for USB controllers 36 - interrupts: Should contain ehci interrupt 37 - clocks: Should reference the peripheral and the UTMI clocks 38 - clock-names: Should contain two strings 53 - compatible: Should be one of the following 59 - interrupts: Should contain macb interrupt [all …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/caching/ |
| D | backend-api.rst | 21 The cache definition (struct fscache_cache) should be initialised by calling:: 39 The cache should then be registered with FS-Cache by passing a pointer to the 46 Two extra arguments should also be supplied: 48 * "fsdef" which should point to the object representation for the FS-Cache 53 * "tagname" which, if given, should be a text string naming this cache. If 135 Structures of this type should be allocated by the cache backend and 141 that refer to a particular object. In such a case it should be printed 145 is backing. An object should retired when put_object() is called if it is 146 in state FSCACHE_OBJECT_RECYCLING. The fscache_object struct should be 170 an operation needs more processing time, it should be enqueued again. [all …]
|
| /kernel/linux/linux-4.19/Documentation/filesystems/caching/ |
| D | backend-api.txt | 20 The cache definition (struct fscache_cache) should be initialised by calling: 38 The cache should then be registered with FS-Cache by passing a pointer to the 45 Two extra arguments should also be supplied: 47 (*) "fsdef" which should point to the object representation for the FS-Cache 52 (*) "tagname" which, if given, should be a text string naming this cache. If 138 Structures of this type should be allocated by the cache backend and 144 that refer to a particular object. In such a case it should be printed 148 is backing. An object should retired when put_object() is called if it is 149 in state FSCACHE_OBJECT_RECYCLING. The fscache_object struct should be 173 an operation needs more processing time, it should be enqueued again. [all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | akebono.txt | 20 - compatible : should be "ibm,476gtr-sdhci","generic-sdhci". 21 - reg : should contain the SDHCI registers location and length. 22 - interrupts : should contain the SDHCI interrupt. 30 - compatible : should be "ibm,476gtr-ahci". 31 - reg : should contain the AHCI registers location and length. 32 - interrupts : should contain the AHCI interrupt. 41 - compatible : should be "ibm,akebono-fpga". 42 - reg : should contain the FPGA registers location and length. 51 - compatible : should be "ibm,akebono-avr". 52 - reg : should contain the I2C bus address for the AVR.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | akebono.txt | 20 - compatible : should be "ibm,476gtr-sdhci","generic-sdhci". 21 - reg : should contain the SDHCI registers location and length. 22 - interrupts : should contain the SDHCI interrupt. 30 - compatible : should be "ibm,476gtr-ahci". 31 - reg : should contain the AHCI registers location and length. 32 - interrupts : should contain the AHCI interrupt. 41 - compatible : should be "ibm,akebono-fpga". 42 - reg : should contain the FPGA registers location and length. 51 - compatible : should be "ibm,akebono-avr". 52 - reg : should contain the I2C bus address for the AVR.
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/kunit/ |
| D | style.rst | 33 rule of thumb is that a test subsystem should match a single kernel module. If 35 should correspond to a directory in the source tree or an entry in the 39 Test subsystems should be named after the code being tested, either after the 41 subsystems should be named to avoid ambiguity where necessary. 43 If a test subsystem name has multiple components, they should be separated by 62 Names should use underscores, not dashes, to separate words. Prefer 65 As well as using underscores, this name should not have "kunit-test" as a 69 The corresponding module name is ``parport_pc``, so this subsystem should also 87 contains several suites, the specific area under test should be appended to the 91 subsystem (e.g., both unit tests and integration tests), they should be put into [all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/usb/ |
| D | atmel-usb.txt | 6 - compatible: Should be "atmel,at91rm9200-ohci" for USB controllers 9 - interrupts: Should contain ohci interrupt 10 - clocks: Should reference the peripheral, host and system clocks 11 - clock-names: Should contain three strings 33 - compatible: Should be "atmel,at91sam9g45-ehci" for USB controllers 36 - interrupts: Should contain ehci interrupt 37 - clocks: Should reference the peripheral and the UTMI clocks 38 - clock-names: Should contain two strings 53 - compatible: Should be one of the following 59 - interrupts: Should contain macb interrupt [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/imx/ |
| D | fsl-imx-drm.txt | 8 - compatible: Should be "fsl,imx-display-subsystem" 9 - ports: Should contain a list of phandles pointing to display interface ports 24 - compatible: Should be "fsl,<chip>-ipu" where <chip> is one of 29 - reg: should be register base and length as documented in the 31 - interrupts: Should contain sync interrupt and error interrupt, 40 Ports 0 and 1 should correspond to CSI0 and CSI1, 41 ports 2 and 3 should correspond to DI0 and DI1, respectively. 66 - compatible: should be "fsl,imx6qp-pre" 67 - reg: should be register base and length as documented in the 72 - clock-names: should be "axi" [all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/imx/ |
| D | fsl-imx-drm.txt | 8 - compatible: Should be "fsl,imx-display-subsystem" 9 - ports: Should contain a list of phandles pointing to display interface ports 24 - compatible: Should be "fsl,<chip>-ipu" where <chip> is one of 29 - reg: should be register base and length as documented in the 31 - interrupts: Should contain sync interrupt and error interrupt, 40 Ports 0 and 1 should correspond to CSI0 and CSI1, 41 ports 2 and 3 should correspond to DI0 and DI1, respectively. 66 - compatible: should be "fsl,imx6qp-pre" 67 - reg: should be register base and length as documented in the 72 - clock-names: should be "axi" [all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/net/forwarding/ |
| D | fib_offload_lib.sh | 69 check_err $? "Route not in hardware when should" 73 check_err $? "Appended route in hardware when should not" 77 check_err $? "Prepended route not in hardware when should" 100 check_err $? "Route not in hardware when should" 104 check_err $? "Highest TOS route not in hardware when should" 107 check_err $? "Lowest TOS route still in hardware when should not" 111 check_err $? "Middle TOS route in hardware when should not" 129 check_err $? "Route not in hardware when should" 133 check_err $? "Lowest metric route not in hardware when should" 136 check_err $? "Highest metric route still in hardware when should not" [all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | 5.Posting.rst | 24 feedback from the community before the work is complete. So you should 38 There are a number of things which should be done before you consider 49 - Does your change have performance implications? If so, you should run 51 summary of the results should be included with the patch. 69 general rule, a patch should be based on the current mainline as found in 80 Only the most simple changes should be formatted as a single patch; 81 everything else should be made as a logical series of changes. Splitting 93 - Each logically independent change should be formatted as a separate 95 large (adding a significant new driver, for example), but they should be 97 should make a specific change which can be reviewed on its own and [all …]
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| D | 5.Posting.rst | 23 feedback from the community before the work is complete. So you should 37 There are a number of things which should be done before you consider 48 - Does your change have performance implications? If so, you should run 50 summary of the results should be included with the patch. 68 general rule, a patch should be based on the current mainline as found in 79 Only the most simple changes should be formatted as a single patch; 80 everything else should be made as a logical series of changes. Splitting 92 - Each logically independent change should be formatted as a separate 94 large (adding a significant new driver, for example), but they should be 96 should make a specific change which can be reviewed on its own and [all …]
|