Home
last modified time | relevance | path

Searched refs:should (Results 1 – 25 of 2955) sorted by relevance

12345678910>>...119

/Linux-v5.15/Documentation/devicetree/bindings/powerpc/nintendo/
Dwii.txt30 - 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"
64 - reg : should contain the DSP registers location and length
65 - interrupts : should contain the DSP interrupt
75 - compatible : should be "nintendo,hollywood-si","nintendo,flipper-si"
[all …]
Dgamecube.txt21 - 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
64 - compatible : should be "nintendo,flipper-aram"
[all …]
/Linux-v5.15/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-v5.15/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-v5.15/Documentation/devicetree/bindings/spi/
Dspi-mxic.txt5 - compatible: should be "mxicy,mx25f0a-spi"
6 - #address-cells: should be 1
7 - #size-cells: should be 0
8 - reg: should contain 2 entries, one for the registers and one for the direct
10 - reg-names: should contain "regs" and "dirmap"
12 - clock-names: should contain "ps_clk", "send_clk" and "send_dly_clk"
13 - clocks: should contain 3 entries for the "ps_clk", "send_clk" and
Dspi-slave-mt27xx.txt4 - compatible: should be one of the following.
10 It's clock gate, and should be <&infracfg CLK_INFRA_AO_SPI1>.
11 - clock-names: should be "spi" for the clock gate.
14 - assigned-clocks: it's mux clock, should be <&topckgen CLK_TOP_SPISLV_SEL>.
16 It's PLL, and should be one of the following.
/Linux-v5.15/Documentation/misc-devices/
Dpci-endpoint-test.rst7 This driver should be used as a host side driver if the root complex is
25 should be used to perform the above tests.
32 should be passed as argument.
37 to be tested should be passed as argument.
40 to be tested should be passed as argument.
43 should be passed as argument (0: Legacy, 1:MSI, 2:MSI-X).
47 Perform write tests. The size of the buffer should be passed
50 Perform read tests. The size of the buffer should be passed
53 Perform read tests. The size of the buffer should be passed
/Linux-v5.15/Documentation/driver-api/80211/
Dmac80211.rst5 You should read and understand the information contained within this
26 programming model should be in here, including the definition of
29 Finally, a discussion of hardware capabilities should be done with
49 This chapter should describe PHY handling including start/stop callbacks
62 This chapter should describe virtual interface basics that are relevant
63 to the driver (VLANs, MGMT etc are not.) It should explain the use of
67 Things related to AP mode should be discussed there.
69 Things related to supporting multiple interfaces should be in the
70 appropriate chapter, a BIG FAT note should be here about this though and
80 what should be here
[all …]
/Linux-v5.15/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/
Dpar_io.txt4 The node should reside in the "soc" node of the tree. For each
5 device that using parallel I/O ports, a child node should be created.
10 - device_type : should be "par_io".
25 Note that "par_io" nodes are obsolete, and should not be used for
26 the new device trees. Instead, each Par I/O bank should be represented
30 - #gpio-cells : should be "2".
31 - compatible : should be "fsl,<chip>-qe-pario-bank",
/Linux-v5.15/Documentation/devicetree/bindings/mtd/
Dmxic-nand.txt5 - compatible: should be "mxic,multi-itfc-v009-nand-controller"
6 - reg: should contain 1 entry for the registers
7 - #address-cells: should be set to 1
8 - #size-cells: should be set to 0
10 - clock-names: should contain "ps", "send" and "send_dly"
11 - clocks: should contain 3 phandles for the "ps", "send" and
/Linux-v5.15/Documentation/devicetree/bindings/regulator/
Dpbias-regulator.txt5 - should be "ti,pbias-dra7" for DRA7
6 - should be "ti,pbias-omap2" for OMAP2
7 - should be "ti,pbias-omap3" for OMAP3
8 - should be "ti,pbias-omap4" for OMAP4
9 - should be "ti,pbias-omap5" for OMAP5
13 - regulator-name : should be
/Linux-v5.15/Documentation/devicetree/bindings/media/
Dexynos-fimc-lite.txt5 - compatible : should be one of:
11 - interrupts : should contain FIMC-LITE interrupt;
12 - clocks : FIMC LITE gate clock should be specified in this property.
13 - clock-names : should contain "flite" entry.
15 Each FIMC device should have an alias in the aliases node, in the form of
/Linux-v5.15/Documentation/devicetree/bindings/powerpc/fsl/
Dmpc512x_lpbfifo.txt4 - compatible: should be "fsl,mpc512x-lpbfifo";
5 - reg: should contain the offset and length of SCLPC register set;
6 - interrupts: should contain the interrupt specifier for SCLPC; syntax of an
8 - dmas: should contain the DMA specifier for SCLPC as described at
10 - dma-names: should be "rx-tx";
/Linux-v5.15/Documentation/devicetree/bindings/clock/
Doxnas,stdclk.txt8 - compatible: For OX810SE, should be "oxsemi,ox810se-stdclk"
9 For OX820, should be "oxsemi,ox820-stdclk"
12 Parent node should have the following properties :
13 - compatible: For OX810SE, should be
15 For OX820, should be
/Linux-v5.15/Documentation/devicetree/bindings/arm/
Dsp810.txt9 should be: "arm,sp810", "arm,primecell"
16 should be: "refclk", "timclk", "apb_pclk"
22 should be: <1>
25 should be: "timerclken0", "timerclken1", "timerclken2", "timerclken3"
28 should be: clock specifier for each output clock of this
32 should be: phandle of input clock listed in clocks
/Linux-v5.15/scripts/kconfig/tests/auto_submenu/
DKconfig12 This depends on A, so should be a submenu of A.
19 This should be a submenu of A0.
26 This should line up with A0.
32 Choice should become a submenu as well.
51 This depends on A, but not a consecutive item, so can/should not
/Linux-v5.15/Documentation/devicetree/bindings/reset/
Doxnas,reset.txt8 - compatible: For OX810SE, should be "oxsemi,ox810se-reset"
9 For OX820, should be "oxsemi,ox820-reset"
12 Parent node should have the following properties :
13 - compatible: For OX810SE, should be :
15 For OX820, should be :
/Linux-v5.15/Documentation/devicetree/bindings/display/imx/
Dfsl-imx-drm.txt29 - reg: should be register base and length as documented in the
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"
73 - interrupts: should contain the PRE interrupt
74 - fsl,iram: phandle pointing to the mmio-sram device node, that should be
92 - compatible: should be "fsl,imx6qp-prg"
93 - reg: should be register base and length as documented in the
[all …]
/Linux-v5.15/Documentation/devicetree/bindings/rtc/
Datmel,at91sam9-rtc.txt4 - compatible: should be one of the following:
7 - reg: should encode the memory region of the RTT controller
9 - clocks: should contain the 32 KHz slow clk that will drive the RTT block.
10 - atmel,rtt-rtc-time-reg: should encode the GPBR register used to store
12 The first cell should point to the GPBR node and the second one
/Linux-v5.15/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 …]
/Linux-v5.15/Documentation/admin-guide/device-mapper/
Ddm-init.rst34 The dm line should be equivalent to the one used by the dmsetup tool with the
45 `cache` constrained, userspace should verify cache device
48 `era` constrained, userspace should verify metadata device
51 `log-writes` constrained, userspace should verify metadata device
52 `mirror` constrained, userspace should verify main/mirror device
53 `raid` constrained, userspace should verify metadata device
54 `snapshot` constrained, userspace should verify src/dst device
56 `snapshot-merge` constrained, userspace should verify src/dst device
58 `switch` constrained, userspace should verify dev path
62 `writecache` constrained, userspace should verify cache device
/Linux-v5.15/drivers/staging/media/imx/
DTODO7 instead the CSI subdev should call its neighbor's g_mbus_config op
8 (which should be propagated if necessary) to get this info. However
14 operation which should be used to avoid parsing the remote endpoint
20 link_notify callback when the pipeline is modified. This feature should be
21 removed, userspace should use the subdev-based userspace API instead.
25 connected subdev should be removed.
/Linux-v5.15/Documentation/virt/kvm/
Dreview-checklist.rst10 2. Patches should be against kvm.git master branch.
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
23 7. Emulator changes should be accompanied by unit tests for qemu-kvm.git
26 8. Changes should be vendor neutral when possible. Changes to common code
/Linux-v5.15/Documentation/devicetree/bindings/mfd/
Dsamsung,exynos5433-lpass.txt6 - reg : should contain the LPASS top SFR region location
8 - clock-names : should contain following required clocks: "sfr0_ctrl"
9 - clocks : should contain clock specifiers of all clocks, which
12 - #address-cells : should be 1
13 - #size-cells : should be 1
16 Each IP block of the Low Power Audio Subsystem should be specified as
/Linux-v5.15/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 …]

12345678910>>...119