Home
last modified time | relevance | path

Searched full:design (Results 1 – 25 of 988) sorted by relevance

12345678910>>...40

/Linux-v5.10/Documentation/admin-guide/media/
Ddvb-usb-dib0700-cardlist.rst29 * - 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
47 * - DiBcom STK807xPVR reference design
[all …]
Dsaa7134-cardlist.rst22 - 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.10/Documentation/devicetree/bindings/power/supply/
Dbq27xxx.yaml64 - 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.
84 voltage-min-design-microvolt = <3200000>;
85 energy-full-design-microwatt-hours = <5290000>;
86 charge-full-design-microamp-hours = <1430000>;
Dbattery.yaml40 voltage-min-design-microvolt:
43 voltage-max-design-microvolt:
46 energy-full-design-microwatt-hours:
47 description: battery design energy
49 charge-full-design-microamp-hours:
50 description: battery design capacity
136 voltage-min-design-microvolt = <3200000>;
137 voltage-max-design-microvolt = <4200000>;
138 energy-full-design-microwatt-hours = <5290000>;
139 charge-full-design-microamp-hours = <1430000>;
Dingenic,battery.yaml35 - 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>;
/Linux-v5.10/Documentation/locking/
Dindex.rst11 lockdep-design
14 mutex-design
15 rt-mutex-design
19 ww-mutex-design
/Linux-v5.10/Documentation/RCU/
Dindex.rst28 Design/Memory-Ordering/Tree-RCU-Memory-Ordering
29 Design/Expedited-Grace-Periods/Expedited-Grace-Periods
30 Design/Requirements/Requirements
31 Design/Data-Structures/Data-Structures
/Linux-v5.10/Documentation/networking/devlink/
Dnfp.rst35 - 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
Dbnxt.rst56 - Part number identifying the board design
59 - ASIC design identifier
62 - ASIC design revision
Ddevlink-info.rst57 Versions in this section identify the device design. For example,
127 Unique identifier of the board design.
132 Board design revision.
137 ASIC design identifier.
142 ASIC design revision/stepping.
/Linux-v5.10/Documentation/driver-api/driver-model/
Ddesign-patterns.rst2 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.10/arch/arm/mach-orion5x/
DKconfig37 bool "Marvell Orion-NAS Reference Design"
44 bool "Marvell Orion-NAS Reference Design (Flattened Device Tree)"
151 bool "Marvell Orion-VoIP GE Reference Design"
157 bool "Marvell Orion-VoIP FXO Reference Design"
163 bool "Marvell Orion-1-90 AP GE Reference Design"
/Linux-v5.10/Documentation/trace/
Dindex.rst8 ftrace-design
23 histogram-design
27 ring-buffer-design
/Linux-v5.10/Documentation/power/regulator/
Ddesign.rst2 Regulator API design notes
6 of the design considerations which impact the regulator API design.
/Linux-v5.10/Documentation/arm/
Dixp4xx.rst21 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.10/include/net/
Dethoc.h5 * Copyright (C) 2008-2009 Avionic Design GmbH
7 * Written by Thierry Reding <thierry.reding@avionic-design.de>
/Linux-v5.10/Documentation/scheduler/
Dindex.rst13 sched-design-CFS
17 sched-nice-design
/Linux-v5.10/drivers/staging/gs_fpgaboot/
DREADME10 3. DESIGN
22 used in various applications. Hardware design needs to programmed through
26 3. DESIGN
/Linux-v5.10/Documentation/userspace-api/
Dunshare.rst6 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.10/drivers/net/usb/
DKconfig229 * Broadcom Cable Modem (reference design)
266 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
267 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
268 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
269 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
373 on this design: one NetChip 1080 chip and supporting logic,
433 based on this design, which supports USB 2.0 high speed.
441 based on this design. Note that AnchorChips is now a
451 based on this design: two NetChip 2890 chips and an Atmel
/Linux-v5.10/arch/arm/mach-mv78xx0/
DKconfig23 bool "Marvell RD-78x00-mASA Reference Design"
26 Marvell RD-78x00-mASA Reference Design.
/Linux-v5.10/drivers/media/usb/dvb-usb/
DKconfig124 tristate "Conexant USB2.0 hybrid reference design support"
142 Say Y here to support the Conexant USB2.0 hybrid reference design.
145 reference design").
152 bool "Analog support for the Conexant USB2.0 hybrid reference design"
159 USB2.0 hybrid reference design.
/Linux-v5.10/Documentation/devicetree/bindings/sound/
Dfsl,ssi.txt58 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.10/drivers/media/usb/dvb-usb-v2/
Dec168.c337 &ec168_props, "E3C EC168 reference design", NULL)},
339 &ec168_props, "E3C EC168 reference design", NULL)},
341 &ec168_props, "E3C EC168 reference design", NULL)},
343 &ec168_props, "E3C EC168 reference design", NULL)},
345 &ec168_props, "E3C EC168 reference design", NULL)},
/Linux-v5.10/Documentation/filesystems/
Dinotify.rst18 What is the design decision behind not tying the watch to the open fd of
29 What is the design decision behind using an-fd-per-instance as opposed to
38 spaces is thus sensible. The current design is what user-space developers

12345678910>>...40