Home
last modified time | relevance | path

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

12345678910>>...329

/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 …]
Domap-usb.txt4 - compatible : Should be "ti,omap4-musb" or "ti,omap3-musb"
6 - multipoint : Should be "1" indicating the musb controller supports
9 MUSB configuration-specific setting. Should be set to "16"
10 - ram-bits : Specifies the ram address size. Should be set to "12"
12 interface between the controller and the phy. It should be "0" or "1"
14 - mode : Should be "3" to represent OTG. "1" signifies HOST and "2"
16 - power : Should be "50". This signifies the controller can supply up to
47 - compatible : Should be
50 - ti,hwmods : Should be "usb_otg_ss"
56 It should be set to "1" for HW mode and "2" for SW mode.
[all …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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.
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.6/tools/testing/selftests/mm/
Dhugetlb-madvise.c134 /* addr before mapping should fail */ in main()
143 /* addr + length after mapping should fail */ in main()
168 /* addr is not huge page size aligned and should fail */ in main()
178 /* addr + length should be aligned down to huge page size */ in main()
186 /* should free all but last page in mapping */ in main()
211 /* should free all pages in mapping */ in main()
233 /* read should not consume any pages */ in main()
237 /* madvise should not free any pages */ in main()
244 /* writes should allocate private pages */ in main()
248 /* madvise should free private pages */ in main()
[all …]
/Linux-v6.6/Documentation/devicetree/bindings/regulator/
Dregulator.yaml38 description: boolean, regulator should never be disabled
44 If the bootloader didn't leave it on then OS should turn it on
60 disabling ramp rate, it should be explicitly initialised to zero (regulator-ramp-delay
124 protection and value '1' indicates that protection should be enabled but
131 that detection should be enabled but limit setting can be omitted.
136 damaged. Recovery actions should be initiated. Zero can be passed to
137 disable detection and value '1' indicates that detection should
143 protection and value '1' indicates that protection should be enabled but
151 that detection should be enabled but limit setting can be omitted. Limit
157 damaged. Recovery actions should be initiated. Zero can be passed to
[all …]
/Linux-v6.6/Documentation/devicetree/bindings/mmc/
Dsdhci-omap.txt5 For UHS devices which require tuning, the device tree should have a "cpu_thermal" node which maps t…
8 - compatible: Should be "ti,omap2430-sdhci" for omap2430 controllers
9 Should be "ti,omap3-sdhci" for omap3 controllers
10 Should be "ti,omap4-sdhci" for omap4 and ti81 controllers
11 Should be "ti,omap5-sdhci" for omap5 controllers
12 Should be "ti,dra7-sdhci" for DRA7 and DRA72 controllers
13 Should be "ti,k2g-sdhci" for K2G
14 Should be "ti,am335-sdhci" for am335x controllers
15 Should be "ti,am437-sdhci" for am437x controllers
18 - pinctrl-names: Should be subset of "default", "hs", "sdr12", "sdr25", "sdr50",
/Linux-v6.6/tools/testing/selftests/bpf/
Dtest_flow_dissector.sh113 # Send 10 IPv4/UDP packets from port 8. Filter should not drop any.
115 # Send 10 IPv4/UDP packets from port 9. Filter should drop all.
117 # Send 10 IPv4/UDP packets from port 10. Filter should not drop any.
121 # Send 10 IPv4/UDP packets from port 8. Filter should not drop any.
123 # Send 10 IPv4/UDP packets from port 9. Filter should drop all.
125 # Send 10 IPv4/UDP packets from port 10. Filter should not drop any.
129 # Send 10 IPv4/IPv4/UDP packets from port 8. Filter should not drop any.
132 # Send 10 IPv4/IPv4/UDP packets from port 9. Filter should drop all.
135 # Send 10 IPv4/IPv4/UDP packets from port 10. Filter should not drop any.
140 # Send 10 IPv4/GRE/IPv4/UDP packets from port 8. Filter should not drop any.
[all …]
/Linux-v6.6/Documentation/devicetree/bindings/remoteproc/
Dti,keystone-rproc.txt15 Each DSP Core sub-system is represented as a single DT node, and should also
25 - compatible: Should be one of the following,
31 - reg: Should contain an entry for each value in 'reg-names'.
32 Each entry should have the memory region's start address
36 - reg-names: Should contain strings with the following names, each
38 should be defined in this order,
41 - ti,syscon-dev: Should be a pair of the phandle to the Keystone Device
45 - resets: Should contain the phandle to the reset controller node
54 - interrupts: Should contain an entry for each value in 'interrupt-names'.
55 Each entry should have the interrupt source number used by
[all …]
/Linux-v6.6/Documentation/process/
D5.Posting.rst23 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 …]
/Linux-v6.6/Documentation/filesystems/
Dxfs-maintainer-entry-profile.rst46 They should help prioritize development and review work for each release
60 Reviewers should identify themselves with an ``R:`` entry in the kernel
68 The testing lead should identify themselves with an ``M:`` entry in
72 enough detail to identify the person to whom the report should be
75 The bug triagers should identify themselves with a ``B:`` entry in
86 The release manager should identify themselves with an ``M:`` entry in
99 The maintainer for a given LTS release should identify themselves with an
101 Unmaintained LTS kernels should be marked with status ``S: Orphan`` in that
108 - Patches affecting only the filesystem itself should be based against
116 - Any patchset changing XFS should be cc'd in its entirety to linux-xfs.
[all …]
/Linux-v6.6/scripts/kconfig/tests/preprocess/escape/
DKconfig23 # The following should print "$(X)". It should not be expanded further.
28 # The following should print "(".
32 # A simple expanded should not be expanded multiple times.
33 # The following should print "$(X)". It should not be expanded further.
37 # The following should print "$(X)" as well.
41 # The following should print "$(".
42 # It should not be emit "unterminated reference" error.
/Linux-v6.6/tools/testing/selftests/kvm/s390x/
Dcmma_test.c238 /* GET_CMMA_BITS without CMMA enabled should fail */ in test_get_cmma_basic()
248 /* GET_CMMA_BITS without migration mode and without peeking should fail */ in test_get_cmma_basic()
253 /* GET_CMMA_BITS without migration mode and with peeking should work */ in test_get_cmma_basic()
284 /* enabling migration mode on a VM without memory should fail */ in test_migration_mode()
288 TEST_ASSERT(!is_migration_mode_on(vm), "migration mode should still be off"); in test_migration_mode()
305 /* migration mode when memslots have dirty tracking off should fail */ in test_migration_mode()
309 TEST_ASSERT(!is_migration_mode_on(vm), "migration mode should still be off"); in test_migration_mode()
315 /* enabling migration mode should work now */ in test_migration_mode()
318 TEST_ASSERT(is_migration_mode_on(vm), "migration mode should be on"); in test_migration_mode()
328 * This should turn off migration mode. in test_migration_mode()
[all …]
/Linux-v6.6/Documentation/devicetree/bindings/pci/
Dti-pci.txt4 - compatible: Should be "ti,dra7-pcie" for RC (deprecated)
5 Should be "ti,dra7-pcie-ep" for EP (deprecated)
6 Should be "ti,dra746-pcie-rc" for dra74x/dra76 in RC mode
7 Should be "ti,dra746-pcie-ep" for dra74x/dra76 in EP mode
8 Should be "ti,dra726-pcie-rc" for dra72x in RC mode
9 Should be "ti,dra726-pcie-ep" for dra72x in EP mode
37 should contain the register offset within syscon
38 and the 2nd argument should contain the bit field
55 should contain the register offset within syscon
56 and the 2nd argument should contain the bit field
[all …]
/Linux-v6.6/Documentation/input/
Devent-codes.rst116 Client should ignore all events up to and including next SYN_REPORT
137 code should be set to a value of 1. When the tool is no longer interacting
138 with the input device, the BTN_TOOL_<name> code should be reset to 0. All
139 trackpads, tablets, and touchscreens should use at least one BTN_TOOL_<name>
141 touchscreens should export only one BTN_TOOL_<name> at a time. To not break
172 BTN_TOOL_DOUBLETAP should be set to value 1 for the duration of the motion.
174 purpose. A trackpad event generated by finger touches should generate events
176 codes should have a value of 1 during any synchronization frame.
181 Note: In multitouch drivers, the input_mt_report_finger_count() function should
189 space is unknown. If the absolute position is known, EV_ABS codes should be used
[all …]
/Linux-v6.6/Documentation/driver-api/dmaengine/
Dprovider.rst71 destination addresses, whether it should increment these addresses or
114 - ``channels``: should be initialized as a list using the
118 should contain a bitmask of the supported source transfer width
121 should contain a bitmask of the supported destination transfer width
124 should contain a bitmask of the supported slave directions
142 - ``dev``: should hold the pointer to the ``struct device`` associated
265 - The driver should return DMA_OUT_OF_ORDER for device_tx_status if
268 - All cookie tracking and checking API should be treated as invalid if
284 - This feature is limited to interleaved transfers, this flag should thus not
287 should be added in the future if and when the need arises.
[all …]

12345678910>>...329