| /openbmc/linux/Documentation/devicetree/bindings/powerpc/nintendo/ |
| H A D | wii.txt | 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"
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 …]
|
| H A D | gamecube.txt | 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
64 - compatible : should be "nintendo,flipper-aram"
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-pylint/ |
| H A D | 0001-Adjust-test-expectations-for-ptest.patch | 18 …wrong-import-order:15:0:15:15::"standard import ""datetime"" should be placed before third party i…
19 …wrong-import-order:18:0:18:22::"third party import ""totally_missing"" should be placed before loc…
20 …wrong-import-order:20:0:20:14::"third party import ""astroid"" should be placed before local impor…
21 -wrong-import-order:22:0:22:22::"first party import ""pylint.checkers"" should be placed before loc…
22 -wrong-import-order:23:0:23:25::"first party import ""pylint.config"" should be placed before local…
23 -wrong-import-order:24:0:24:17::"first party import ""pylint.sys"" should be placed before local im…
24 -wrong-import-order:25:0:25:28::"first party import ""pylint.pyreverse"" should be placed before lo…
25 -wrong-import-order:30:0:30:40::"third party import ""six.moves.urllib.parse.quote"" should be plac…
26 -wrong-import-order:31:0:31:23::"first party import ""pylint.constants"" should be placed before lo…
27 -wrong-import-order:32:0:32:19::"standard import ""re"" should be placed before third party imports…
[all …]
|
| /openbmc/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.
|
| /openbmc/linux/scripts/kconfig/tests/preprocess/escape/ |
| H A D | Kconfig | 23 # 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.
|
| /openbmc/openbmc/meta-nuvoton/recipes-bsp/images/npcm7xx-igps/ |
| H A D | 0001-Adjust-paths-for-use-with-Bitbake.patch | 28 …ileContent'>output_binaries/BootBlockAndHeader.bin</content> <!-- content the user should fill -->
29 + <content format='FileContent'>Poleg_bootblock.bin.full</content> <!-- content the user should f…
40 …t='FileContent'>output_binaries/UbootAndHeader.bin</content> <!-- content the user should fill -->
41 + <content format='FileContent'>u-boot.bin.full</content> <!-- content the user should fill -->
53 - <content format='FileSize'>inputs/Poleg_bootblock.bin</content> <!-- content the user should fil…
54 + <content format='FileSize'>Poleg_bootblock.bin</content> <!-- content the user should fill -->
65 - <content format='FileContent'>inputs/Poleg_bootblock.bin</content> <!-- content the user should…
66 + <content format='FileContent'>Poleg_bootblock.bin</content> <!-- content the user should fill -…
78 - <content format='FileSize'>inputs/Poleg_bootblock.bin</content> <!-- content the user should fil…
79 + <content format='FileSize'>Poleg_bootblock.bin</content> <!-- content the user should fill -->
[all …]
|
| /openbmc/docs/ |
| H A D | cpp-style-and-conventions.md | 15 1. Code should be clear and concise.
16 2. Code should be written with modern practices.
17 3. Code should be performant.
19 ### Code should be clear and concise
24 for the writer. Solutions should avoid tricks that detract from the clarity of
31 When there is a conflict between clarity and conciseness, clarity should win
34 ### Code should be written with modern practices
37 standards. Today, that means all C++ code should be compiled using C++23
55 ### Code should be performant.
108 2. Implementers should include the lowest level header required to solve the
[all …]
|
| /openbmc/linux/Documentation/misc-devices/ |
| H A D | pci-endpoint-test.rst | 7 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
|
| /openbmc/linux/Documentation/driver-api/80211/ |
| H A D | mac80211.rst | 5 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 …]
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| H A D | par_io.txt | 4 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",
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | pbias-regulator.txt | 5 - 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
|
| /openbmc/linux/Documentation/devicetree/bindings/mtd/ |
| H A D | mxic-nand.txt | 5 - 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
|
| /openbmc/u-boot/drivers/power/ |
| H A D | Kconfig | 100 On A10(s) / A13 / A20 boards dcdc2 is VDD-CPU and should be 1.4V.
101 On A31 boards dcdc2 is used for VDD-GPU and should be 1.2V.
102 On A23/A33 boards dcdc2 is used for VDD-SYS and should be 1.1V.
104 On A83T boards dcdc2 is used for VDD-CPUA(cluster 0) and should be 0.9V.
105 On R40 boards dcdc2 is VDD-CPU and should be 1.1V
119 should be 1.25V.
120 On A10s boards with an axp152 dcdc3 is VCC-DRAM and should be 1.5V.
121 On A23 / A31 / A33 boards dcdc3 is VDD-CPU and should be 1.2V.
122 On A80 boards dcdc3 is used for VDD-CPUA(cluster 0) and should be 0.9V.
123 On A83T boards dcdc3 is used for VDD-CPUB(cluster 1) and should be 0.9V.
[all …]
|
| /openbmc/bmcweb/ |
| H A D | DEVELOPING.md | 7 As OpenBMC is intended to be deployed on an embedded system, care should be
11 - Binaries and static files should take up < 1MB of filesystem size
12 - Memory usage should remain below 10MB at all times
13 - Application startup time should be less than 1 second on target hardware
18 Care should be taken to ensure that all code is written to be asynchronous in
21 should be avoided if possible, and instead use async tasks within boost::asio.
25 Secure coding practices should be followed in all places in the webserver
31 - All input from outside the application is considered untrusted, and should be
35 - Where applicable, noexcept methods should be preferred to methods that use
37 - Explicitly bounded types should be preferred over implicitly bounded types
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.drivers.eth | 4 should be implemented this way. All new drivers should be written against the
33 Keep in mind that you should code the driver to avoid storing state in global
35 Any such information that is specific to an interface should be stored in a
102 need to pass more/less arguments, that's fine. You should also add the
105 The return value for this function should be as follows:
110 xxx_register(). This is the old naming convention and should be avoided as it
113 Other than locating the MAC address in dedicated hardware storage, you should
132 and/or PHY, and waiting for the link to autonegotiate. You should also take
138 size is specified by length (in bytes). You should not return until the
139 transmission is complete, and you should leave the state such that the send
[all …]
|
| /openbmc/linux/Documentation/driver-api/firmware/ |
| H A D | firmware-usage-guidelines.rst | 5 Users switching to a newer kernel should *not* have to install newer
10 Drivers that use firmware from linux-firmware should follow the rules in
19 specific name, and just the major version. The firmware version should
22 fixes/changes. The firmware files in linux-firmware should be
32 bumps should not introduce new features that newer kernels depend on
38 should be updated with the security fix. The kernel patches should
40 is fixed. All communications around security fixes should point at
42 deprecating old major versions, then this should only be done as a
|
| /openbmc/u-boot/doc/device-tree-bindings/serial/ |
| H A D | omap_serial.txt | 4 - compatible : should be "ti,omap2-uart" for OMAP2 controllers
5 - compatible : should be "ti,omap3-uart" for OMAP3 controllers
6 - compatible : should be "ti,omap4-uart" for OMAP4 controllers
7 - compatible : should be "ti,am4372-uart" for AM437x controllers
8 - compatible : should be "ti,am3352-uart" for AM335x controllers
9 - compatible : should be "ti,dra742-uart" for DRA7x controllers
|
| /openbmc/linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | mpc512x_lpbfifo.txt | 4 - 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";
|
| /openbmc/u-boot/scripts/kconfig/tests/auto_submenu/ |
| H A D | Kconfig | 10 This depends on A, so should be a submenu of A.
17 This should be a submenu of A0.
24 This should line up with A0.
30 Choice should become a submenu as well.
49 This depends on A, but not a consecutive item, so can/should not
|
| /openbmc/linux/Documentation/devicetree/bindings/display/imx/ |
| H A D | fsl-imx-drm.txt | 29 - 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 …]
|
| /openbmc/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 …]
|
| /openbmc/linux/scripts/kconfig/tests/auto_submenu/ |
| H A D | Kconfig | 12 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
|
| /openbmc/openbmc/meta-google/dynamic-layers/nuvoton-layer/recipes-bsp/images/npcm7xx-igps/ |
| H A D | 0001-Set-FIU0_DRD_CFG-and-FIU_Clk_divider-for-gbmc-hoth.patch | 24 - <content format='32bit'>0x030011BB</content> <!-- content the user should fill -->
25 + <content format='32bit'>0x0300100B</content> <!-- content the user should fill -->
33 - <content format='bytes'>4</content> <!-- content the user should fill -->
34 + <content format='bytes'>10</content> <!-- content the user should fill -->
46 - <content format='32bit'>0x030111BC</content> <!-- content the user should fill 0x0…
47 + <content format='32bit'>0x0300100B</content> <!-- content the user should fill 0x0…
|
| /openbmc/phosphor-dbus-interfaces/ |
| H A D | requirements.md | 21 Arbitrary strings should only be utilized for human consumption and never parsed
23 as "... can be shown in user interfaces but this field should not be used for
33 enumerations. In those cases a property may be a string, but should specify that
64 associations should be considered to have a "primary" and "secondary" end, which
69 ### Peer associations should be named with hierarchy names
73 the entity in the dbus path hierarchy. Accordingly, the association should be
82 ### Directed associations should not codify type
84 The end-point names of an association should not codify the types of the
90 ### Directed associations should be named with participle verbs
92 The primary relationship should be a verb with a Present Participle tense
[all …]
|
| /openbmc/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 …]
|