/freebsd/sys/contrib/device-tree/Bindings/thermal/ |
H A D | thermal.txt | 15 - thermal sensors: devices which may be used to take temperature 17 - cooling devices: devices which may be used to dissipate heat. 18 - trip points: describe key temperatures at which cooling is recommended. The 20 - cooling maps: used to describe links between trip points and cooling devices; 21 - thermal zones: used to describe thermal data within the hardware; 23 The following is a description of each of these node types. 25 * Thermal sensor devices 27 Thermal sensor devices are nodes providing temperature sensing capabilities on 29 nodes providing temperature data to thermal zones. Thermal sensor devices may 33 - #thermal-sensor-cells: Used to provide sensor device specific information [all …]
|
H A D | nvidia,tegra186-bpmp-thermal.txt | 1 NVIDIA Tegra186 BPMP thermal sensor 5 and GPU temperatures. This binding describes the thermal sensor that is 8 The BPMP thermal node must be located directly inside the main BPMP node. See 9 ../firmware/nvidia,tegra186-bpmp.txt for details of the BPMP binding. 11 This node represents a thermal sensor. See Documentation/devicetree/bindings/thermal/thermal-sensor… 15 - compatible: 18 - "nvidia,tegra186-bpmp-thermal" 19 - "nvidia,tegra194-bpmp-thermal" 20 - #thermal-sensor-cells: Cell for sensor index. 21 Single-cell integer. [all …]
|
H A D | thermal-zones.yaml | 1 # SPDX-License-Identifier: (GPL-2.0) 4 --- 5 $id: http://devicetree.org/schemas/thermal/thermal-zones.yaml# 6 $schema: http://devicetree.org/meta-schemas/base.yaml# 11 - Daniel Lezcano <daniel.lezcano@linaro.org> 14 Thermal management is achieved in devicetree by describing the sensor hardware 18 The following node types are used to completely describe a thermal management 20 - thermal-sensor: device that measures temperature, has SoC-specific bindings 21 - cooling-device: device used to dissipate heat either passively or actively 22 - thermal-zones: a container of the following node types used to describe all [all …]
|
H A D | thermal-sensor.yaml | 1 # SPDX-License-Identifier: (GPL-2.0) 4 --- 5 $id: http://devicetree.org/schemas/thermal/thermal-sensor.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 title: Thermal sensor 11 - Amit Kucheria <amitk@kernel.org> 14 Thermal management is achieved in devicetree by describing the sensor hardware 18 The following node types are used to completely describe a thermal management 20 - thermal-sensor: device that measures temperature, has SoC-specific bindings 21 - cooling-device: device used to dissipate heat either passively or actively [all …]
|
H A D | fsl,scu-thermal.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/thermal/fsl,scu-thermal.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: i.MX SCU Client Device Node - Thermal Based on SCU Message Protocol 10 - Dong Aisheng <aisheng.dong@nxp.com> 12 description: i.MX SCU Client Device Node 13 Client nodes are maintained as children of the relevant IMX-SCU device node. 16 - $ref: thermal-sensor.yaml# 21 - enum: [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/iio/temperature/ |
H A D | adi,ltc2983.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Analog Devices LTC2983, LTC2986, LTM2985 Multi-sensor Temperature system 10 - Nuno Sá <nuno.sa@analog.com> 13 Analog Devices LTC2983, LTC2984, LTC2986, LTM2985 Multi-Sensor Digital 16 https://www.analog.com/media/en/technical-documentation/data-sheets/2983fc.pdf 17 https://www.analog.com/media/en/technical-documentation/data-sheets/2984fb.pdf 18 https://www.analog.com/media/en/technical-documentation/data-sheets/29861fa.pdf 19 https://www.analog.com/media/en/technical-documentation/data-sheets/ltm2985.pdf [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/powerpc/opal/ |
H A D | sensor-groups.txt | 1 IBM OPAL Sensor Groups Binding 2 ------------------------------- 4 Node: /ibm,opal/sensor-groups 6 Description: Contains sensor groups available in the Powernv P9 7 servers. Each child node indicates a sensor group. 9 - compatible : Should be "ibm,opal-sensor-group" 11 Each child node contains below properties: 13 - type : String to indicate the type of sensor-group 15 - sensor-group-id: Abstract unique identifier provided by firmware of 16 type <u32> which is used for sensor-group [all …]
|
/freebsd/sys/powerpc/powernv/ |
H A D | opal_sensor.c | 1 /*- 56 #define SENSOR_LOCK(_sc) mtx_lock(&(_sc)->sc_mtx) 57 #define SENSOR_UNLOCK(_sc) mtx_unlock(&(_sc)->sc_mtx) 59 mtx_init(&_sc->sc_mtx, device_get_nameunit(_sc->sc_dev), \ 60 "opal-sensor", MTX_DEF) 64 * of "ibm,opal-sensor". One hangs off /ibm,opal/, named "sensors", the other 65 * hangs off of this node. For newbus attachments, we have one node (opalsens) 128 uint32_t sensor; in opal_sensor_sysctl() local 132 sensor = arg2; in opal_sensor_sysctl() 134 error = opal_sensor_get_val(sc, sensor, &sensval); in opal_sensor_sysctl() [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/hwmon/ |
H A D | ibmpowernv.txt | 2 ---------------------------- 4 Required node properties: 5 - compatible: must be one of 6 "ibm,opal-sensor-cooling-fan" 7 "ibm,opal-sensor-amb-temp" 8 "ibm,opal-sensor-power-supply" 9 "ibm,opal-sensor-power" 10 - sensor-id: an opaque id provided by the firmware to the kernel, identifies a 11 given sensor and its attribute data 13 Example sensors node: [all …]
|
H A D | lm90.txt | 3 Required node properties: 4 - compatible: manufacturer and chip name, one of 28 - reg: I2C bus address of the device 30 - vcc-supply: vcc regulator for the supply voltage. 33 - interrupts: Contains a single interrupt specifier which describes the 34 LM90 "-ALERT" pin output. 35 See interrupt-controller/interrupts.txt for the format. 37 - #thermal-sensor-cells: should be set to 1. See thermal/thermal-sensor.yaml 38 for details. See <include/dt-bindings/thermal/lm90.h> for the 39 definition of the local, remote and 2nd remote sensor index [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/media/i2c/ |
H A D | imx274.txt | 1 * Sony 1/2.5-Inch 8.51Mp CMOS Digital Image Sensor 3 The Sony imx274 is a 1/2.5-inch CMOS active pixel digital image sensor with 5 interface. The I2C address is fixed to 0x1a as per sensor data sheet. 6 Image data is sent through MIPI CSI-2, which is configured as 4 lanes 11 - compatible: value should be "sony,imx274" for imx274 sensor 12 - reg: I2C bus address of the device 15 - reset-gpios: Sensor reset GPIO 17 The imx274 device node should contain one 'port' child node with 18 an 'endpoint' subnode. For further reading on port node refer to 19 Documentation/devicetree/bindings/media/video-interfaces.txt. [all …]
|
H A D | imx290.txt | 1 * Sony IMX290 1/2.8-Inch CMOS Image Sensor 3 The Sony IMX290 is a 1/2.8-Inch CMOS Solid-state image sensor with 4 Square Pixel for Color Cameras. It is programmable through I2C and 4-wire 5 interfaces. The sensor output is available via CMOS logic parallel SDR output, 6 Low voltage LVDS DDR output and CSI-2 serial data output. The CSI-2 bus is the 10 - compatible: Should be "sony,imx290" 11 - reg: I2C bus address of the device 12 - clocks: Reference to the xclk clock. 13 - clock-names: Should be "xclk". 14 - clock-frequency: Frequency of the xclk clock in Hz. [all …]
|
H A D | nokia,smia.txt | 1 SMIA/SMIA++ sensor 3 SMIA (Standard Mobile Imaging Architecture) is an image sensor standard 8 Documentation/devicetree/bindings/media/video-interfaces.txt . 10 The device node should contain a "port" node which may contain one or more 12 Documentation/devicetree/bindings/media/video-interfaces.txt . 15 -------------------- 17 - compatible: "nokia,smia" 18 - reg: I2C address (0x10, or an alternative address) 19 - vana-supply: Analogue voltage supply (VANA), typically 2,8 volts (sensor 21 - clocks: External clock to the sensor [all …]
|
H A D | mt9m001.txt | 1 MT9M001: 1/2-Inch Megapixel Digital Image Sensor 3 The MT9M001 is an SXGA-format with a 1/2-inch CMOS active-pixel digital 4 image sensor. It is programmable through I2C interface. 8 - compatible: shall be "onnn,mt9m001". 9 - clocks: reference to the master clock into sensor 13 - reset-gpios: GPIO handle which is connected to the reset pin of the chip. 15 - standby-gpios: GPIO handle which is connected to the standby pin of the chip. 18 The device node must contain one 'port' child node with one 'endpoint' child 19 sub-node for its digital output video port, in accordance with the video 21 Documentation/devicetree/bindings/media/video-interfaces.txt [all …]
|
H A D | ov5647.txt | 1 Omnivision OV5647 raw image sensor 2 --------------------------------- 4 OV5647 is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces 9 - compatible : "ovti,ov5647". 10 - reg : I2C slave address of the sensor. 11 - clocks : Reference to the xclk clock. 13 The common video interfaces bindings (see video-interfaces.txt) should be 15 node should contain one 'port' child node with an 'endpoint' subnode. 17 Endpoint node mandatory properties: 19 - remote-endpoint: A phandle to the bus receiver's endpoint node. [all …]
|
H A D | aptina,mt9v111.txt | 1 * Aptina MT9V111 CMOS sensor 2 ---------------------------- 4 The Aptina MT9V111 is a 1/4-Inch VGA-format digital image sensor with a core 5 based on Aptina MT9V011 sensor and an integrated Image Flow Processor (IFP). 7 The sensor has an active pixel array of 640x480 pixels and can output a number 8 of image resolution and formats controllable through a simple two-wires 12 -------------------- 14 - compatible: shall be "aptina,mt9v111". 15 - clocks: reference to the system clock input provider. 18 -------------------- [all …]
|
H A D | toshiba,et8ek8.txt | 1 Toshiba et8ek8 5MP sensor 3 Toshiba et8ek8 5MP sensor is an image sensor found in Nokia N900 device 6 Documentation/devicetree/bindings/media/video-interfaces.txt . 10 -------------------- 12 - compatible: "toshiba,et8ek8" 13 - reg: I2C address (0x3e, or an alternative address) 14 - vana-supply: Analogue voltage supply (VANA), 2.8 volts 15 - clocks: External clock to the sensor 16 - clock-frequency: Frequency of the external clock to the sensor. Camera 18 a pre-determined frequency known to be suitable to the board. [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/media/ |
H A D | samsung-fimc.txt | 2 ---------------------------------------------- 4 The S5P/Exynos SoC Camera subsystem comprises of multiple sub-devices 6 the S5P SoCs series known as CAMIF), MIPI CSIS, FIMC-LITE and FIMC-IS (ISP). 8 The sub-subdevices are defined as child nodes of the common 'camera' node which 10 any single sub-device, like common camera port pins or the CAMCLK clock outputs 13 Common 'camera' node 14 -------------------- 18 - compatible: must be "samsung,fimc", "simple-bus" 19 - clocks: list of clock specifiers, corresponding to entries in 20 the clock-names property; [all …]
|
H A D | samsung-s5k6a3.txt | 1 Samsung S5K6A3(YX) raw image sensor 2 --------------------------------- 4 S5K6A3(YX) is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces 9 - compatible : "samsung,s5k6a3"; 10 - reg : I2C slave address of the sensor; 11 - svdda-supply : core voltage supply; 12 - svddio-supply : I/O voltage supply; 13 - afvdd-supply : AF (actuator) voltage supply; 14 - gpios : specifier of a GPIO connected to the RESET pin; 15 - clocks : should contain list of phandle and clock specifier pairs [all …]
|
H A D | microchip,csi2dc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Eugen Hristev <eugen.hristev@microchip.com> 13 CSI2DC - Camera Serial Interface 2 Demux Controller 19 clock domain towards a parallel interface that can be read by a sensor 26 is connected at the output to a sensor controller and the data pipe is 29 CSI2DC supports a single 'port' node as a sink port with either Synopsys 30 32-bit IDI interface or a parallel interface. 32 CSI2DC supports one 'port' node as source port with parallel interface. [all …]
|
H A D | samsung-s5c73m3.txt | 2 ------------------------------ 4 The S5C73M3 camera ISP supports MIPI CSI-2 and parallel (ITU-R BT.656) video 10 I2C slave device node 11 --------------------- 15 - compatible : "samsung,s5c73m3"; 16 - reg : I2C slave address of the sensor; 17 - vdd-int-supply : digital power supply (1.2V); 18 - vdda-supply : analog power supply (1.2V); 19 - vdd-reg-supply : regulator input power supply (2.8V); 20 - vddio-host-supply : host I/O power supply (1.8V to 2.8V); [all …]
|
/freebsd/sys/dev/acpi_support/ |
H A D | atk0110.c | 43 * -- Constantine A. Murenin <http://cnst.su/> 137 sc->sc_dev = dev; in aibs_attach() 138 sc->sc_ah = acpi_get_handle(dev); in aibs_attach() 140 sc->sc_ggrp_method = false; in aibs_attach() 151 if (sc->sc_volt_sysctl != NULL) in aibs_attach() 152 sysctl_remove_oid(sc->sc_volt_sysctl, true, true); in aibs_attach() 153 if (sc->sc_temp_sysctl != NULL) in aibs_attach() 154 sysctl_remove_oid(sc->sc_temp_sysctl, true, true); in aibs_attach() 155 if (sc->sc_fan_sysctl != NULL) in aibs_attach() 156 sysctl_remove_oid(sc->sc_fan_sysctl, true, true); in aibs_attach() [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/arm/ |
H A D | arm,scpi.txt | 2 ---------------------------------------------------------- 10 - compatible : should be 12 * "arm,scpi-pre-1.0" : For implementations complying to all 14 - mboxes: List of phandle and mailbox channel specifiers 17 - shmem : List of phandle pointing to the shared memory(SHM) area between the 27 ------------------------------------------------------------ 31 Container Node 34 - compatible : should be "arm,scpi-clocks" 36 protocol much be listed as sub-nodes under this node. 38 Sub-nodes [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/misc/ |
H A D | ifm-csi.txt | 1 IFM camera sensor interface on mpc5200 LocalPlus bus 4 - compatible: "ifm,o2d-csi" 5 - reg: specifies sensor chip select number and associated address range 6 - interrupts: external interrupt line number and interrupt sense mode 8 - gpios: three gpio-specifiers for "capture", "reset" and "master enable" 10 - ifm,csi-clk-handle: the phandle to a node in the DT describing the sensor 11 clock generator. This node is usually a general purpose timer controller. 12 - ifm,csi-addr-bus-width: address bus width (valid values are 16, 24, 25) 13 - ifm,csi-data-bus-width: data bus width (valid values are 8 and 16) 14 - ifm,csi-wait-cycles: sensor bus wait cycles [all …]
|
/freebsd/sys/dev/iicbus/pwm/ |
H A D | adt746x.c | 1 /*- 2 * SPDX-License-Identifier: BSD-2-Clause 144 static MALLOC_DEFINE(M_ADT746X, "adt746x", "ADT Sensor Information"); 169 return (-1); in adt746x_write() 198 return (-1); in adt746x_read() 222 sc->sc_dev = dev; in adt746x_probe() 223 sc->sc_addr = iicbus_get_addr(dev); in adt746x_probe() 237 sc->enum_hook.ich_func = adt746x_start; in adt746x_attach() 238 sc->enum_hook.ich_arg = dev; in adt746x_attach() 243 * the master. The openpic on mac-io is controlling the htpic. in adt746x_attach() [all …]
|