Searched full:design (Results 1 – 25 of 261) sorted by relevance
1234567891011
| /Documentation/devicetree/bindings/power/supply/ |
| 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 | 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 | 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>;
|
| /Documentation/locking/ |
| D | index.rst | 10 lockdep-design
13 mutex-design
14 rt-mutex-design
17 ww-mutex-design
|
| /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.
|
| D | netif-msg.txt | 5 The design of the network interface message level setting.
9 The design of the debugging message interface was guided and
|
| /Documentation/power/regulator/ |
| D | design.rst | 2 Regulator API design notes
6 of the design considerations which impact the regulator API design.
|
| /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
|
| D | index.rst | 11 design-patterns
|
| /Documentation/scheduler/ |
| D | index.rst | 13 sched-design-CFS
16 sched-nice-design
|
| /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
|
| /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
|
| /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
|
| /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.
|
| /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
|
| /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
|
| /Documentation/target/ |
| D | index.rst | 10 tcmu-design
|
| /Documentation/usb/ |
| D | index.rst | 29 wusb-design-overview
|
| /Documentation/devicetree/bindings/mfd/ |
| D | qriox.txt | 4 the kmp204x design.
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | megachips-stdpxxxx-ge-b850v3-fw.txt | 10 design. The result is that, in this design, neither the STDP4028 nor the
|
| /Documentation/trace/ |
| D | index.rst | 8 ftrace-design
|
| /Documentation/devicetree/bindings/pci/ |
| D | cdns,cdns-pcie-host.txt | 25 - vendor-id: The PCI vendor ID (16 bits, default is design dependent)
26 - device-id: The PCI device ID (16 bits, default is design dependent)
|
| /Documentation/power/ |
| D | index.rst | 36 regulator/design
|
| /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
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-uids | 14 Documentation/scheduler/sched-design-CFS.rst
|
1234567891011