Searched full:from (Results 1 – 25 of 2576) sorted by relevance
12345678910>>...104
| /Documentation/hwmon/ |
| D | ucd9200.rst | 29 [From datasheets] UCD9220, UCD9222, UCD9224, UCD9240, UCD9244, UCD9246, and
62 in1_input Measured voltage. From READ_VIN register.
63 in1_min Minimum Voltage. From VIN_UV_WARN_LIMIT register.
64 in1_max Maximum voltage. From VIN_OV_WARN_LIMIT register.
66 in1_crit Critical maximum voltage. From VIN_OV_FAULT_LIMIT
68 in1_min_alarm Voltage low alarm. From VIN_UV_WARNING status.
69 in1_max_alarm Voltage high alarm. From VIN_OV_WARNING status.
70 in1_lcrit_alarm Voltage critical low alarm. From VIN_UV_FAULT status.
71 in1_crit_alarm Voltage critical high alarm. From VIN_OV_FAULT status.
74 in[2-5]_input Measured voltage. From READ_VOUT register.
[all …]
|
| D | pmbus.rst | 188 supported, and determines available sensors from this information.
197 inX_input Measured voltage. From READ_VIN or READ_VOUT register.
199 From VIN_UV_WARN_LIMIT or VOUT_UV_WARN_LIMIT register.
201 From VIN_OV_WARN_LIMIT or VOUT_OV_WARN_LIMIT register.
203 From VIN_UV_FAULT_LIMIT or VOUT_UV_FAULT_LIMIT register.
205 From VIN_OV_FAULT_LIMIT or VOUT_OV_FAULT_LIMIT register.
206 inX_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
207 inX_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
209 From VOLTAGE_UV_FAULT status.
211 From VOLTAGE_OV_FAULT status.
[all …]
|
| D | max8688.rst | 49 in1_input Measured voltage. From READ_VOUT register.
50 in1_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
51 in1_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
53 in1_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT
55 in1_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
56 in1_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
57 in1_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT
59 in1_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT
65 curr1_input Measured current. From READ_IOUT register.
66 curr1_max Maximum current. From IOUT_OC_WARN_LIMIT register.
[all …]
|
| D | f71882fg.rst | 10 Addresses scanned: none, address read from Super I/O config space
18 Addresses scanned: none, address read from Super I/O config space
26 Addresses scanned: none, address read from Super I/O config space
28 Datasheet: Available from the Fintek website
34 Addresses scanned: none, address read from Super I/O config space
36 Datasheet: Available from the Fintek website
42 Addresses scanned: none, address read from Super I/O config space
44 Datasheet: Available from the Fintek website
50 Addresses scanned: none, address read from Super I/O config space
58 Addresses scanned: none, address read from Super I/O config space
[all …]
|
| D | tps40422.rst | 48 in[1-2]_input Measured voltage. From READ_VOUT register.
51 curr[1-2]_input Measured current. From READ_IOUT register.
53 curr1_max Maximum current. From IOUT_OC_WARN_LIMIT register.
54 curr1_crit Critical maximum current. From IOUT_OC_FAULT_LIMIT
56 curr1_max_alarm Current high alarm. From IOUT_OC_WARN_LIMIT status.
57 curr1_crit_alarm Current critical high alarm. From IOUT_OC_FAULT status.
58 curr2_alarm Current high alarm. From IOUT_OC_WARNING status.
60 temp1_input Measured temperature. From READ_TEMPERATURE_2 register
62 temp1_max Maximum temperature. From OT_WARN_LIMIT register.
63 temp1_crit Critical high temperature. From OT_FAULT_LIMIT register.
[all …]
|
| D | max16064.rst | 49 in[1-4]_input Measured voltage. From READ_VOUT register.
50 in[1-4]_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
51 in[1-4]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
53 in[1-4]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT
55 in[1-4]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
56 in[1-4]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
57 in[1-4]_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT
59 in[1-4]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT
64 temp1_input Measured temperature. From READ_TEMPERATURE_1 register.
65 temp1_max Maximum temperature. From OT_WARN_LIMIT register.
[all …]
|
| D | ucd9000.rst | 28 From datasheets:
94 in[1-12]_input Measured voltage. From READ_VOUT register.
95 in[1-12]_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
96 in[1-12]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
98 in[1-12]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT
100 in[1-12]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
101 in[1-12]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
102 in[1-12]_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT
104 in[1-12]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT
108 curr[1-12]_input Measured current. From READ_IOUT register.
[all …]
|
| D | nct6775.rst | 15 Addresses scanned: ISA address retrieved from Super I/O registers
17 Datasheet: Available from the Nuvoton web site
23 Addresses scanned: ISA address retrieved from Super I/O registers
25 Datasheet: Available from Nuvoton upon request
31 Addresses scanned: ISA address retrieved from Super I/O registers
33 Datasheet: Available from Nuvoton upon request
39 Addresses scanned: ISA address retrieved from Super I/O registers
41 Datasheet: Available from Nuvoton upon request
47 Addresses scanned: ISA address retrieved from Super I/O registers
49 Datasheet: Available from Nuvoton upon request
[all …]
|
| D | lochnagar.rst | 31 power1_average_interval Power averaging time input valid from 1 to 1708mS
38 power2_average_interval Power averaging time input valid from 1 to 1708mS
45 power3_average_interval Power averaging time input valid from 1 to 1708mS
52 power4_average_interval Power averaging time input valid from 1 to 1708mS
59 power5_average_interval Power averaging time input valid from 1 to 1708mS
64 power6_average_interval Power averaging time input valid from 1 to 1708mS
71 power7_average_interval Power averaging time input valid from 1 to 1708mS
78 power8_average_interval Power averaging time input valid from 1 to 1708mS
|
| /Documentation/admin-guide/ |
| D | numastat.rst | 10 are able to allocate memory from nodes they prefer. If they succeed, numa_hit
17 incremented on allocation from a node by CPU on the same node. other_node is
19 from a CPU from a different node. Note there is no counter analogical to
25 numa_hit A process wanted to allocate memory from this node,
28 numa_miss A process wanted to allocate memory from another node,
29 but ended up with memory from this node.
32 but ended up with memory from another node.
35 and got memory from this node.
38 and got memory from this node.
40 interleave_hit Interleaving wanted to allocate from this node
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | cirrus,lochnagar.yaml | 48 - ln-cdc-clkout # Output clock from CODEC card.
49 - ln-dsp-clkout # Output clock from DSP card.
50 - ln-gf-mclk1 # Optional input clock from host system.
51 - ln-gf-mclk2 # Optional input clock from host system.
52 - ln-gf-mclk3 # Optional input clock from host system.
53 - ln-gf-mclk4 # Optional input clock from host system.
54 - ln-psia1-mclk # Optional input clock from external connector.
55 - ln-psia2-mclk # Optional input clock from external connector.
56 - ln-spdif-mclk # Optional input clock from SPDIF.
57 - ln-spdif-clkout # Optional input clock from SPDIF.
[all …]
|
| D | qcom,sdm845-dispcc.yaml | 28 - description: GPLL0 source from GCC
29 - description: GPLL0 div source from GCC
30 - description: Byte clock from DSI PHY0
31 - description: Pixel clock from DSI PHY0
32 - description: Byte clock from DSI PHY1
33 - description: Pixel clock from DSI PHY1
34 - description: Link clock from DP PHY
35 - description: VCO DIV clock from DP PHY
|
| /Documentation/devicetree/bindings/display/exynos/ |
| D | exynos_dp.txt | 15 For the Panel initialization, we read data from dp-controller node.
25 from common clock binding: handle to dp clock.
27 from common clock binding: Shall be "dp".
29 from general PHY binding: the phandle for the PHY device.
31 from general PHY binding: Should be "dp".
60 -interlaced: deprecated prop that can parsed from drm_display_mode.
61 -vsync-active-high: deprecated prop that can parsed from drm_display_mode.
62 -hsync-active-high: deprecated prop that can parsed from drm_display_mode.
63 -samsung,ycbcr-coeff: deprecated prop that can parsed from drm_display_mode.
64 -samsung,dynamic-range: deprecated prop that can parsed from drm_display_mode.
[all …]
|
| /Documentation/scsi/ |
| D | ChangeLog.lpfc | 5 Changes from 20050323 to 20050413
11 * Merged patch from Christoph Hellwig <hch@lst.de>: split helpers
24 only be called from lpfc_sli_submit_iocb. Also make
47 Changes from 20050308 to 20050323
50 * Changed a few lines from patch submitted by Christoph Hellwig
53 * Merged patch from Christoph Hellwig (3/19): some misc patches
64 - don't call dma_sync function on allocations from
66 * Merged patch from Christoph Hellwig (3/19) - nlp_failMask isn't
73 * Merged patch from Christoph Hellwig (03/19) - fix initialization
74 order - scsi_add_host must happen last from scsi POV. Also some
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-coresight-devices-etb10 | 5 Description: (RW) Add/remove a sink from a trace path. There can be multiple
20 value stored in this register+1 (from ARM ETB-TRM).
27 2. The value is read directly from HW register RDP, 0x004.
34 is read directly from HW register STS, 0x00C.
41 that is used to read entries from the Trace RAM over the APB
42 interface. The value is read directly from HW register RRP,
50 that is used to sets the write pointer to write entries from
52 from HW register RWP, 0x018.
59 read directly from HW register TRG, 0x01C.
66 is read directly from HW register CTL, 0x020.
[all …]
|
| D | sysfs-devices-power | 15 from sleep states, such as the memory sleep state (suspend to
20 used to activate the system from a sleep state. Such devices
33 be enabled to wake up the system from sleep states.
46 + "on\n" to prevent the device from being power managed;
51 from power managing the device at run time. Doing that while
87 the system from sleep states, this attribute is not present.
88 If the device is not enabled to wake up the system from sleep
99 system from sleep states, this attribute is not present. If
100 the device is not enabled to wake up the system from sleep
111 is not capable to wake up the system from sleep states, this
[all …]
|
| D | sysfs-bus-coresight-devices-tmc | 15 The value is read directly from HW register RSZ, 0x004.
22 is read directly from HW register STS, 0x00C.
29 that is used to read entries from the Trace RAM over the APB
30 interface. The value is read directly from HW register RRP,
38 that is used to sets the write pointer to write entries from
40 from HW register RWP, 0x018.
47 read directly from HW register TRG, 0x01C.
54 is read directly from HW register CTL, 0x020.
61 register. The value is read directly from HW register FFSR,
69 register. The value is read directly from HW register FFCR,
[all …]
|
| D | sysfs-bus-iio-light-isl29018 | 6 From ISL29018 Data Sheet (FN6619.4, Oct 8, 2012) regarding the
10 detection. The range of Scheme 0 proximity count is from 0 to
13 range of Scheme 1 proximity count is from -2^(n-1) to 2^(n-1).
19 0 Sensing IR from LED and ambient
20 1 Sensing IR from LED with ambient IR rejection
|
| /Documentation/devicetree/bindings/arm/ |
| D | sp810.txt | 14 - clock-names: from the common clock bindings, for more details see
18 - clocks: from the common clock bindings, phandle and clock
21 - #clock-cells: from the common clock bindings;
24 - clock-output-names: from the common clock bindings;
27 - assigned-clocks: from the common clock binding;
31 - assigned-clock-parents: from the common clock binding;
|
| /Documentation/driver-api/ |
| D | device_link.rst | 55 or the device link needs to be added from a function which is guaranteed
56 not to run in parallel to a suspend/resume transition, such as from a
60 represents a driver presence dependency, yet is added from the consumer's
65 non-presence. [Note that it is valid to create a link from the consumer's
87 link is added from the consumer's ``->probe`` callback: ``DL_FLAG_RPM_ACTIVE``
88 can be specified to runtime resume the supplier and prevent it from suspending
93 Similarly, when the device link is added from supplier's ``->probe`` callback,
160 runtime PM integration is added from the busmaster device (consumer)
172 and an NHI device to manage the PCIe switch. On resume from system sleep,
177 device links from the hotplug ports (consumers) to the NHI device
[all …]
|
| /Documentation/vm/ |
| D | numa.rst | 9 This question can be answered from a couple of perspectives: the
12 From the hardware perspective, a NUMA system is a computer platform that
16 from the software abstraction thereof, we'll call the components/assemblies
25 cells at multiple distances from other cells.
29 to and accessible from any CPU attached to any cell and cache coherency
33 away the cell containing the CPU or IO bus making the memory access is from the
37 can have cells at multiple remote distances from any given cell.
87 from the same node before using remote nodes which are ordered by NUMA distance.
89 By default, Linux will attempt to satisfy memory allocation requests from the
91 Linux will attempt to allocate from the first node in the appropriate zonelist
[all …]
|
| /Documentation/devicetree/bindings/misc/ |
| D | atmel-ssc.txt | 21 - atmel,clk-from-rk-pin: bool property.
23 clock can get from TK pin, and also can get from RK pin. So, add
24 this parameter to choose where the clock from.
25 - By default the clock is from TK pin, if the clock from RK pin, this
|
| /Documentation/devicetree/bindings/spi/ |
| D | nvidia,tegra114-spi.txt | 28 with this tap value. This property is used to tune the outgoing data from
30 Tap values vary based on the platform design trace lengths from Tegra SPI
31 to corresponding slave devices. Valid tap values are from 0 thru 63.
32 - nvidia,rx-clk-tap-delay: Delays the clock coming in from the external device
34 clock with respect to the data from the SPI slave device.
35 Tap values vary based on the platform design trace lengths from Tegra SPI
36 to corresponding slave devices. Valid tap values are from 0 thru 63.
|
| /Documentation/usb/ |
| D | ohci.rst | 8 from the "usb-ohci" driver from the 2.4 kernel series. The "usb-ohci" code
10 contributions from many others (read its copyright/licencing header).
14 compared to the earlier "Universal Host Controller Interface" (UHCI) from
16 from vendors other than Intel and VIA generally use OHCI.
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-mem2mem.rst | 10 otherwise convert video data from one format into another format, in memory.
14 converting from YUV to RGB).
17 supports both output (sending frames from memory to the hardware)
18 and capture (receiving the processed frames from the hardware into
26 it independently from the others. The driver will arbitrate access to
28 This is different from the usual video node behavior where the video
|
12345678910>>...104