Home
last modified time | relevance | path

Searched full:should (Results 1 – 25 of 11543) sorted by relevance

12345678910>>...462

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/nintendo/
Dwii.txt11 - 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 …]
Dgamecube.txt12 - 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-6.6/Documentation/devicetree/bindings/powerpc/nintendo/
Dwii.txt11 - 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 …]
Dgamecube.txt12 - 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-6.6/Documentation/devicetree/bindings/arm/
Datmel-sysregs.txt4 - compatible: Should be "atmel,sama5d2-chipid" or "microchip,sama7g5-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/arm/
Datmel-sysregs.txt4 - 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/
Dsocfpga-eccmgr.txt8 - 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-6.6/Documentation/devicetree/bindings/edac/
Dsocfpga-eccmgr.txt8 - 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-6.6/drivers/staging/axis-fifo/
Daxis-fifo.txt17 - 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/
Daxis-fifo.txt17 - 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-6.6/Documentation/devicetree/bindings/arm/omap/
Dl4.txt6 - 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/
Dl4.txt6 - 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-6.6/Documentation/devicetree/bindings/usb/
Datmel-usb.txt6 - 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
43 - phy_type : For multi port host USB controllers, should be one of
57 - compatible: Should be one of the following
[all …]
/kernel/linux/linux-5.10/Documentation/filesystems/caching/
Dbackend-api.rst21 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-5.10/Documentation/devicetree/bindings/usb/
Datmel-usb.txt6 - 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/powerpc/4xx/
Dakebono.txt20 - 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-6.6/Documentation/devicetree/bindings/powerpc/4xx/
Dakebono.txt20 - 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/
Dstyle.rst33 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-6.6/Documentation/dev-tools/kunit/
Dstyle.rst33 test subsystem should match a single kernel module. If the code being tested
34 cannot be compiled as a module, in many cases the subsystem should correspond to
38 Test subsystems should be named after the code being tested, either after the
40 subsystems should be named to avoid ambiguity where necessary.
42 If a test subsystem name has multiple components, they should be separated by
60 Names should use underscores, not dashes, to separate words. Prefer
63 This name should use underscores, and not have "kunit-test" as a
67 The corresponding module name is ``parport_pc``, so this subsystem should also
85 contains several suites, the specific area under test should be appended to the
89 subsystem (for example, both unit tests and integration tests), they should be
[all …]
/kernel/linux/linux-6.6/tools/testing/selftests/bpf/progs/
Ddynptr_fail.c143 /* this should fail */ in ringbuf_release_uninit_dynptr()
163 /* this should fail */ in use_after_invalid()
202 /* this should fail */ in add_dynptr_to_map1()
220 /* this should fail */ in add_dynptr_to_map2()
265 /* this should fail */ in data_slice_out_of_bounds_skb()
308 /* this should fail */ in data_slice_use_after_release1()
342 /* this should fail */ in data_slice_use_after_release2()
369 /* this should fail */ in data_slice_missing_null_check1()
389 /* this should fail */ in data_slice_missing_null_check2()
407 /* this should fail */ in invalid_helper1()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/imx/
Dfsl-imx-drm.txt8 - 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-6.6/Documentation/devicetree/bindings/display/imx/
Dfsl-imx-drm.txt8 - 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/
Dfib_offload_lib.sh69 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-6.6/tools/testing/selftests/net/forwarding/
Dfib_offload_lib.sh69 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/
D5.Posting.rst24 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 …]

12345678910>>...462