| /linux/Documentation/devicetree/bindings/powerpc/nintendo/ |
| H A 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 …]
|
| H A 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 …]
|
| /linux/tools/testing/selftests/net/ |
| H A D | epoll_busy_poll.c | 5 * Only tests the ioctls, but should be expanded to test two connected hosts in
76 TH_LOG("EPIOCGPARAMS on invalid epoll FD should error"); in TEST_F()
79 TH_LOG("EPIOCGPARAMS on invalid epoll FD should set errno to ENOTTY"); in TEST_F()
86 TH_LOG("EPIOCSPARAMS on invalid epoll FD should error"); in TEST_F()
89 TH_LOG("EPIOCSPARAMS on invalid epoll FD should set errno to ENOTTY"); in TEST_F()
130 * the default should be default and all fields should be zero'd by the in TEST_F()
142 TH_LOG("ioctl EPIOCGPARAMS should succeed"); in TEST_F()
145 TH_LOG("EPIOCGPARAMS busy_poll_usecs should have been 0"); in TEST_F()
148 TH_LOG("EPIOCGPARAMS busy_poll_budget should have been 0"); in TEST_F()
151 TH_LOG("EPIOCGPARAMS prefer_busy_poll should have been 0"); in TEST_F()
[all …]
|
| /linux/Documentation/devicetree/bindings/arm/ |
| H A D | atmel-sysregs.txt | 4 - compatible: Should be "atmel,sama5d2-chipid" or "microchip,sama7g5-chipid"
6 - reg : Should contain registers location and length
9 - compatible: Should be "atmel,at91sam9260-pit"
10 - reg: Should contain registers location and length
11 - interrupts: Should contain interrupt for the PIT which is the IRQ line
15 - compatible: Should be "microchip,sam9x60-pit64b" or
18 - reg: Should contain registers location and length
19 - interrupts: Should contain interrupt for PIT64B timer
20 - clocks: Should contain the available clock sources for PIT64B timer.
23 - compatible: Should be "atmel,at91rm9200-st", "syscon", "simple-mfd"
[all …]
|
| /linux/drivers/staging/axis-fifo/ |
| H A D | axis-fifo.txt | 17 - compatible: Should be one of:
21 - interrupt-names: Should be "interrupt"
22 - interrupt-parent: Should be <&intc>
23 - interrupts: Should contain interrupts lines.
24 - reg: Should contain registers location and length.
25 - xlnx,axi-str-rxd-protocol: Should be "XIL_AXI_STREAM_ETH_DATA"
26 - xlnx,axi-str-rxd-tdata-width: Should be <0x20>
27 - xlnx,axi-str-txc-protocol: Should be "XIL_AXI_STREAM_ETH_CTRL"
28 - xlnx,axi-str-txc-tdata-width: Should be <0x20>
29 - xlnx,axi-str-txd-protocol: Should be "XIL_AXI_STREAM_ETH_DATA"
[all …]
|
| /linux/Documentation/userspace-api/ |
| H A D | check_exec.rst | 14 Whether an interpreter should check these securebits or not depends on the
18 syscalls and access arbitrary files. Such interpreters should then be
20 However, a JavaScript engine running in a web browser should already be
21 sandboxed and then should not be able to harm the user's environment.
41 Programs should always perform this check to apply kernel-level checks against
44 view of the interpreter, should be checked. However the result of this check
45 should only be enforced according to ``SECBIT_EXEC_RESTRICT_FILE`` or
54 In a secure environment, libraries and any executable dependencies should also
55 be checked. For instance, dynamic linking should make sure that all libraries
57 For such secure execution environment to make sense, only trusted code should
[all …]
|
| /linux/Documentation/devicetree/bindings/usb/ |
| H A 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
43 - phy_type : For multi port host USB controllers, should be one of
57 - compatible: Should be one of the following
[all …]
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | dynptr_fail.c | 144 /* this should fail */ in ringbuf_release_uninit_dynptr()
164 /* this should fail */ in use_after_invalid()
203 /* this should fail */ in add_dynptr_to_map1()
221 /* this should fail */ in add_dynptr_to_map2()
266 /* this should fail */ in data_slice_out_of_bounds_skb()
286 /* this should fail */ in data_slice_out_of_bounds_skb_meta()
329 /* this should fail */ in data_slice_use_after_release1()
363 /* this should fail */ in data_slice_use_after_release2()
390 /* this should fail */ in data_slice_missing_null_check1()
410 /* this should fai in data_slice_missing_null_check2()
[all...] |
| H A D | verifier_sock_addr.c | 17 __failure __msg("At program exit the register R0 has smin=0 smax=0 should have been in [1, 1]")
31 __failure __msg("At program exit the register R0 has smin=0 smax=0 should have been in [1, 1]")
45 __failure __msg("At program exit the register R0 has smin=0 smax=0 should have been in [1, 1]")
66 __failure __msg("At program exit the register R0 has smin=2 smax=2 should have been in [0, 1]")
87 __failure __msg("At program exit the register R0 has smin=2 smax=2 should have been in [0, 1]")
108 __failure __msg("At program exit the register R0 has smin=2 smax=2 should have been in [0, 1]")
122 __failure __msg("At program exit the register R0 has smin=0 smax=0 should have been in [1, 1]")
136 __failure __msg("At program exit the register R0 has smin=0 smax=0 should have been in [1, 1]")
150 __failure __msg("At program exit the register R0 has smin=0 smax=0 should have been in [1, 1]")
164 __failure __msg("At program exit the register R0 has smin=0 smax=0 should have been in [1, 1]")
[all …]
|
| /linux/Documentation/devicetree/bindings/arm/omap/ |
| H A 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 …]
|
| /linux/tools/testing/selftests/net/forwarding/ |
| H A 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 …]
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | style.rst | 33 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/tools/testing/selftests/mm/ |
| H A D | hugetlb-madvise.c | 108 /* addr before mapping should fail */ in main()
117 /* addr + length after mapping should fail */ in main()
142 /* addr is not huge page size aligned and should fail */ in main()
152 /* addr + length should be aligned down to huge page size */ in main()
160 /* should free all but last page in mapping */ in main()
185 /* should free all pages in mapping */ in main()
207 /* read should not consume any pages */ in main()
211 /* madvise should not free any pages */ in main()
218 /* writes should allocate private pages */ in main()
222 /* madvise should free private pages */ in main()
[all …]
|
| /linux/Documentation/devicetree/bindings/regulator/ |
| H A D | regulator.yaml | 41 description: boolean, regulator should never be disabled
47 If the bootloader didn't leave it on then OS should turn it on
63 disabling ramp rate, it should be explicitly initialised to zero (regulator-ramp-delay
132 protection and value '1' indicates that protection should be enabled but
139 that detection should be enabled but limit setting can be omitted.
144 damaged. Recovery actions should be initiated. Zero can be passed to
145 disable detection and value '1' indicates that detection should
151 protection and value '1' indicates that protection should be enabled but
159 that detection should be enabled but limit setting can be omitted. Limit
165 damaged. Recovery actions should be initiated. Zero can be passed to
[all …]
|
| /linux/tools/testing/selftests/kvm/ |
| H A D | guest_memfd_test.c | 33 "read on a guest_mem fd should fail"); in test_file_read_write()
35 "write on a guest_mem fd should fail"); in test_file_read_write()
37 "pread on a guest_mem fd should fail"); in test_file_read_write()
39 "pwrite on a guest_mem fd should fail"); in test_file_read_write()
65 TEST_ASSERT(!ret, "fallocate the first page should succeed."); in test_mmap_supported()
117 "mbind with invalid policy should fail with EINVAL"); in test_mbind()
218 TEST_ASSERT(!ret, "fstat should succeed"); in test_file_size()
228 TEST_ASSERT(!ret, "fallocate with aligned offset and size should succeed"); in test_fallocate()
232 TEST_ASSERT(ret, "fallocate with unaligned offset should fail"); in test_fallocate()
235 TEST_ASSERT(ret, "fallocate beginning at total_size should fail"); in test_fallocate()
[all …]
|
| /linux/Documentation/devicetree/bindings/powerpc/4xx/ |
| H A 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.
|
| /linux/Documentation/networking/ |
| H A D | netdev-features.rst | 26 request. This set should be initialized in ndo_init callback and not
30 for a device. This should be changed only by network core or in
41 networking core and should not be referenced in drivers.
65 netdev_update_features() while holding rtnl_lock. This should not be done
66 from ndo_*_features callbacks. netdev->features should not be modified by
76 All dependencies between features should be resolved here. The resulting
81 This callback should not modify hardware nor driver state (should be
91 Hardware should be reconfigured to match passed feature set. The set
92 should not be altered unless some error condition happens that can't
94 should update netdev->features to match resulting hardware state.
[all …]
|
| /linux/Documentation/devicetree/bindings/remoteproc/ |
| H A D | ti,keystone-rproc.txt | 15 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/Documentation/process/ |
| H A 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
53 - Does your change have performance implications? If so, you should run
55 summary of the results should be included with the patch.
73 general rule, a patch should be based on the current mainline as found in
84 Only the most simple changes should be formatted as a single patch;
85 everything else should be made as a logical series of changes. Splitting
97 - Each logically independent change should be formatted as a separate
99 large (adding a significant new driver, for example), but they should be
101 should make a specific change which can be reviewed on its own and
[all …]
|
| /linux/tools/testing/selftests/kvm/s390/ |
| H A D | cmma_test.c | 233 /* GET_CMMA_BITS without CMMA enabled should fail */ in test_get_cmma_basic()
243 /* GET_CMMA_BITS without migration mode and without peeking should fail */ in test_get_cmma_basic()
248 /* GET_CMMA_BITS without migration mode and with peeking should work */ in test_get_cmma_basic()
279 /* enabling migration mode on a VM without memory should fail */ in test_migration_mode()
283 TEST_ASSERT(!is_migration_mode_on(vm), "migration mode should still be off"); in test_migration_mode()
300 /* migration mode when memslots have dirty tracking off should fail */ in test_migration_mode()
304 TEST_ASSERT(!is_migration_mode_on(vm), "migration mode should still be off"); in test_migration_mode()
310 /* enabling migration mode should work now */ in test_migration_mode()
313 TEST_ASSERT(is_migration_mode_on(vm), "migration mode should be on"); in test_migration_mode()
323 * This should turn off migration mode. in test_migration_mode()
[all …]
|
| /linux/Documentation/dev-tools/ |
| H A D | checkpatch.rst | 246 The first argument for kcalloc or kmalloc_array should be the
259 should be::
276 Architecture specific defines should be avoided wherever
286 BUG() or BUG_ON() should be avoided totally.
355 The function names should preferably follow the above pattern.
407 otherwise valid syscalls. This should be avoided in new code.
412 ENOTSUPP is not a standard error code and should be avoided in new patches.
413 EOPNOTSUPP should be used instead.
418 EXPORT_SYMBOL should immediately follow the symbol to be exported.
433 It should not be used for any other purpose.
[all …]
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-maintainer-entry-profile.rst | 46 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/Documentation/driver-api/dmaengine/ |
| H A D | provider.rst | 71 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
267 - The driver should return DMA_OUT_OF_ORDER for device_tx_status if
270 - All cookie tracking and checking API should be treated as invalid if
286 - This feature is limited to interleaved transfers, this flag should thus not
289 should be added in the future if and when the need arises.
[all …]
|
| /linux/Documentation/virt/kvm/ |
| H A D | review-checklist.rst | 10 2. Patches should be against kvm.git master or next branches.
18 5. New features must default to off (userspace should explicitly request them).
19 Performance improvements can and should default to on.
21 6. New cpu features should be exposed via KVM_GET_SUPPORTED_CPUID2,
24 7. The feature should be testable (see below).
26 8. Changes should be vendor neutral when possible. Changes to common code
42 All features contributed to KVM, and in many cases bugfixes too, should be
70 The corresponding CPU features (if applicable) should be made available
77 These should be tested via ``kvm-unit-tests``; this more or less implies
91 While it's difficult to provide a single policy, you should ensure that
[all …]
|
| /linux/include/linux/iio/ |
| H A D | events.h | 14 * @chan_type: Type of the channel. Should be one of enum iio_chan_type.
16 * @modifier: Modifier for the channel. Should be one of enum iio_modifier.
18 * @type: Type of the event. Should be one of enum iio_event_type.
23 * Drivers should use the specialized macros below instead of using this one
38 * @chan_type: Type of the channel. Should be one of enum iio_chan_type.
40 * @modifier: Modifier for the channel. Should be one of enum iio_modifier.
41 * @type: Type of the event. Should be one of enum iio_event_type.
52 * @chan_type: Type of the channel. Should be one of enum iio_chan_type.
54 * @type: Type of the event. Should be one of enum iio_event_type.
63 * @chan_type: Type of the channel. Should be one of enum iio_chan_type.
[all …]
|