Searched full:own (Results 1 – 25 of 521) sorted by relevance
12345678910>>...21
| /Documentation/hwmon/ |
| D | adm1031.rst | 33 They sense their own temperature as well as the temperature of up to one
39 Each temperature channel has its own high and low limits, plus a critical
43 two. Each fan channel has its own low speed limit.
|
| D | lm95245.rst | 29 the temperature of a remote diode as well as its own temperature.
38 Each sensor has its own critical limit. Additionally, there is a relative
|
| D | lm95234.rst | 30 or four (LM95234) remote diodes as well as its own temperature.
40 Each sensor has its own maximum limit, but the hysteresis is common to all
|
| D | lm83.rst | 29 The LM83 is a digital temperature sensor. It senses its own temperature as
80 (actually measuring the LM83's own temperature), one is used for the
91 Each sensor has its own high limit, but the critical limit is common to
|
| D | max6642.rst | 23 The MAX6642 is a digital temperature sensor. It senses its own temperature as
|
| /Documentation/riscv/ |
| D | patch-acceptance.rst | 24 course, maintain their own Linux kernel trees that contain code for
28 their own custom extensions. These custom extensions aren't required
34 (Implementors, may, of course, maintain their own Linux kernel trees
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-detect.rst | 37 - The image is divided into a grid, each cell with its own motion
41 - The image is divided into a grid, each cell with its own region
43 should be used. Each region has its own thresholds. How these
|
| /Documentation/mips/ |
| D | ingenic-tcu.rst | 18 - Each one of the TCU channels has its own clock, which can be reparented to three
45 own interrupt line; channels 2-7 share the last interrupt line.
46 - On JZ4725B, channel 0 has its own interrupt; channels 1-5 share one
48 - on newer SoCs (JZ4750 and above), channel 5 has its own interrupt;
|
| /Documentation/admin-guide/ |
| D | edid.rst | 19 - A KVM sends its own EDID data instead of querying the connected monitor.
39 If you want to create your own EDID file, copy the file 1024x768.S,
40 replace the settings with your own data and add a new target to the
|
| /Documentation/networking/ |
| D | tc-actions-env-rules.rst | 18 someone else is referencing the skb. After that you "own" the skb.
20 3) Dropping packets you don't own is a no-no. You simply return
|
| D | mac80211-injection.rst | 40 legacy rate for the transmission (only for devices without own rate control)
44 HT rate for the transmission (only for devices without own rate control).
60 without own rate control). Also other fields are parsed
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-bdi | 14 non-block filesystems which provide their own BDI, such as NFS
24 filesystems which do not provide their own BDI.
|
| D | sysfs-kernel-btf | 14 Read-only binary attribute exposing kernel's own BTF type
|
| /Documentation/driver-api/usb/ |
| D | typec.rst | 30 Every port will be presented as its own device under /sys/class/typec/. The
33 When connected, the partner will be presented also as its own device under
39 The cable and the two plugs on it may also be optionally presented as their own
47 Alternate Mode SVID will have their own device describing them. Note that the
51 Every mode that is supported will have its own group under the Alternate Mode
110 The plugs are represented as their own devices. The cable is registered first,
172 own functions, but the registration will always return a handle to struct
201 own logical components: "mux" for the mode and "switch" for the orientation.
|
| /Documentation/devicetree/bindings/phy/ |
| D | nvidia,tegra20-usb-phy.txt | 11 - The PHY's own register set.
18 - reg: The clock needed to access the PHY's own registers. This is the
31 - usb: The PHY's own reset signal.
|
| /Documentation/process/ |
| D | 6.Followthrough.rst | 7 addition of your own engineering skills, have posted a perfect series of
48 agendas at the expense of your own. Kernel developers often expect to
56 making. Do not let their form of expression or your own pride keep that
69 be easy to become blinded by your own solution to a problem to the point
110 subsystem to the next; each maintainer has his or her own way of doing
142 Merging into the mainline brings its own challenges.
193 your own), or send an Acked-by: response back and let the original poster
|
| /Documentation/devicetree/bindings/mfd/ |
| D | motorola-cpcap.txt | 16 The sub-functions of CPCAP get their own node with their own compatible values,
|
| /Documentation/devicetree/bindings/clock/ |
| D | st,nomadik.txt | 16 board has its own circuitry for providing this oscillator
19 if the board has its own circuitry for providing this
|
| /Documentation/gpu/ |
| D | msm-crash-dump.rst | 48 will have its own unique id.
86 Set of registers values. Each entry is on its own line enclosed
|
| /Documentation/isdn/ |
| D | m_isdn.rst | 9 space is based on sockets with a own address family AF_ISDN.
|
| /Documentation/devicetree/bindings/sound/ |
| D | da9055.txt | 5 The Audio CODEC device in DA9055 has it's own I2C address which is configurable,
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 18 own binding.
25 For example, a pin controller may set up its own "active" state when the
41 Each client device's own binding determines the set of states that must be
|
| /Documentation/misc-devices/ |
| D | bh1770glc.rst | 21 ALS and proximity parts operates on their own, but they shares common I2C
22 interface and interrupt logic. In principle they can run on their own,
|
| /Documentation/admin-guide/device-mapper/ |
| D | persistent-data.rst | 10 different targets were rolling their own data structures, for example:
67 its own data within the space it's managing.
|
| /Documentation/locking/ |
| D | pi-futex.rst | 16 relatively simple: only a single owner may own a lock (i.e. no
94 own TID into the futex value], and attaches a 'PI state' structure to
100 futex value to its own TID and returns. Userspace has no other work to
|
12345678910>>...21