/openbmc/linux/Documentation/admin-guide/media/ |
H A D | dvb-usb-dib0700-cardlist.rst | 29 * - DiBcom NIM7090 reference design 31 * - DiBcom NIM8096MD reference design 33 * - DiBcom NIM9090MD reference design 35 * - DiBcom STK7070P reference design 37 * - DiBcom STK7070PD reference design 39 * - DiBcom STK7700D reference design 41 * - DiBcom STK7700P reference design 43 * - DiBcom STK7770P reference design 45 * - DiBcom STK807xP reference design 53 * - DiBcom STK9090M reference design [all …]
|
/openbmc/docs/designs/ |
H A D | README.md | 1 This is a directory of design documents. 3 Newly authored design documents are encouraged to follow the 4 [design document template](design-template.md).
|
H A D | design-template.md | 7 - Not all new features need a design document. If a feature can be contributed 9 areas, it doesn't need a design discussion and documentation. 17 design proposals compel the reviewers agree with the proposal's conclusions. 23 - You should get your design reviewed and merged before writing your code. 25 may learn of new requirements during the design review process that could 46 "design" 50 # Example design - this is the design title 74 glossary if necessary. Note: this is background; do not write about your design, 98 (2 paragraphs) Include alternate design ideas here which you are leaning away 99 from. Elaborate on why a design was considered and why the idea was rejected. [all …]
|
H A D | cper-records.md | 33 design, and passes the OpenBMC CI tests currently. This is the proposed branch 56 While this design fits into a much more elaborate design alluded to in the 62 might not meet all design goals for all contributors, having a common 65 Future design docs (or amendments to this design) will iterate on implementing 66 more of the design referenced in this [CPER specification][arm_sbmr], for common 68 the quality up to standards is the initial goal of this design. 72 Rewrite libcper decoding from a new design point. While this is certainly 85 - Which repositories are expected to be modified to execute this design? 100 design is complete.
|
/openbmc/linux/Documentation/locking/ |
H A D | index.rst | 11 lockdep-design 14 mutex-design 15 rt-mutex-design 19 ww-mutex-design
|
/openbmc/linux/Documentation/devicetree/bindings/power/supply/ |
H A D | bq27xxx.yaml | 64 - energy-full-design-microwatt-hours 65 - charge-full-design-microamp-hours 66 - voltage-min-design-microvolt 67 Both or neither of the *-full-design-*-hours properties must be set. 80 voltage-min-design-microvolt = <3200000>; 81 energy-full-design-microwatt-hours = <5290000>; 82 charge-full-design-microamp-hours = <1430000>;
|
H A D | battery.yaml | 54 voltage-min-design-microvolt: 57 voltage-max-design-microvolt: 60 energy-full-design-microwatt-hours: 61 description: battery design energy 63 charge-full-design-microamp-hours: 64 description: battery design capacity 152 voltage-min-design-microvolt = <3200000>; 153 voltage-max-design-microvolt = <4200000>; 154 energy-full-design-microwatt-hours = <5290000>; 155 charge-full-design-microamp-hours = <1430000>;
|
H A D | ingenic,battery.yaml | 35 - voltage-min-design-microvolt: drained battery voltage, 36 - voltage-max-design-microvolt: fully charged battery voltage. 52 voltage-min-design-microvolt = <3600000>; 53 voltage-max-design-microvolt = <4200000>;
|
/openbmc/linux/Documentation/translations/zh_CN/locking/ |
H A D | index.rst | 17 mutex-design 23 * lockdep-design 26 * rt-mutex-design 29 * ww-mutex-design
|
/openbmc/linux/Documentation/trace/ |
H A D | index.rst | 8 ftrace-design 25 histogram-design 31 ring-buffer-design
|
/openbmc/linux/Documentation/networking/devlink/ |
H A D | nfp.rst | 35 - Part number identifying the board design 38 - Revision of the board design 41 - Vendor of the board design 44 - Model name of the board design
|
/openbmc/entity-manager/configurations/ |
H A D | VENDORS.md | 7 In some cases a company might design a component (such as a network card), 11 when multiple companies are involved in the chain between design and end-user. 16 1. A company which primarily initiates and oversees the design, manufacture and 29 3. When one company primarily oversees the design but other companies 31 the company that primarily oversaw the design of the component would be the
|
/openbmc/u-boot/board/avionic-design/tec/ |
H A D | MAINTAINERS | 2 M: Alban Bedel <alban.bedel@avionic-design.de> 4 F: board/avionic-design/tec/
|
/openbmc/u-boot/board/avionic-design/plutux/ |
H A D | MAINTAINERS | 2 M: Alban Bedel <alban.bedel@avionic-design.de> 4 F: board/avionic-design/plutux/
|
/openbmc/u-boot/arch/arm/mach-tegra/tegra20/ |
H A D | Kconfig | 49 source "board/avionic-design/medcom-wide/Kconfig" 51 source "board/avionic-design/plutux/Kconfig" 53 source "board/avionic-design/tec/Kconfig"
|
/openbmc/linux/arch/arm64/boot/dts/rockchip/ |
H A D | rk3326-odroid-go2.dts | 42 charge-full-design-microamp-hours = <3000000>; 47 voltage-max-design-microvolt = <4100000>; 48 voltage-min-design-microvolt = <3500000>;
|
/openbmc/linux/arch/arm64/boot/dts/qcom/ |
H A D | sdm845-oneplus-enchilada.dts | 20 charge-full-design-microamp-hours = <3300000>; 21 voltage-min-design-microvolt = <3400000>; 22 voltage-max-design-microvolt = <4400000>;
|
H A D | sdm845-oneplus-fajita.dts | 20 charge-full-design-microamp-hours = <3700000>; 21 voltage-min-design-microvolt = <3400000>; 22 voltage-max-design-microvolt = <4400000>;
|
/openbmc/u-boot/board/avionic-design/tec-ng/ |
H A D | MAINTAINERS | 2 M: Alban Bedel <alban.bedel@avionic-design.de> 4 F: board/avionic-design/tec-ng/
|
/openbmc/u-boot/board/avionic-design/medcom-wide/ |
H A D | MAINTAINERS | 2 M: Alban Bedel <alban.bedel@avionic-design.de> 4 F: board/avionic-design/medcom-wide/
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/VirtualMedia/ |
H A D | README.md | 4 [openbmc/docs/designs/VirtualMedia.md][design]. 6 [design]: https://github.com/openbmc/docs/blob/master/designs/VirtualMedia.md
|
/openbmc/linux/Documentation/translations/zh_CN/mm/damon/ |
H A D | index.rst | 17 (该核心机制详见(Documentation/translations/zh_CN/mm/damon/design.rst)) 31 design
|
/openbmc/linux/Documentation/scheduler/ |
H A D | index.rst | 13 sched-design-CFS 19 sched-nice-design
|
/openbmc/linux/Documentation/power/regulator/ |
H A D | design.rst | 2 Regulator API design notes 6 of the design considerations which impact the regulator API design.
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/BIOSConfig/ |
H A D | README.md | 9 Please refer to the [design][design] for more details. 44 [design]:
|