Searched full:design (Results 1 – 25 of 926) sorted by relevance
12345678910>>...38
| /Linux-v5.4/Documentation/devicetree/bindings/power/supply/ |
| D | battery.txt | 18 - voltage-min-design-microvolt: drained battery voltage
19 - voltage-max-design-microvolt: fully charged battery voltage
20 - energy-full-design-microwatt-hours: battery design energy
21 - charge-full-design-microamp-hours: battery design capacity
51 voltage-min-design-microvolt = <3200000>;
52 voltage-max-design-microvolt = <4200000>;
53 energy-full-design-microwatt-hours = <5290000>;
54 charge-full-design-microamp-hours = <1430000>;
|
| D | bq27xxx.txt | 37 + energy-full-design-microwatt-hours
38 + charge-full-design-microamp-hours
39 + voltage-min-design-microvolt
40 Both or neither of the *-full-design-*-hours properties must be set.
47 voltage-min-design-microvolt = <3200000>;
48 energy-full-design-microwatt-hours = <5290000>;
49 charge-full-design-microamp-hours = <1430000>;
|
| D | ingenic,battery.txt | 13 - voltage-min-design-microvolt: Drained battery voltage.
14 - voltage-max-design-microvolt: Fully charged battery voltage.
22 voltage-min-design-microvolt = <3600000>;
23 voltage-max-design-microvolt = <4200000>;
|
| /Linux-v5.4/Documentation/locking/ |
| D | index.rst | 10 lockdep-design
13 mutex-design
14 rt-mutex-design
17 ww-mutex-design
|
| /Linux-v5.4/Documentation/networking/ |
| D | devlink-info-versions.rst | 10 Unique identifier of the board design.
15 Board design revision.
20 ASIC design identifier.
25 ASIC design revision.
|
| /Linux-v5.4/Documentation/driver-api/driver-model/ |
| D | design-patterns.rst | 2 Device Driver Design Patterns
5 This document describes a few common design patterns found in device drivers.
7 conform to these design patterns.
21 The most common way to achieve this is to use the state container design
102 The design pattern is the same for an hrtimer or something similar that will
|
| /Linux-v5.4/arch/arm/mach-orion5x/ |
| D | Kconfig | 39 bool "Marvell Orion-NAS Reference Design"
46 bool "Marvell Orion-NAS Reference Design (Flattened Device Tree)"
153 bool "Marvell Orion-VoIP GE Reference Design"
159 bool "Marvell Orion-VoIP FXO Reference Design"
165 bool "Marvell Orion-1-90 AP GE Reference Design"
|
| /Linux-v5.4/Documentation/power/regulator/ |
| D | design.rst | 2 Regulator API design notes
6 of the design considerations which impact the regulator API design.
|
| /Linux-v5.4/Documentation/arm/ |
| D | ixp4xx.rst | 21 http://developer.intel.com/design/network/products/npfamily/ixp4xx.htm
48 http://developer.intel.com/design/network/products/npfamily/ixp425.htm
106 The ADI Coyote platform is reference design for those building
122 http://www.intel.com/design/network/products/npfamily/ixdpg425.htm
129 http://www.intel.com/design/network/products/npfamily/ixdp465.htm
|
| /Linux-v5.4/include/net/ |
| D | ethoc.h | 5 * Copyright (C) 2008-2009 Avionic Design GmbH
7 * Written by Thierry Reding <thierry.reding@avionic-design.de>
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | index.rst | 13 sched-design-CFS
16 sched-nice-design
|
| /Linux-v5.4/drivers/staging/gs_fpgaboot/ |
| D | README | 10 3. DESIGN
22 used in various applications. Hardware design needs to programmed through
26 3. DESIGN
|
| /Linux-v5.4/Documentation/userspace-api/ |
| D | unshare.rst | 6 be used, its interface specification, design, implementation and
20 6) High Level Design
21 7) Low Level Design
101 extensively in the beginning. However, with proper design and code
119 If and when new context flags are added, unshare() design should allow
184 6) High Level Design
231 7) Low Level Design
|
| /Linux-v5.4/drivers/net/usb/ |
| D | Kconfig | 229 * Broadcom Cable Modem (reference design)
265 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
266 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
267 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
268 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
370 on this design: one NetChip 1080 chip and supporting logic,
430 based on this design, which supports USB 2.0 high speed.
438 based on this design. Note that AnchorChips is now a
448 based on this design: two NetChip 2890 chips and an Atmel
|
| /Linux-v5.4/arch/arm/mach-mv78xx0/ |
| D | Kconfig | 23 bool "Marvell RD-78x00-mASA Reference Design"
26 Marvell RD-78x00-mASA Reference Design.
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | inotify.txt | 12 Q: What is the design decision behind not tying the watch to the open fd of
21 Q: What is the design decision behind using an-fd-per-instance as opposed to
29 spaces is thus sensible. The current design is what user-space developers
|
| /Linux-v5.4/drivers/media/usb/dvb-usb/ |
| D | Kconfig | 123 tristate "Conexant USB2.0 hybrid reference design support"
141 Say Y here to support the Conexant USB2.0 hybrid reference design.
144 reference design").
151 bool "Analog support for the Conexant USB2.0 hybrid reference design"
157 USB2.0 hybrid reference design.
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | saa7134-cardlist.rst | 22 - Proteus Pro [philips reference design]
262 - Philips TOUGH DVB-T reference design
294 - Philips EUROPA V3 reference design
342 - Philips Tiger reference design
454 - Philips Tiger - S Reference design
550 - NXP Snake DVB-S reference design
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | fsl,ssi.txt | 58 design. See the notes below.
62 by SOC design. See the notes below.
79 purpose of these two properties is to represent this hardware design.
|
| /Linux-v5.4/Documentation/timers/ |
| D | highres.rst | 2 High resolution timers and dynamic ticks design notes
15 design of the Linux time(r) system before hrtimers and other building blocks
21 The design contains the following basic building blocks:
80 architecture. Another implication of the current design is that it is necessary
170 a support function. The design allows the system to utilize separate per-CPU
|
| /Linux-v5.4/Documentation/devicetree/bindings/ |
| D | writing-bindings.txt | 3 This is a list of common review feedback items focused on binding design. With
10 Overall design
|
| /Linux-v5.4/Documentation/target/ |
| D | tcmu-design.rst | 2 TCM Userspace Design
8 1) TCM Userspace Design
11 c) Design constraints
26 TCM Userspace Design
32 This document describes the design.
82 Design constraints
|
| /Linux-v5.4/drivers/hwmon/ |
| D | hwmon-vid.c | 23 * For VRM 8.4 to 9.1, "VRM x.y DC-DC Converter Design Guidelines",
26 * For VRD 10.0 and up, "VRD x.y Design Guide",
52 * http://www.intel.com/design/intarch/pentiumm/docs_pentiumm.htm
57 * http://www.intel.com/design/mobile/datashts/309221.htm
60 * http://www.intel.com/design/processor/applnots/313214.htm
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | armada-388-rd.dts | 3 * Device Tree file for Marvell Armada 388 Reference Design board
16 model = "Marvell Armada 385 Reference Design";
|
| /Linux-v5.4/Documentation/devicetree/bindings/spi/ |
| D | nvidia,tegra114-spi.txt | 30 Tap values vary based on the platform design trace lengths from Tegra SPI
35 Tap values vary based on the platform design trace lengths from Tegra SPI
|
12345678910>>...38
