* [PATCH v2 01/29] dt-bindings:iio:humidity:hdc100x Drop separate doc + add to trivial-devices
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 02/29] dt-bindings:iio:humidity:htu21 " Jonathan Cameron
` (28 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Matt Ranostay
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Very simple binding for this i2c device with no properties beyond
reg and compatible. Hence doesn't need it's own document.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Acked-by: Matt Ranostay <matt.ranostay@konsulko.com>
---
.../bindings/iio/humidity/hdc100x.txt | 17 -----------------
.../devicetree/bindings/trivial-devices.yaml | 10 ++++++++++
2 files changed, 10 insertions(+), 17 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/humidity/hdc100x.txt b/Documentation/devicetree/bindings/iio/humidity/hdc100x.txt
deleted file mode 100644
index c52333bdfd19..000000000000
--- a/Documentation/devicetree/bindings/iio/humidity/hdc100x.txt
+++ /dev/null
@@ -1,17 +0,0 @@
-* HDC100x temperature + humidity sensors
-
-Required properties:
- - compatible: Should contain one of the following:
- ti,hdc1000
- ti,hdc1008
- ti,hdc1010
- ti,hdc1050
- ti,hdc1080
- - reg: i2c address of the sensor
-
-Example:
-
-hdc100x@40 {
- compatible = "ti,hdc1000";
- reg = <0x40>;
-};
diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml
index ab623ba930d5..d37f757e6bd1 100644
--- a/Documentation/devicetree/bindings/trivial-devices.yaml
+++ b/Documentation/devicetree/bindings/trivial-devices.yaml
@@ -356,6 +356,16 @@ properties:
- ti,ads7830
# Temperature Monitoring and Fan Control
- ti,amc6821
+ # Temperature and humidity sensor with i2c interface
+ - ti,hdc1000
+ # Temperature and humidity sensor with i2c interface
+ - ti,hdc1008
+ # Temperature and humidity sensor with i2c interface
+ - ti,hdc1010
+ # Temperature and humidity sensor with i2c interface
+ - ti,hdc1050
+ # Temperature and humidity sensor with i2c interface
+ - ti,hdc1080
# Temperature sensor with 2-wire interface
- ti,lm73
# Temperature sensor with integrated fan control
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 02/29] dt-bindings:iio:humidity:htu21 Drop separate doc + add to trivial-devices
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 01/29] dt-bindings:iio:humidity:hdc100x Drop separate doc + add to trivial-devices Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 03/29] dt-bindings:iio:humidity:st,hts221 yaml conversion Jonathan Cameron
` (27 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree; +Cc: Jonathan Cameron, Rob Herring
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Very simple binding for this i2c device with no properties beyond
reg and compatible. Hence doesn't need it's own document.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
---
.../devicetree/bindings/iio/humidity/htu21.txt | 13 -------------
.../devicetree/bindings/trivial-devices.yaml | 4 ++++
2 files changed, 4 insertions(+), 13 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/humidity/htu21.txt b/Documentation/devicetree/bindings/iio/humidity/htu21.txt
deleted file mode 100644
index 97d79636f7ae..000000000000
--- a/Documentation/devicetree/bindings/iio/humidity/htu21.txt
+++ /dev/null
@@ -1,13 +0,0 @@
-*HTU21 - Measurement-Specialties htu21 temperature & humidity sensor and humidity part of MS8607 sensor
-
-Required properties:
-
- - compatible: should be "meas,htu21" or "meas,ms8607-humidity"
- - reg: I2C address of the sensor
-
-Example:
-
-htu21@40 {
- compatible = "meas,htu21";
- reg = <0x40>;
-};
diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml
index d37f757e6bd1..43febb3057b6 100644
--- a/Documentation/devicetree/bindings/trivial-devices.yaml
+++ b/Documentation/devicetree/bindings/trivial-devices.yaml
@@ -132,6 +132,10 @@ properties:
- mcube,mc3230
# MEMSIC 2-axis 8-bit digital accelerometer
- memsic,mxc6225
+ # Measurement Specialities I2C temperature and humidity sensor
+ - meas,htu21
+ # Measurement Specialities temp and humidity part of ms8607 device
+ - meas,ms8607-humidity
# Microchip differential I2C ADC, 1 Channel, 18 bit
- microchip,mcp3421
# Microchip differential I2C ADC, 2 Channel, 18 bit
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 03/29] dt-bindings:iio:humidity:st,hts221 yaml conversion.
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 01/29] dt-bindings:iio:humidity:hdc100x Drop separate doc + add to trivial-devices Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 02/29] dt-bindings:iio:humidity:htu21 " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 04/29] dt-bindings:iio:humidity:dht11 " Jonathan Cameron
` (26 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Lorenzo Bianconi
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Straight forward conversion of this temperature and pressure sensor binding.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>
---
.../bindings/iio/humidity/hts221.txt | 30 -----------
.../bindings/iio/humidity/st,hts221.yaml | 52 +++++++++++++++++++
2 files changed, 52 insertions(+), 30 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/humidity/hts221.txt b/Documentation/devicetree/bindings/iio/humidity/hts221.txt
deleted file mode 100644
index 84d029372260..000000000000
--- a/Documentation/devicetree/bindings/iio/humidity/hts221.txt
+++ /dev/null
@@ -1,30 +0,0 @@
-* HTS221 STM humidity + temperature sensor
-
-Required properties:
-- compatible: should be "st,hts221"
-- reg: i2c address of the sensor / spi cs line
-
-Optional properties:
-- drive-open-drain: the interrupt/data ready line will be configured
- as open drain, which is useful if several sensors share the same
- interrupt line. This is a boolean property.
- If the requested interrupt is configured as IRQ_TYPE_LEVEL_HIGH or
- IRQ_TYPE_EDGE_RISING a pull-down resistor is needed to drive the line
- when it is not active, whereas a pull-up one is needed when interrupt
- line is configured as IRQ_TYPE_LEVEL_LOW or IRQ_TYPE_EDGE_FALLING.
- Refer to pinctrl/pinctrl-bindings.txt for the property description.
-- interrupts: interrupt mapping for IRQ. It should be configured with
- flags IRQ_TYPE_LEVEL_HIGH, IRQ_TYPE_EDGE_RISING, IRQ_TYPE_LEVEL_LOW or
- IRQ_TYPE_EDGE_FALLING.
-
- Refer to interrupt-controller/interrupts.txt for generic interrupt
- client node bindings.
-
-Example:
-
-hts221@5f {
- compatible = "st,hts221";
- reg = <0x5f>;
- interrupt-parent = <&gpio0>;
- interrupts = <0 IRQ_TYPE_EDGE_RISING>;
-};
diff --git a/Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml b/Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml
new file mode 100644
index 000000000000..396451c26728
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml
@@ -0,0 +1,52 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/humidity/st,hts221.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: HTS221 STM humidity + temperature sensor
+
+maintainers:
+ - Lorenzo Bianconi <lorenzo@kernel.org>
+
+description: |
+ Humidity and temperature sensor with I2C interface and data ready
+ interrupt.
+
+properties:
+ compatible:
+ const: st,hts221
+
+ reg:
+ maxItems: 1
+
+ drive-open-drain:
+ type: boolean
+ description:
+ The interrupt/data ready line will be configured as open drain, which
+ is useful if several sensors share the same interrupt line.
+
+ interrupts:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ hts221@5f {
+ compatible = "st,hts221";
+ reg = <0x5f>;
+ interrupt-parent = <&gpio0>;
+ interrupts = <0 IRQ_TYPE_EDGE_RISING>;
+ };
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 04/29] dt-bindings:iio:humidity:dht11 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (2 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 03/29] dt-bindings:iio:humidity:st,hts221 yaml conversion Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 05/29] dt-bindings:iio:pressure:ms5637 Drop separate doc + add to trivial-devices Jonathan Cameron
` (25 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Harald Geyer
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
The conversion is straight forward, but leaves an open question.
The compatible for this device has never had a vendor.
Harald Geyer has identified as probably being made by aosong,
but we have no current match to any of their more specific part
numbers. As such, this is noted in the file but the
compatible doesn't include the vendor prefix.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Acked-By: Harald Geyer <harald@ccbib.org>
---
v2: Added note on aosong as probably manufacturer
.../bindings/iio/humidity/dht11.txt | 14 -------
.../bindings/iio/humidity/dht11.yaml | 41 +++++++++++++++++++
2 files changed, 41 insertions(+), 14 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/humidity/dht11.txt b/Documentation/devicetree/bindings/iio/humidity/dht11.txt
deleted file mode 100644
index ecc24c199fd6..000000000000
--- a/Documentation/devicetree/bindings/iio/humidity/dht11.txt
+++ /dev/null
@@ -1,14 +0,0 @@
-* DHT11 humidity/temperature sensor (and compatibles like DHT22)
-
-Required properties:
- - compatible: Should be "dht11"
- - gpios: Should specify the GPIO connected to the sensor's data
- line, see "gpios property" in
- Documentation/devicetree/bindings/gpio/gpio.txt.
-
-Example:
-
-humidity_sensor {
- compatible = "dht11";
- gpios = <&gpio0 6 0>;
-}
diff --git a/Documentation/devicetree/bindings/iio/humidity/dht11.yaml b/Documentation/devicetree/bindings/iio/humidity/dht11.yaml
new file mode 100644
index 000000000000..2247481d0203
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/humidity/dht11.yaml
@@ -0,0 +1,41 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/humidity/dht11.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: DHT11 humidity + temperature sensor
+
+maintainers:
+ - Harald Geyer <harald@ccbib.org>
+
+description: |
+ A simple and low cost module providing a non standard single GPIO based
+ interface. It is believed the part is made by aosong but don't have
+ absolute confirmation of this, or what the aosong part number is.
+
+properties:
+ compatible:
+ const: dht11
+
+ reg:
+ maxItems: 1
+
+ gpios:
+ maxItems: 1
+ description:
+ Single, interrupt capable, GPIO used to communicate with the device.
+
+required:
+ - compatible
+ - gpios
+
+additionalProperties: false
+
+examples:
+ - |
+ humidity_sensor {
+ compatible = "dht11";
+ gpios = <&gpio0 6 0>;
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 05/29] dt-bindings:iio:pressure:ms5637 Drop separate doc + add to trivial-devices
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (3 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 04/29] dt-bindings:iio:humidity:dht11 " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 06/29] dt-bindings:iio:pressure:murata,zpa2326 yaml conversion Jonathan Cameron
` (24 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree; +Cc: Jonathan Cameron, Rob Herring
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Very simple binding for this i2c device with no properties beyond
reg and compatible. Hence doesn't need it's own document.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
---
.../devicetree/bindings/iio/pressure/ms5637.txt | 17 -----------------
.../devicetree/bindings/trivial-devices.yaml | 8 ++++++++
2 files changed, 8 insertions(+), 17 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/pressure/ms5637.txt b/Documentation/devicetree/bindings/iio/pressure/ms5637.txt
deleted file mode 100644
index 1f43ffa068ac..000000000000
--- a/Documentation/devicetree/bindings/iio/pressure/ms5637.txt
+++ /dev/null
@@ -1,17 +0,0 @@
-* MS5637 - Measurement-Specialties MS5637, MS5805, MS5837 and MS8607 pressure & temperature sensor
-
-Required properties:
-
- -compatible: should be one of the following
- meas,ms5637
- meas,ms5805
- meas,ms5837
- meas,ms8607-temppressure
- -reg: I2C address of the sensor
-
-Example:
-
-ms5637@76 {
- compatible = "meas,ms5637";
- reg = <0x76>;
-};
diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml
index 43febb3057b6..8d8eadbab473 100644
--- a/Documentation/devicetree/bindings/trivial-devices.yaml
+++ b/Documentation/devicetree/bindings/trivial-devices.yaml
@@ -134,8 +134,16 @@ properties:
- memsic,mxc6225
# Measurement Specialities I2C temperature and humidity sensor
- meas,htu21
+ # Measurement Specialities I2C pressure and temperature sensor
+ - meas,ms5637
+ # Measurement Specialities I2C pressure and temperature sensor
+ - meas,ms5805
+ # Measurement Specialities I2C pressure and temperature sensor
+ - meas,ms5837
# Measurement Specialities temp and humidity part of ms8607 device
- meas,ms8607-humidity
+ # Measurement Specialities temp and pressure part of ms8607 device
+ - meas,ms8607-temppressure
# Microchip differential I2C ADC, 1 Channel, 18 bit
- microchip,mcp3421
# Microchip differential I2C ADC, 2 Channel, 18 bit
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 06/29] dt-bindings:iio:pressure:murata,zpa2326 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (4 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 05/29] dt-bindings:iio:pressure:ms5637 Drop separate doc + add to trivial-devices Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 07/29] dt-bindings:iio:pressure:meas,ms5611 " Jonathan Cameron
` (23 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree; +Cc: Jonathan Cameron, Rob Herring
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Simple conversion with a few minor tweaks:
* I added 1MHz max for spi-max-frequency
* I have give myself as the maintainer. This driver was written by
Gregor Boirie but I don't have an up to date email address for Gregor.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
---
.../bindings/iio/pressure/murata,zpa2326.yaml | 62 +++++++++++++++++++
.../bindings/iio/pressure/zpa2326.txt | 29 ---------
2 files changed, 62 insertions(+), 29 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/pressure/murata,zpa2326.yaml b/Documentation/devicetree/bindings/iio/pressure/murata,zpa2326.yaml
new file mode 100644
index 000000000000..d6103be03460
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/pressure/murata,zpa2326.yaml
@@ -0,0 +1,62 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/pressure/murata,zpa2326.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Murata ZPA2326 pressure sensor
+
+maintainers:
+ - Jonathan Cameron <jic23@kernel.org>
+
+description: |
+ Pressure sensor from Murata with SPI and I2C bus interfaces.
+
+
+properties:
+ compatible:
+ const: murata,zpa2326
+
+ reg:
+ maxItems: 1
+
+ vdd-supply: true
+ vref-supply: true
+
+ interrupts:
+ maxItems: 1
+
+ spi-max-frequency:
+ maximum: 1000000
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ pressure@5c {
+ compatible = "murata,zpa2326";
+ reg = <0x5c>;
+ interrupt-parent = <&gpio>;
+ interrupts = <12>;
+ vdd-supply = <&ldo_1v8_gnss>;
+ };
+ };
+ - |
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ pressure@0 {
+ compatible = "murata,zpa2326";
+ reg = <0>;
+ spi-max-frequency = <500000>;
+ };
+ };
+...
diff --git a/Documentation/devicetree/bindings/iio/pressure/zpa2326.txt b/Documentation/devicetree/bindings/iio/pressure/zpa2326.txt
deleted file mode 100644
index a36ab3e0c3f7..000000000000
--- a/Documentation/devicetree/bindings/iio/pressure/zpa2326.txt
+++ /dev/null
@@ -1,29 +0,0 @@
-Murata ZPA2326 pressure sensor
-
-Pressure sensor from Murata with SPI and I2C bus interfaces.
-
-Required properties:
-- compatible: "murata,zpa2326"
-- reg: the I2C address or SPI chip select the device will respond to
-
-Recommended properties for SPI bus usage:
-- spi-max-frequency: maximum SPI bus frequency as documented in
- Documentation/devicetree/bindings/spi/spi-bus.txt
-
-Optional properties:
-- vref-supply: an optional regulator that needs to be on to provide VREF
- power to the sensor
-- vdd-supply: an optional regulator that needs to be on to provide VDD
- power to the sensor
-- interrupts: interrupt mapping for IRQ as documented in
- Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
-
-Example:
-
-zpa2326@5c {
- compatible = "murata,zpa2326";
- reg = <0x5c>;
- interrupt-parent = <&gpio>;
- interrupts = <12>;
- vdd-supply = <&ldo_1v8_gnss>;
-};
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 07/29] dt-bindings:iio:pressure:meas,ms5611 yaml conversion.
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (5 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 06/29] dt-bindings:iio:pressure:murata,zpa2326 yaml conversion Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 08/29] dt-bindings:iio:pressure:hoperf,hp03 " Jonathan Cameron
` (22 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Tomasz Duszynski
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
One addition here was to put in a 20MHz maximum for the SPI bus
as specified in the datasheets of both support parts.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Cc: Tomasz Duszynski <tduszyns@gmail.com>
---
.../bindings/iio/pressure/meas,ms5611.yaml | 57 +++++++++++++++++++
.../bindings/iio/pressure/ms5611.txt | 19 -------
2 files changed, 57 insertions(+), 19 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/pressure/meas,ms5611.yaml b/Documentation/devicetree/bindings/iio/pressure/meas,ms5611.yaml
new file mode 100644
index 000000000000..4f06707450bf
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/pressure/meas,ms5611.yaml
@@ -0,0 +1,57 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/pressure/meas,ms5611.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Measurement Specialities ms5611 and similar pressure sensors
+
+maintainers:
+ - Tomasz Duszynski <tduszyns@gmail.com>
+
+description: |
+ Pressure sensors from MEAS Switzerland with SPI and I2C bus interfaces.
+
+properties:
+ compatible:
+ enum:
+ - meas,ms5607
+ - meas,ms5611
+
+ reg:
+ maxItems: 1
+
+ vdd-supply: true
+
+ spi-max-frequency:
+ maximum: 20000000
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ pressure@77 {
+ compatible = "meas,ms5607";
+ reg = <0x77>;
+ vdd-supply = <&ldo_3v3_gnss>;
+ };
+ };
+ - |
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ pressure@0 {
+ compatible = "meas,ms5611";
+ reg = <0>;
+ vdd-supply = <&ldo_3v3_gnss>;
+ };
+ };
+...
diff --git a/Documentation/devicetree/bindings/iio/pressure/ms5611.txt b/Documentation/devicetree/bindings/iio/pressure/ms5611.txt
deleted file mode 100644
index 17bca866c084..000000000000
--- a/Documentation/devicetree/bindings/iio/pressure/ms5611.txt
+++ /dev/null
@@ -1,19 +0,0 @@
-MEAS ms5611 family pressure sensors
-
-Pressure sensors from MEAS Switzerland with SPI and I2C bus interfaces.
-
-Required properties:
-- compatible: "meas,ms5611" or "meas,ms5607"
-- reg: the I2C address or SPI chip select the device will respond to
-
-Optional properties:
-- vdd-supply: an optional regulator that needs to be on to provide VDD
- power to the sensor.
-
-Example:
-
-ms5607@77 {
- compatible = "meas,ms5607";
- reg = <0x77>;
- vdd-supply = <&ldo_3v3_gnss>;
-};
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 08/29] dt-bindings:iio:pressure:hoperf,hp03 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (6 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 07/29] dt-bindings:iio:pressure:meas,ms5611 " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 09/29] dt-bindings:iio:proximity:semtech,sx9500 " Jonathan Cameron
` (21 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Marek Vasut
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
One quirk in the txt file was that the xclr gpio was specified as
xclr-gpio rather than xclr-gpios. I've fixed that in the
yaml version.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Cc: Marek Vasut <marex@denx.de>
---
v2: Fixed description naming of xclr-gpios
.../bindings/iio/pressure/hoperf,hp03.yaml | 47 +++++++++++++++++++
.../devicetree/bindings/iio/pressure/hp03.txt | 17 -------
2 files changed, 47 insertions(+), 17 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/pressure/hoperf,hp03.yaml b/Documentation/devicetree/bindings/iio/pressure/hoperf,hp03.yaml
new file mode 100644
index 000000000000..69a3759e23db
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/pressure/hoperf,hp03.yaml
@@ -0,0 +1,47 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/pressure/hoperf,hp03.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: HopeRF HP03 digital pressure/temperature sensors
+
+maintainers:
+ - Marek Vasut <marex@denx.de>
+
+description: |
+ Digital pressure and temperature sensor with an I2C interface.
+
+properties:
+ compatible:
+ const: hoperf,hp03
+
+ reg:
+ maxItems: 1
+
+ xclr-gpios:
+ description:
+ The XCLR pin is a reset of the ADC in the chip, it must be pulled
+ HI before the conversion and readout of the value from the ADC
+ registers and pulled LO afterward.
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ pressure@77 {
+ compatible = "hoperf,hp03";
+ reg = <0x77>;
+ xclr-gpios = <&portc 0 0x0>;
+ };
+ };
+...
diff --git a/Documentation/devicetree/bindings/iio/pressure/hp03.txt b/Documentation/devicetree/bindings/iio/pressure/hp03.txt
deleted file mode 100644
index 831dbee7a5c3..000000000000
--- a/Documentation/devicetree/bindings/iio/pressure/hp03.txt
+++ /dev/null
@@ -1,17 +0,0 @@
-HopeRF HP03 digital pressure/temperature sensors
-
-Required properties:
-- compatible: must be "hoperf,hp03"
-- xclr-gpio: must be device tree identifier of the XCLR pin.
- The XCLR pin is a reset of the ADC in the chip,
- it must be pulled HI before the conversion and
- readout of the value from the ADC registers and
- pulled LO afterward.
-
-Example:
-
-hp03@77 {
- compatible = "hoperf,hp03";
- reg = <0x77>;
- xclr-gpio = <&portc 0 0x0>;
-};
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 09/29] dt-bindings:iio:proximity:semtech,sx9500 yaml conversion.
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (7 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 08/29] dt-bindings:iio:pressure:hoperf,hp03 " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 10/29] dt-bindings:iio:proximity:st,vl53l0x " Jonathan Cameron
` (20 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree; +Cc: Jonathan Cameron, Rob Herring
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Simple conversion. There hasn't been much activity around this driver
for a long time and I don't think I have any up to date contact details
for the original authors. As such, I've listed myself as the binding
maintainer. More than happy to hand it off to someone more relevant though!
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
---
.../iio/proximity/semtech,sx9500.yaml | 50 +++++++++++++++++++
.../bindings/iio/proximity/sx9500.txt | 23 ---------
2 files changed, 50 insertions(+), 23 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/proximity/semtech,sx9500.yaml b/Documentation/devicetree/bindings/iio/proximity/semtech,sx9500.yaml
new file mode 100644
index 000000000000..66dd01506859
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/proximity/semtech,sx9500.yaml
@@ -0,0 +1,50 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/proximity/semtech,sx9500.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Semtech's SX9500 capacitive proximity button device
+
+maintainers:
+ - Jonathan Cameron <jic23@kernel.org>
+
+properties:
+ compatible:
+ const: semtech,sx9500
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+ reset-gpios:
+ description:
+ GPIO connected to the active low reset pin.
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+ - interrupts
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+ #include <dt-bindings/gpio/gpio.h>
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ proximity@28 {
+ compatible = "semtech,sx9500";
+ reg = <0x28>;
+ interrupt-parent = <&gpio2>;
+ interrupts = <16 IRQ_TYPE_LEVEL_LOW>;
+ reset-gpios = <&gpio2 10 GPIO_ACTIVE_LOW>;
+ };
+ };
+...
diff --git a/Documentation/devicetree/bindings/iio/proximity/sx9500.txt b/Documentation/devicetree/bindings/iio/proximity/sx9500.txt
deleted file mode 100644
index c54455db3bec..000000000000
--- a/Documentation/devicetree/bindings/iio/proximity/sx9500.txt
+++ /dev/null
@@ -1,23 +0,0 @@
-Semtech's SX9500 capacitive proximity button device driver
-
-Required properties:
- - compatible: must be "semtech,sx9500"
- - reg: i2c address where to find the device
- - interrupts : the sole interrupt generated by the device
-
- Refer to interrupt-controller/interrupts.txt for generic
- interrupt client node bindings.
-
-Optional properties:
- - reset-gpios: Reference to the GPIO connected to the device's active
- low reset pin.
-
-Example:
-
-sx9500@28 {
- compatible = "semtech,sx9500";
- reg = <0x28>;
- interrupt-parent = <&gpio2>;
- interrupts = <16 IRQ_TYPE_LEVEL_LOW>;
- reset-gpios = <&gpio2 10 GPIO_ACTIVE_LOW>;
-};
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 10/29] dt-bindings:iio:proximity:st,vl53l0x yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (8 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 09/29] dt-bindings:iio:proximity:semtech,sx9500 " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 11/29] dt-bindings:iio:proximity:ams,as3935 " Jonathan Cameron
` (19 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Song Qiang
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Straight forward conversion from txt to yaml.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Cc: Song Qiang <songqiang1304521@gmail.com>
---
.../bindings/iio/proximity/st,vl53l0x.yaml | 42 +++++++++++++++++++
.../bindings/iio/proximity/vl53l0x.txt | 18 --------
2 files changed, 42 insertions(+), 18 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/proximity/st,vl53l0x.yaml b/Documentation/devicetree/bindings/iio/proximity/st,vl53l0x.yaml
new file mode 100644
index 000000000000..656460d9d8c8
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/proximity/st,vl53l0x.yaml
@@ -0,0 +1,42 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/proximity/st,vl53l0x.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: ST VL53L0X ToF ranging sensor
+
+maintainers:
+ - Song Qiang <songqiang1304521@gmail.com>
+
+properties:
+ compatible:
+ const: st,vl53l0x
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ proximity@29 {
+ compatible = "st,vl53l0x";
+ reg = <0x29>;
+ interrupt-parent = <&gpio>;
+ interrupts = <23 IRQ_TYPE_EDGE_FALLING>;
+ };
+ };
+...
diff --git a/Documentation/devicetree/bindings/iio/proximity/vl53l0x.txt b/Documentation/devicetree/bindings/iio/proximity/vl53l0x.txt
deleted file mode 100644
index dfe00eb961cd..000000000000
--- a/Documentation/devicetree/bindings/iio/proximity/vl53l0x.txt
+++ /dev/null
@@ -1,18 +0,0 @@
-ST VL53L0X ToF ranging sensor
-
-Required properties:
- - compatible: must be "st,vl53l0x"
- - reg: i2c address where to find the device
-
-Optional properties:
- - interrupts: Interrupt for notifying that new measurement is ready.
- If no interrupt is specified, polling is used.
-
-Example:
-
-vl53l0x@29 {
- compatible = "st,vl53l0x";
- reg = <0x29>;
- interrupt-parent = <&gpio>;
- interrupts = <23 IRQ_TYPE_EDGE_FALLING>;
-};
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 11/29] dt-bindings:iio:proximity:ams,as3935 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (9 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 10/29] dt-bindings:iio:proximity:st,vl53l0x " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 12/29] dt-bindings:iio:dac:ti,dac5571 " Jonathan Cameron
` (18 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Matt Ranostay
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
A straight forward conversion of this binding. I have added
a maximum SPI frequency from the datasheet.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Acked-by: Matt Ranostay <matt.ranostay@konsulko.com>
Cc: Matt Ranostay <matt.ranostay@konsulko.com>
---
.../bindings/iio/proximity/ams,as3935.yaml | 71 +++++++++++++++++++
.../bindings/iio/proximity/as3935.txt | 34 ---------
2 files changed, 71 insertions(+), 34 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/proximity/ams,as3935.yaml b/Documentation/devicetree/bindings/iio/proximity/ams,as3935.yaml
new file mode 100644
index 000000000000..7fcba5d6d508
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/proximity/ams,as3935.yaml
@@ -0,0 +1,71 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/proximity/ams,as3935.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Austrian Microsystems AS3935 Franklin lightning sensor
+
+maintainers:
+ - Matt Ranostay <matt.ranostay@konsulko.com>
+
+description:
+ This lightening distance sensor uses an I2C or SPI interface. The
+ binding currently only covers the SPI option.
+
+properties:
+ compatible:
+ const: ams,as3935
+
+ reg:
+ maxItems: 1
+
+ spi-max-frequency:
+ maximum: 2000000
+
+ spi-cpha: true
+
+ interrupts:
+ maxItems: 1
+
+ ams,tuning-capacitor-pf:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description:
+ Calibration tuning capacitor stepping value. This will require using
+ the calibration data from the manufacturer.
+ minimum: 0
+ maximum: 120
+
+ ams,nflwdth:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description:
+ Set the noise and watchdog threshold register on startup. This will
+ need to set according to the noise from the MCU board, and possibly
+ the local environment. Refer to the datasheet for the threshold settings.
+
+required:
+ - compatible
+ - reg
+ - spi-cpha
+ - interrupts
+
+additionalProperties: false
+
+examples:
+ - |
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ lightning@0 {
+ compatible = "ams,as3935";
+ reg = <0>;
+ spi-max-frequency = <400000>;
+ spi-cpha;
+ interrupt-parent = <&gpio1>;
+ interrupts = <16 1>;
+ ams,tuning-capacitor-pf = <80>;
+ ams,nflwdth = <0x44>;
+ };
+ };
+...
diff --git a/Documentation/devicetree/bindings/iio/proximity/as3935.txt b/Documentation/devicetree/bindings/iio/proximity/as3935.txt
deleted file mode 100644
index 849115585d55..000000000000
--- a/Documentation/devicetree/bindings/iio/proximity/as3935.txt
+++ /dev/null
@@ -1,34 +0,0 @@
-Austrian Microsystems AS3935 Franklin lightning sensor device driver
-
-Required properties:
- - compatible: must be "ams,as3935"
- - reg: SPI chip select number for the device
- - spi-max-frequency: specifies maximum SPI clock frequency
- - spi-cpha: SPI Mode 1. Refer to spi/spi-bus.txt for generic SPI
- slave node bindings.
- - interrupts : the sole interrupt generated by the device
-
- Refer to interrupt-controller/interrupts.txt for generic
- interrupt client node bindings.
-
-Optional properties:
- - ams,tuning-capacitor-pf: Calibration tuning capacitor stepping
- value 0 - 120pF. This will require using the calibration data from
- the manufacturer.
- - ams,nflwdth: Set the noise and watchdog threshold register on
- startup. This will need to set according to the noise from the
- MCU board, and possibly the local environment. Refer to the
- datasheet for the threshold settings.
-
-Example:
-
-as3935@0 {
- compatible = "ams,as3935";
- reg = <0>;
- spi-max-frequency = <400000>;
- spi-cpha;
- interrupt-parent = <&gpio1>;
- interrupts = <16 1>;
- ams,tuning-capacitor-pf = <80>;
- ams,nflwdth = <0x44>;
-};
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 12/29] dt-bindings:iio:dac:ti,dac5571 yaml conversion.
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (10 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 11/29] dt-bindings:iio:proximity:ams,as3935 " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 13/29] dt-bindings:iio:dac:ti,dac7311 " Jonathan Cameron
` (17 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Sean Nyekjaer
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
A few tweaks in this conversion.
* The example didn't have the I2C address of 4C in the node name so
fixed that.
* The reference voltage in the txt file is an optional binding, but
the driver is making use of it to provide the scaling of the output
channels. As such I have made it required going forwards.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Acked-by: Sean Nyekjaer <sean@geanix.com>
Cc: Sean Nyekjaer <sean@geanix.com>
---
.../bindings/iio/dac/ti,dac5571.txt | 24 ---------
.../bindings/iio/dac/ti,dac5571.yaml | 52 +++++++++++++++++++
2 files changed, 52 insertions(+), 24 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac5571.txt b/Documentation/devicetree/bindings/iio/dac/ti,dac5571.txt
deleted file mode 100644
index 03af6b9a4d07..000000000000
--- a/Documentation/devicetree/bindings/iio/dac/ti,dac5571.txt
+++ /dev/null
@@ -1,24 +0,0 @@
-* Texas Instruments DAC5571 Family
-
-Required properties:
- - compatible: Should contain
- "ti,dac5571"
- "ti,dac6571"
- "ti,dac7571"
- "ti,dac5574"
- "ti,dac6574"
- "ti,dac7574"
- "ti,dac5573"
- "ti,dac6573"
- "ti,dac7573"
- - reg: Should contain the DAC I2C address
-
-Optional properties:
- - vref-supply: The regulator supply for DAC reference voltage
-
-Example:
-dac@0 {
- compatible = "ti,dac5571";
- reg = <0x4C>;
- vref-supply = <&vdd_supply>;
-};
diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac5571.yaml b/Documentation/devicetree/bindings/iio/dac/ti,dac5571.yaml
new file mode 100644
index 000000000000..714191724f7c
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/ti,dac5571.yaml
@@ -0,0 +1,52 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/dac/ti,dac5571.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Texas Instruments DAC5571 Family
+
+maintainers:
+ - Sean Nyekjaer <sean@geanix.com>
+
+properties:
+ compatible:
+ enum:
+ - ti,dac5571
+ - ti,dac6571
+ - ti,dac7571
+ - ti,dac5574
+ - ti,dac6574
+ - ti,dac7574
+ - ti,dac5573
+ - ti,dac6573
+ - ti,dac7573
+
+ reg:
+ maxItems: 1
+
+ vref-supply:
+ description:
+ Reference voltage must be supplied to establish the scaling of the
+ output voltage.
+
+required:
+ - compatible
+ - reg
+ - vref-supply
+
+additionalProperties: false
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ dac@4c {
+ compatible = "ti,dac5571";
+ reg = <0x4C>;
+ vref-supply = <&vdd_supply>;
+ };
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 13/29] dt-bindings:iio:dac:ti,dac7311 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (11 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 12/29] dt-bindings:iio:dac:ti,dac5571 " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 14/29] dt-bindings:iio:dac:ti,dac7512 " Jonathan Cameron
` (16 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Charles-Antoine Couret
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Very simple conversion of this binding from txt to yaml.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Cc: Charles-Antoine Couret <charles-antoine.couret@essensium.com>
---
.../bindings/iio/dac/ti,dac7311.txt | 23 ---------
.../bindings/iio/dac/ti,dac7311.yaml | 49 +++++++++++++++++++
2 files changed, 49 insertions(+), 23 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac7311.txt b/Documentation/devicetree/bindings/iio/dac/ti,dac7311.txt
deleted file mode 100644
index e5a507db5e01..000000000000
--- a/Documentation/devicetree/bindings/iio/dac/ti,dac7311.txt
+++ /dev/null
@@ -1,23 +0,0 @@
-TI DAC7311 device tree bindings
-
-Required properties:
-- compatible: must be set to:
- * "ti,dac7311"
- * "ti,dac6311"
- * "ti,dac5311"
-- reg: spi chip select number for the device
-- vref-supply: The regulator supply for ADC reference voltage
-
-Optional properties:
-- spi-max-frequency: Max SPI frequency to use
-
-Example:
-
- spi_master {
- dac@0 {
- compatible = "ti,dac7311";
- reg = <0>; /* CS0 */
- spi-max-frequency = <1000000>;
- vref-supply = <&vdd_supply>;
- };
- };
diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac7311.yaml b/Documentation/devicetree/bindings/iio/dac/ti,dac7311.yaml
new file mode 100644
index 000000000000..10be98d1f19c
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/ti,dac7311.yaml
@@ -0,0 +1,49 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/dac/ti,dac7311.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Texas Instruments DAC5311 and similar SPI DACs
+
+maintainers:
+ - Charles-Antoine Couret <charles-antoine.couret@essensium.com>
+
+properties:
+ compatible:
+ enum:
+ - ti,dac7311
+ - ti,dac6311
+ - ti,dac5311
+
+ reg:
+ maxItems: 1
+
+ vref-supply:
+ description:
+ Reference voltage must be supplied to establish the scaling of the
+ output voltage.
+
+ spi-max-frequency: true
+
+required:
+ - compatible
+ - reg
+ - vref-supply
+
+additionalProperties: false
+
+examples:
+ - |
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ dac@0 {
+ compatible = "ti,dac7311";
+ reg = <0>; /* CS0 */
+ spi-max-frequency = <1000000>;
+ vref-supply = <&vdd_supply>;
+ };
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 14/29] dt-bindings:iio:dac:ti,dac7512 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (12 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 13/29] dt-bindings:iio:dac:ti,dac7311 " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 15/29] dt-bindings:iio:dac:ti,dac7612 " Jonathan Cameron
` (15 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree; +Cc: Jonathan Cameron, Rob Herring
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
This one is a bit interesting because the binding was moved from
misc a while back, but the linux support for this device is
provided via the ad5446 DAC driver which doesn't currently
have a binding.
For now, lets just convert this file over, but we may want to
think about consolidating this with proper documentation of
the bindings for the other parts supported by the ad5446 driver.
As Daniel Mack does not seem to have been active since 2015,
I've put myself as maintainer of this binding for now.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
---
.../bindings/iio/dac/ti,dac7512.txt | 20 ---------
.../bindings/iio/dac/ti,dac7512.yaml | 42 +++++++++++++++++++
2 files changed, 42 insertions(+), 20 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac7512.txt b/Documentation/devicetree/bindings/iio/dac/ti,dac7512.txt
deleted file mode 100644
index 1db45939dac9..000000000000
--- a/Documentation/devicetree/bindings/iio/dac/ti,dac7512.txt
+++ /dev/null
@@ -1,20 +0,0 @@
-TI DAC7512 DEVICETREE BINDINGS
-
-Required properties:
-
- - "compatible" Must be set to "ti,dac7512"
-
-Property rules described in Documentation/devicetree/bindings/spi/spi-bus.txt
-apply. In particular, "reg" and "spi-max-frequency" properties must be given.
-
-
-Example:
-
- spi_master {
- dac7512: dac7512@0 {
- compatible = "ti,dac7512";
- reg = <0>; /* CS0 */
- spi-max-frequency = <1000000>;
- };
- };
-
diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac7512.yaml b/Documentation/devicetree/bindings/iio/dac/ti,dac7512.yaml
new file mode 100644
index 000000000000..4277cf8a4a2e
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/ti,dac7512.yaml
@@ -0,0 +1,42 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/dac/ti,dac7512.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Texas Instruments DAC7512 DAC
+
+maintainers:
+ - Jonathan Cameron <jic23@kernel.org>
+
+properties:
+ compatible:
+ const: ti,dac7512
+
+ reg:
+ maxItems: 1
+
+ spi-max-frequency:
+ description:
+ Maximum frequency is reduced for supply voltage of less than 3.6V
+ maximum: 30000000
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ dac@0 {
+ compatible = "ti,dac7512";
+ reg = <0>; /* CS0 */
+ spi-max-frequency = <1000000>;
+ };
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 15/29] dt-bindings:iio:dac:ti,dac7612 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (13 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 14/29] dt-bindings:iio:dac:ti,dac7512 " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 16/29] dt-bindings:iio:dac:ti,dac082s085 " Jonathan Cameron
` (14 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Ricardo Ribalda Delgado
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Simple conversion from txt to yaml. No significant adjustments.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Acked-by: Ricardo Ribalda Delgado <ricardo@ribalda.com>
---
.../bindings/iio/dac/ti,dac7612.txt | 28 ----------
.../bindings/iio/dac/ti,dac7612.yaml | 53 +++++++++++++++++++
2 files changed, 53 insertions(+), 28 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac7612.txt b/Documentation/devicetree/bindings/iio/dac/ti,dac7612.txt
deleted file mode 100644
index 17af395b99d9..000000000000
--- a/Documentation/devicetree/bindings/iio/dac/ti,dac7612.txt
+++ /dev/null
@@ -1,28 +0,0 @@
-* Texas Instruments Dual, 12-Bit Serial Input Digital-to-Analog Converter
-
-The DAC7612 is a dual, 12-bit digital-to-analog converter (DAC) with guaranteed
-12-bit monotonicity performance over the industrial temperature range.
-Is is programmable through an SPI interface.
-
-The internal DACs are loaded when the LOADDACS pin is pulled down.
-
-https://www.ti.com/lit/ds/sbas106/sbas106.pdf
-
-Required Properties:
-- compatible: Should be one of:
- "ti,dac7612"
- "ti,dac7612u"
- "ti,dac7612ub"
-- reg: Definition as per Documentation/devicetree/bindings/spi/spi-bus.txt
-
-Optional Properties:
-- ti,loaddacs-gpios: GPIO descriptor for the LOADDACS pin.
-- spi-*: Definition as per Documentation/devicetree/bindings/spi/spi-bus.txt
-
-Example:
-
- dac@1 {
- compatible = "ti,dac7612";
- reg = <0x1>;
- ti,loaddacs-gpios = <&msmgpio 25 GPIO_ACTIVE_LOW>;
- };
diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac7612.yaml b/Documentation/devicetree/bindings/iio/dac/ti,dac7612.yaml
new file mode 100644
index 000000000000..d172b142f6ed
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/ti,dac7612.yaml
@@ -0,0 +1,53 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/dac/ti,dac7612.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Texas Instruments DAC7612 family of DACs
+
+description:
+ The DAC7612 is a dual, 12-bit digital-to-analog converter (DAC) with
+ guaranteed 12-bit monotonicity performance over the industrial temperature
+ range. Is is programmable through an SPI interface.
+
+maintainers:
+ - Ricardo Ribalda Delgado <ricardo@ribalda.com>
+
+properties:
+ compatible:
+ enum:
+ - ti,dac7612
+ - ti,dac7612u
+ - ti,dac7612ub
+
+ reg:
+ maxItems: 1
+
+ ti,loaddacs-gpios:
+ description:
+ DACs are loaded when the pin connected to this GPIO is pulled low.
+ maxItems: 1
+
+ spi-max-frequency: true
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ dac@1 {
+ compatible = "ti,dac7612";
+ reg = <0x1>;
+ ti,loaddacs-gpios = <&msmgpio 25 GPIO_ACTIVE_LOW>;
+ };
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 16/29] dt-bindings:iio:dac:ti,dac082s085 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (14 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 15/29] dt-bindings:iio:dac:ti,dac7612 " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 16:58 ` Lukas Wunner
2020-11-03 2:21 ` Rob Herring
2020-10-31 13:40 ` [PATCH v2 17/29] dt-bindings:iio:dac:adi,ad7303 " Jonathan Cameron
` (13 subsequent siblings)
29 siblings, 2 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree; +Cc: Jonathan Cameron, Lukas Wunner
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Fairly simple conversion with the exception of the XOR between
spi-cpha and spi-cpol.
Is there a better way to specify that?
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Lukas Wunner <lukas@wunner.de>
---
v2:
* Family typo
* Put back the reference regulator in example.
* Added checking of XOR of spi-cpha and spi-cpol
(dropped Rob Herrings Reviewed-by due to this change)
.../bindings/iio/dac/ti,dac082s085.yaml | 79 +++++++++++++++++++
.../bindings/iio/dac/ti-dac082s085.txt | 34 --------
2 files changed, 79 insertions(+), 34 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml b/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml
new file mode 100644
index 000000000000..192b314c99d1
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml
@@ -0,0 +1,79 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/dac/ti,dac082s085.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Texas Instruments DAC082s085 and similar DACs
+
+description:
+ A family of Texas Instruments 8/10/12-bit 2/4-channel DACs
+
+maintainers:
+ - Lukas Wunner <lukas@wunner.de>
+
+properties:
+ compatible:
+ enum:
+ - ti,dac082s085
+ - ti,dac102s085
+ - ti,dac122s085
+ - ti,dac084s085
+ - ti,dac104s085
+ - ti,dac124s085
+
+ reg:
+ maxItems: 1
+
+ spi-cpha: true
+ spi-cpol:
+ description:
+ Should be either spi-cpha, or spi-cpol but not both.
+
+ vref-supply:
+ description: Needed to provide output scaling.
+
+ spi-max-frequency: true
+
+required:
+ - compatible
+ - reg
+ - vref-supply
+
+additionalProperties: false
+
+allOf:
+ - $ref: '#/definitions/cpolXORcpha'
+
+definitions:
+ cpolXORcpha:
+ not:
+ required: [spi-cpha, spi-cpol]
+ oneOf:
+ - required:
+ - spi-cpha
+ - required:
+ - spi-cpol
+
+examples:
+ - |
+ vref_2v5_reg: regulator-vref {
+ compatible = "regulator-fixed";
+ regulator-name = "2v5";
+ regulator-min-microvolt = <2500000>;
+ regulator-max-microvolt = <2500000>;
+ regulator-always-on;
+ };
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ dac@0 {
+ compatible = "ti,dac082s085";
+ reg = <0>;
+ spi-max-frequency = <40000000>;
+ spi-cpol;
+ vref-supply = <&vref_2v5_reg>;
+ };
+ };
+...
diff --git a/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt b/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
deleted file mode 100644
index 9cb0e10df704..000000000000
--- a/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
+++ /dev/null
@@ -1,34 +0,0 @@
-Texas Instruments 8/10/12-bit 2/4-channel DAC driver
-
-Required properties:
- - compatible: Must be one of:
- "ti,dac082s085"
- "ti,dac102s085"
- "ti,dac122s085"
- "ti,dac084s085"
- "ti,dac104s085"
- "ti,dac124s085"
- - reg: Chip select number.
- - spi-cpha, spi-cpol: SPI mode (0,1) or (1,0) must be used, so specify
- either spi-cpha or spi-cpol (but not both).
- - vref-supply: Phandle to the external reference voltage supply.
-
-For other required and optional properties of SPI slave nodes please refer to
-../../spi/spi-bus.txt.
-
-Example:
- vref_2v5_reg: regulator-vref {
- compatible = "regulator-fixed";
- regulator-name = "2v5";
- regulator-min-microvolt = <2500000>;
- regulator-max-microvolt = <2500000>;
- regulator-always-on;
- };
-
- dac@0 {
- compatible = "ti,dac082s085";
- reg = <0>;
- spi-max-frequency = <40000000>;
- spi-cpol;
- vref-supply = <&vref_2v5_reg>;
- };
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* Re: [PATCH v2 16/29] dt-bindings:iio:dac:ti,dac082s085 yaml conversion
2020-10-31 13:40 ` [PATCH v2 16/29] dt-bindings:iio:dac:ti,dac082s085 " Jonathan Cameron
@ 2020-10-31 16:58 ` Lukas Wunner
2020-10-31 18:11 ` Jonathan Cameron
2020-11-03 2:21 ` Rob Herring
1 sibling, 1 reply; 40+ messages in thread
From: Lukas Wunner @ 2020-10-31 16:58 UTC (permalink / raw)
To: Jonathan Cameron; +Cc: linux-iio, Rob Herring, devicetree, Jonathan Cameron
On Sat, Oct 31, 2020 at 01:40:57PM +0000, Jonathan Cameron wrote:
> + spi-cpha: true
> + spi-cpol:
> + description:
> + Should be either spi-cpha, or spi-cpol but not both.
Do the YAML files follow RFC 2119 terminology? If so, this is a
"must", not a "should". (As it was in the txt file.)
> +required:
> + - compatible
> + - reg
> + - vref-supply
This is missing "spi-cpha xor spi-cpol", not sure if it can be
specified here using the xor YAML trick.
Thanks,
Lukas
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [PATCH v2 16/29] dt-bindings:iio:dac:ti,dac082s085 yaml conversion
2020-10-31 16:58 ` Lukas Wunner
@ 2020-10-31 18:11 ` Jonathan Cameron
0 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 18:11 UTC (permalink / raw)
To: Lukas Wunner; +Cc: linux-iio, Rob Herring, devicetree, Jonathan Cameron
On Sat, 31 Oct 2020 17:58:36 +0100
Lukas Wunner <lukas@wunner.de> wrote:
> On Sat, Oct 31, 2020 at 01:40:57PM +0000, Jonathan Cameron wrote:
> > + spi-cpha: true
> > + spi-cpol:
> > + description:
> > + Should be either spi-cpha, or spi-cpol but not both.
>
> Do the YAML files follow RFC 2119 terminology? If so, this is a
> "must", not a "should". (As it was in the txt file.)
I'll fix that whilst applying if it is all we have outstanding.
This is an information comment only as the actual enforcement is
below.
>
>
> > +required:
> > + - compatible
> > + - reg
> > + - vref-supply
>
> This is missing "spi-cpha xor spi-cpol", not sure if it can be
> specified here using the xor YAML trick.
It has to be specified in a separate block as far as I can tell.
That is done further down the file. I've tested all the combinations
and xor is enforced.
+allOf:
+ - $ref: '#/definitions/cpolXORcpha'
+
+definitions:
+ cpolXORcpha:
+ not:
+ required: [spi-cpha, spi-cpol]
+ oneOf:
+ - required:
+ - spi-cpha
+ - required:
+ - spi-cpol
+
>
> Thanks,
>
> Lukas
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [PATCH v2 16/29] dt-bindings:iio:dac:ti,dac082s085 yaml conversion
2020-10-31 13:40 ` [PATCH v2 16/29] dt-bindings:iio:dac:ti,dac082s085 " Jonathan Cameron
2020-10-31 16:58 ` Lukas Wunner
@ 2020-11-03 2:21 ` Rob Herring
2020-11-08 16:34 ` Jonathan Cameron
1 sibling, 1 reply; 40+ messages in thread
From: Rob Herring @ 2020-11-03 2:21 UTC (permalink / raw)
To: Jonathan Cameron; +Cc: linux-iio, devicetree, Jonathan Cameron, Lukas Wunner
On Sat, Oct 31, 2020 at 01:40:57PM +0000, Jonathan Cameron wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> Fairly simple conversion with the exception of the XOR between
> spi-cpha and spi-cpol.
>
> Is there a better way to specify that?
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Cc: Lukas Wunner <lukas@wunner.de>
> ---
> v2:
> * Family typo
> * Put back the reference regulator in example.
> * Added checking of XOR of spi-cpha and spi-cpol
> (dropped Rob Herrings Reviewed-by due to this change)
>
> .../bindings/iio/dac/ti,dac082s085.yaml | 79 +++++++++++++++++++
> .../bindings/iio/dac/ti-dac082s085.txt | 34 --------
> 2 files changed, 79 insertions(+), 34 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml b/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml
> new file mode 100644
> index 000000000000..192b314c99d1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml
> @@ -0,0 +1,79 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/dac/ti,dac082s085.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Texas Instruments DAC082s085 and similar DACs
> +
> +description:
> + A family of Texas Instruments 8/10/12-bit 2/4-channel DACs
> +
> +maintainers:
> + - Lukas Wunner <lukas@wunner.de>
> +
> +properties:
> + compatible:
> + enum:
> + - ti,dac082s085
> + - ti,dac102s085
> + - ti,dac122s085
> + - ti,dac084s085
> + - ti,dac104s085
> + - ti,dac124s085
> +
> + reg:
> + maxItems: 1
> +
> + spi-cpha: true
> + spi-cpol:
> + description:
> + Should be either spi-cpha, or spi-cpol but not both.
> +
> + vref-supply:
> + description: Needed to provide output scaling.
> +
> + spi-max-frequency: true
> +
> +required:
> + - compatible
> + - reg
> + - vref-supply
> +
> +additionalProperties: false
> +
> +allOf:
> + - $ref: '#/definitions/cpolXORcpha'
> +
> +definitions:
> + cpolXORcpha:
No need for a definition. Just put the below in the allOf entry.
> + not:
> + required: [spi-cpha, spi-cpol]
> + oneOf:
> + - required:
> + - spi-cpha
> + - required:
> + - spi-cpol
> +
> +examples:
> + - |
> + vref_2v5_reg: regulator-vref {
> + compatible = "regulator-fixed";
> + regulator-name = "2v5";
> + regulator-min-microvolt = <2500000>;
> + regulator-max-microvolt = <2500000>;
> + regulator-always-on;
> + };
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + dac@0 {
> + compatible = "ti,dac082s085";
> + reg = <0>;
> + spi-max-frequency = <40000000>;
> + spi-cpol;
> + vref-supply = <&vref_2v5_reg>;
> + };
> + };
> +...
> diff --git a/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt b/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
> deleted file mode 100644
> index 9cb0e10df704..000000000000
> --- a/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
> +++ /dev/null
> @@ -1,34 +0,0 @@
> -Texas Instruments 8/10/12-bit 2/4-channel DAC driver
> -
> -Required properties:
> - - compatible: Must be one of:
> - "ti,dac082s085"
> - "ti,dac102s085"
> - "ti,dac122s085"
> - "ti,dac084s085"
> - "ti,dac104s085"
> - "ti,dac124s085"
> - - reg: Chip select number.
> - - spi-cpha, spi-cpol: SPI mode (0,1) or (1,0) must be used, so specify
> - either spi-cpha or spi-cpol (but not both).
> - - vref-supply: Phandle to the external reference voltage supply.
> -
> -For other required and optional properties of SPI slave nodes please refer to
> -../../spi/spi-bus.txt.
> -
> -Example:
> - vref_2v5_reg: regulator-vref {
> - compatible = "regulator-fixed";
> - regulator-name = "2v5";
> - regulator-min-microvolt = <2500000>;
> - regulator-max-microvolt = <2500000>;
> - regulator-always-on;
> - };
> -
> - dac@0 {
> - compatible = "ti,dac082s085";
> - reg = <0>;
> - spi-max-frequency = <40000000>;
> - spi-cpol;
> - vref-supply = <&vref_2v5_reg>;
> - };
> --
> 2.28.0
>
^ permalink raw reply [flat|nested] 40+ messages in thread* Re: [PATCH v2 16/29] dt-bindings:iio:dac:ti,dac082s085 yaml conversion
2020-11-03 2:21 ` Rob Herring
@ 2020-11-08 16:34 ` Jonathan Cameron
2021-03-14 19:07 ` Jonathan Cameron
0 siblings, 1 reply; 40+ messages in thread
From: Jonathan Cameron @ 2020-11-08 16:34 UTC (permalink / raw)
To: Rob Herring; +Cc: linux-iio, devicetree, Jonathan Cameron, Lukas Wunner
On Mon, 2 Nov 2020 20:21:08 -0600
Rob Herring <robh@kernel.org> wrote:
> On Sat, Oct 31, 2020 at 01:40:57PM +0000, Jonathan Cameron wrote:
> > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> >
> > Fairly simple conversion with the exception of the XOR between
> > spi-cpha and spi-cpol.
> >
> > Is there a better way to specify that?
> >
> > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > Cc: Lukas Wunner <lukas@wunner.de>
> > ---
> > v2:
> > * Family typo
> > * Put back the reference regulator in example.
> > * Added checking of XOR of spi-cpha and spi-cpol
> > (dropped Rob Herrings Reviewed-by due to this change)
> >
> > .../bindings/iio/dac/ti,dac082s085.yaml | 79 +++++++++++++++++++
> > .../bindings/iio/dac/ti-dac082s085.txt | 34 --------
> > 2 files changed, 79 insertions(+), 34 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml b/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml
> > new file mode 100644
> > index 000000000000..192b314c99d1
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml
> > @@ -0,0 +1,79 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/iio/dac/ti,dac082s085.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Texas Instruments DAC082s085 and similar DACs
> > +
> > +description:
> > + A family of Texas Instruments 8/10/12-bit 2/4-channel DACs
> > +
> > +maintainers:
> > + - Lukas Wunner <lukas@wunner.de>
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - ti,dac082s085
> > + - ti,dac102s085
> > + - ti,dac122s085
> > + - ti,dac084s085
> > + - ti,dac104s085
> > + - ti,dac124s085
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + spi-cpha: true
> > + spi-cpol:
> > + description:
> > + Should be either spi-cpha, or spi-cpol but not both.
> > +
> > + vref-supply:
> > + description: Needed to provide output scaling.
> > +
> > + spi-max-frequency: true
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - vref-supply
> > +
> > +additionalProperties: false
> > +
> > +allOf:
> > + - $ref: '#/definitions/cpolXORcpha'
> > +
> > +definitions:
> > + cpolXORcpha:
>
> No need for a definition. Just put the below in the allOf entry.
I can't figure out the syntax to do that.
If I put it directly there I get,
... iio/dac/ti,dac082s085.yaml: allOf:0: 'not' is not one of ['$ref', 'if', 'then', 'else']
The use of $ref was the only way I could find to get around this.
What other option is there? My Yaml is still largely cut and paste
based so not sure I fully understand the restrictions that are applied.
Thanks,
Jonathan
>
> > + not:
> > + required: [spi-cpha, spi-cpol]
> > + oneOf:
> > + - required:
> > + - spi-cpha
> > + - required:
> > + - spi-cpol
> > +
> > +examples:
> > + - |
> > + vref_2v5_reg: regulator-vref {
> > + compatible = "regulator-fixed";
> > + regulator-name = "2v5";
> > + regulator-min-microvolt = <2500000>;
> > + regulator-max-microvolt = <2500000>;
> > + regulator-always-on;
> > + };
> > + spi {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + dac@0 {
> > + compatible = "ti,dac082s085";
> > + reg = <0>;
> > + spi-max-frequency = <40000000>;
> > + spi-cpol;
> > + vref-supply = <&vref_2v5_reg>;
> > + };
> > + };
> > +...
> > diff --git a/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt b/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
> > deleted file mode 100644
> > index 9cb0e10df704..000000000000
> > --- a/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
> > +++ /dev/null
> > @@ -1,34 +0,0 @@
> > -Texas Instruments 8/10/12-bit 2/4-channel DAC driver
> > -
> > -Required properties:
> > - - compatible: Must be one of:
> > - "ti,dac082s085"
> > - "ti,dac102s085"
> > - "ti,dac122s085"
> > - "ti,dac084s085"
> > - "ti,dac104s085"
> > - "ti,dac124s085"
> > - - reg: Chip select number.
> > - - spi-cpha, spi-cpol: SPI mode (0,1) or (1,0) must be used, so specify
> > - either spi-cpha or spi-cpol (but not both).
> > - - vref-supply: Phandle to the external reference voltage supply.
> > -
> > -For other required and optional properties of SPI slave nodes please refer to
> > -../../spi/spi-bus.txt.
> > -
> > -Example:
> > - vref_2v5_reg: regulator-vref {
> > - compatible = "regulator-fixed";
> > - regulator-name = "2v5";
> > - regulator-min-microvolt = <2500000>;
> > - regulator-max-microvolt = <2500000>;
> > - regulator-always-on;
> > - };
> > -
> > - dac@0 {
> > - compatible = "ti,dac082s085";
> > - reg = <0>;
> > - spi-max-frequency = <40000000>;
> > - spi-cpol;
> > - vref-supply = <&vref_2v5_reg>;
> > - };
> > --
> > 2.28.0
> >
^ permalink raw reply [flat|nested] 40+ messages in thread* Re: [PATCH v2 16/29] dt-bindings:iio:dac:ti,dac082s085 yaml conversion
2020-11-08 16:34 ` Jonathan Cameron
@ 2021-03-14 19:07 ` Jonathan Cameron
2021-03-14 19:23 ` Jonathan Cameron
0 siblings, 1 reply; 40+ messages in thread
From: Jonathan Cameron @ 2021-03-14 19:07 UTC (permalink / raw)
To: Rob Herring; +Cc: linux-iio, devicetree, Jonathan Cameron, Lukas Wunner
On Sun, 8 Nov 2020 16:34:51 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> On Mon, 2 Nov 2020 20:21:08 -0600
> Rob Herring <robh@kernel.org> wrote:
>
> > On Sat, Oct 31, 2020 at 01:40:57PM +0000, Jonathan Cameron wrote:
> > > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > >
> > > Fairly simple conversion with the exception of the XOR between
> > > spi-cpha and spi-cpol.
> > >
> > > Is there a better way to specify that?
> > >
> > > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > > Cc: Lukas Wunner <lukas@wunner.de>
> > > ---
> > > v2:
> > > * Family typo
> > > * Put back the reference regulator in example.
> > > * Added checking of XOR of spi-cpha and spi-cpol
> > > (dropped Rob Herrings Reviewed-by due to this change)
> > >
> > > .../bindings/iio/dac/ti,dac082s085.yaml | 79 +++++++++++++++++++
> > > .../bindings/iio/dac/ti-dac082s085.txt | 34 --------
> > > 2 files changed, 79 insertions(+), 34 deletions(-)
> > >
> > > diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml b/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml
> > > new file mode 100644
> > > index 000000000000..192b314c99d1
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml
> > > @@ -0,0 +1,79 @@
> > > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/iio/dac/ti,dac082s085.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: Texas Instruments DAC082s085 and similar DACs
> > > +
> > > +description:
> > > + A family of Texas Instruments 8/10/12-bit 2/4-channel DACs
> > > +
> > > +maintainers:
> > > + - Lukas Wunner <lukas@wunner.de>
> > > +
> > > +properties:
> > > + compatible:
> > > + enum:
> > > + - ti,dac082s085
> > > + - ti,dac102s085
> > > + - ti,dac122s085
> > > + - ti,dac084s085
> > > + - ti,dac104s085
> > > + - ti,dac124s085
> > > +
> > > + reg:
> > > + maxItems: 1
> > > +
> > > + spi-cpha: true
> > > + spi-cpol:
> > > + description:
> > > + Should be either spi-cpha, or spi-cpol but not both.
> > > +
> > > + vref-supply:
> > > + description: Needed to provide output scaling.
> > > +
> > > + spi-max-frequency: true
> > > +
> > > +required:
> > > + - compatible
> > > + - reg
> > > + - vref-supply
> > > +
> > > +additionalProperties: false
> > > +
> > > +allOf:
> > > + - $ref: '#/definitions/cpolXORcpha'
> > > +
> > > +definitions:
> > > + cpolXORcpha:
> >
> > No need for a definition. Just put the below in the allOf entry.
>
> I can't figure out the syntax to do that.
> If I put it directly there I get,
>
> ... iio/dac/ti,dac082s085.yaml: allOf:0: 'not' is not one of ['$ref', 'if', 'then', 'else']
>
> The use of $ref was the only way I could find to get around this.
> What other option is there? My Yaml is still largely cut and paste
> based so not sure I fully understand the restrictions that are applied.
Hi Rob,
I've had another go at playing with the syntax but still can't find a way around the above
issue if I try to get rid of the definitions block as you suggest.
Any pointers on the syntax very much appreciated!
Thanks
Jonathan
>
> Thanks,
>
> Jonathan
>
>
>
> >
> > > + not:
> > > + required: [spi-cpha, spi-cpol]
> > > + oneOf:
> > > + - required:
> > > + - spi-cpha
> > > + - required:
> > > + - spi-cpol
> > > +
> > > +examples:
> > > + - |
> > > + vref_2v5_reg: regulator-vref {
> > > + compatible = "regulator-fixed";
> > > + regulator-name = "2v5";
> > > + regulator-min-microvolt = <2500000>;
> > > + regulator-max-microvolt = <2500000>;
> > > + regulator-always-on;
> > > + };
> > > + spi {
> > > + #address-cells = <1>;
> > > + #size-cells = <0>;
> > > +
> > > + dac@0 {
> > > + compatible = "ti,dac082s085";
> > > + reg = <0>;
> > > + spi-max-frequency = <40000000>;
> > > + spi-cpol;
> > > + vref-supply = <&vref_2v5_reg>;
> > > + };
> > > + };
> > > +...
> > > diff --git a/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt b/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
> > > deleted file mode 100644
> > > index 9cb0e10df704..000000000000
> > > --- a/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
> > > +++ /dev/null
> > > @@ -1,34 +0,0 @@
> > > -Texas Instruments 8/10/12-bit 2/4-channel DAC driver
> > > -
> > > -Required properties:
> > > - - compatible: Must be one of:
> > > - "ti,dac082s085"
> > > - "ti,dac102s085"
> > > - "ti,dac122s085"
> > > - "ti,dac084s085"
> > > - "ti,dac104s085"
> > > - "ti,dac124s085"
> > > - - reg: Chip select number.
> > > - - spi-cpha, spi-cpol: SPI mode (0,1) or (1,0) must be used, so specify
> > > - either spi-cpha or spi-cpol (but not both).
> > > - - vref-supply: Phandle to the external reference voltage supply.
> > > -
> > > -For other required and optional properties of SPI slave nodes please refer to
> > > -../../spi/spi-bus.txt.
> > > -
> > > -Example:
> > > - vref_2v5_reg: regulator-vref {
> > > - compatible = "regulator-fixed";
> > > - regulator-name = "2v5";
> > > - regulator-min-microvolt = <2500000>;
> > > - regulator-max-microvolt = <2500000>;
> > > - regulator-always-on;
> > > - };
> > > -
> > > - dac@0 {
> > > - compatible = "ti,dac082s085";
> > > - reg = <0>;
> > > - spi-max-frequency = <40000000>;
> > > - spi-cpol;
> > > - vref-supply = <&vref_2v5_reg>;
> > > - };
> > > --
> > > 2.28.0
> > >
>
^ permalink raw reply [flat|nested] 40+ messages in thread* Re: [PATCH v2 16/29] dt-bindings:iio:dac:ti,dac082s085 yaml conversion
2021-03-14 19:07 ` Jonathan Cameron
@ 2021-03-14 19:23 ` Jonathan Cameron
0 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2021-03-14 19:23 UTC (permalink / raw)
To: Rob Herring; +Cc: linux-iio, devicetree, Jonathan Cameron, Lukas Wunner
On Sun, 14 Mar 2021 19:07:54 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> On Sun, 8 Nov 2020 16:34:51 +0000
> Jonathan Cameron <jic23@kernel.org> wrote:
>
> > On Mon, 2 Nov 2020 20:21:08 -0600
> > Rob Herring <robh@kernel.org> wrote:
> >
> > > On Sat, Oct 31, 2020 at 01:40:57PM +0000, Jonathan Cameron wrote:
> > > > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > > >
> > > > Fairly simple conversion with the exception of the XOR between
> > > > spi-cpha and spi-cpol.
> > > >
> > > > Is there a better way to specify that?
> > > >
> > > > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > > > Cc: Lukas Wunner <lukas@wunner.de>
> > > > ---
> > > > v2:
> > > > * Family typo
> > > > * Put back the reference regulator in example.
> > > > * Added checking of XOR of spi-cpha and spi-cpol
> > > > (dropped Rob Herrings Reviewed-by due to this change)
> > > >
> > > > .../bindings/iio/dac/ti,dac082s085.yaml | 79 +++++++++++++++++++
> > > > .../bindings/iio/dac/ti-dac082s085.txt | 34 --------
> > > > 2 files changed, 79 insertions(+), 34 deletions(-)
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml b/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml
> > > > new file mode 100644
> > > > index 000000000000..192b314c99d1
> > > > --- /dev/null
> > > > +++ b/Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml
> > > > @@ -0,0 +1,79 @@
> > > > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > > > +%YAML 1.2
> > > > +---
> > > > +$id: http://devicetree.org/schemas/iio/dac/ti,dac082s085.yaml#
> > > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > > +
> > > > +title: Texas Instruments DAC082s085 and similar DACs
> > > > +
> > > > +description:
> > > > + A family of Texas Instruments 8/10/12-bit 2/4-channel DACs
> > > > +
> > > > +maintainers:
> > > > + - Lukas Wunner <lukas@wunner.de>
> > > > +
> > > > +properties:
> > > > + compatible:
> > > > + enum:
> > > > + - ti,dac082s085
> > > > + - ti,dac102s085
> > > > + - ti,dac122s085
> > > > + - ti,dac084s085
> > > > + - ti,dac104s085
> > > > + - ti,dac124s085
> > > > +
> > > > + reg:
> > > > + maxItems: 1
> > > > +
> > > > + spi-cpha: true
> > > > + spi-cpol:
> > > > + description:
> > > > + Should be either spi-cpha, or spi-cpol but not both.
> > > > +
> > > > + vref-supply:
> > > > + description: Needed to provide output scaling.
> > > > +
> > > > + spi-max-frequency: true
> > > > +
> > > > +required:
> > > > + - compatible
> > > > + - reg
> > > > + - vref-supply
> > > > +
> > > > +additionalProperties: false
> > > > +
> > > > +allOf:
> > > > + - $ref: '#/definitions/cpolXORcpha'
> > > > +
> > > > +definitions:
> > > > + cpolXORcpha:
> > >
> > > No need for a definition. Just put the below in the allOf entry.
> >
> > I can't figure out the syntax to do that.
> > If I put it directly there I get,
> >
> > ... iio/dac/ti,dac082s085.yaml: allOf:0: 'not' is not one of ['$ref', 'if', 'then', 'else']
> >
> > The use of $ref was the only way I could find to get around this.
> > What other option is there? My Yaml is still largely cut and paste
> > based so not sure I fully understand the restrictions that are applied.
>
> Hi Rob,
>
> I've had another go at playing with the syntax but still can't find a way around the above
> issue if I try to get rid of the definitions block as you suggest.
>
> Any pointers on the syntax very much appreciated!
Little more digging. So that restriction is coming from base.yaml
Not sure if the following 'fix' is fine though.. :)
diff --git a/meta-schemas/base.yaml b/meta-schemas/base.yaml
index a63e1ec18b2a..6d38ed1be3d2 100644
--- a/meta-schemas/base.yaml
+++ b/meta-schemas/base.yaml
@@ -39,6 +39,7 @@ properties:
- if
- then
- else
+ - not
anyOf: true
oneOf: true
definitions: true
>
> Thanks
>
> Jonathan
>
> >
> > Thanks,
> >
> > Jonathan
> >
> >
> >
> > >
> > > > + not:
> > > > + required: [spi-cpha, spi-cpol]
> > > > + oneOf:
> > > > + - required:
> > > > + - spi-cpha
> > > > + - required:
> > > > + - spi-cpol
> > > > +
> > > > +examples:
> > > > + - |
> > > > + vref_2v5_reg: regulator-vref {
> > > > + compatible = "regulator-fixed";
> > > > + regulator-name = "2v5";
> > > > + regulator-min-microvolt = <2500000>;
> > > > + regulator-max-microvolt = <2500000>;
> > > > + regulator-always-on;
> > > > + };
> > > > + spi {
> > > > + #address-cells = <1>;
> > > > + #size-cells = <0>;
> > > > +
> > > > + dac@0 {
> > > > + compatible = "ti,dac082s085";
> > > > + reg = <0>;
> > > > + spi-max-frequency = <40000000>;
> > > > + spi-cpol;
> > > > + vref-supply = <&vref_2v5_reg>;
> > > > + };
> > > > + };
> > > > +...
> > > > diff --git a/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt b/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
> > > > deleted file mode 100644
> > > > index 9cb0e10df704..000000000000
> > > > --- a/Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
> > > > +++ /dev/null
> > > > @@ -1,34 +0,0 @@
> > > > -Texas Instruments 8/10/12-bit 2/4-channel DAC driver
> > > > -
> > > > -Required properties:
> > > > - - compatible: Must be one of:
> > > > - "ti,dac082s085"
> > > > - "ti,dac102s085"
> > > > - "ti,dac122s085"
> > > > - "ti,dac084s085"
> > > > - "ti,dac104s085"
> > > > - "ti,dac124s085"
> > > > - - reg: Chip select number.
> > > > - - spi-cpha, spi-cpol: SPI mode (0,1) or (1,0) must be used, so specify
> > > > - either spi-cpha or spi-cpol (but not both).
> > > > - - vref-supply: Phandle to the external reference voltage supply.
> > > > -
> > > > -For other required and optional properties of SPI slave nodes please refer to
> > > > -../../spi/spi-bus.txt.
> > > > -
> > > > -Example:
> > > > - vref_2v5_reg: regulator-vref {
> > > > - compatible = "regulator-fixed";
> > > > - regulator-name = "2v5";
> > > > - regulator-min-microvolt = <2500000>;
> > > > - regulator-max-microvolt = <2500000>;
> > > > - regulator-always-on;
> > > > - };
> > > > -
> > > > - dac@0 {
> > > > - compatible = "ti,dac082s085";
> > > > - reg = <0>;
> > > > - spi-max-frequency = <40000000>;
> > > > - spi-cpol;
> > > > - vref-supply = <&vref_2v5_reg>;
> > > > - };
> > > > --
> > > > 2.28.0
> > > >
> >
>
^ permalink raw reply related [flat|nested] 40+ messages in thread
* [PATCH v2 17/29] dt-bindings:iio:dac:adi,ad7303 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (15 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 16/29] dt-bindings:iio:dac:ti,dac082s085 " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:40 ` [PATCH v2 18/29] dt-bindings:iio:dac:maxim,ds4424 " Jonathan Cameron
` (12 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Lars-Peter Clausen
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Converted to maintain the requirement for Vdd-supply as per original file.
It is possible we could relax this requirement to make it at least one
of Vdd-supply and REF-supply. We need to establish the scaling of the
output channel and if REF-supply is provided that is used instead of
Vdd-supply, hence I cannot see why a dummy regulator cannot be used for
Vdd-supply if this happens.
For now, let us keep it simple.
Drop adi,use-external-reference from binding example as no such binding
exists.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>
---
.../devicetree/bindings/iio/dac/ad7303.txt | 23 ---------
.../bindings/iio/dac/adi,ad7303.yaml | 50 +++++++++++++++++++
2 files changed, 50 insertions(+), 23 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/dac/ad7303.txt b/Documentation/devicetree/bindings/iio/dac/ad7303.txt
deleted file mode 100644
index 914610f0556e..000000000000
--- a/Documentation/devicetree/bindings/iio/dac/ad7303.txt
+++ /dev/null
@@ -1,23 +0,0 @@
-Analog Devices AD7303 DAC device driver
-
-Required properties:
- - compatible: Must be "adi,ad7303"
- - reg: SPI chip select number for the device
- - spi-max-frequency: Max SPI frequency to use (< 30000000)
- - Vdd-supply: Phandle to the Vdd power supply
-
-Optional properties:
- - REF-supply: Phandle to the external reference voltage supply. This should
- only be set if there is an external reference voltage connected to the REF
- pin. If the property is not set Vdd/2 is used as the reference voltage.
-
-Example:
-
- ad7303@4 {
- compatible = "adi,ad7303";
- reg = <4>;
- spi-max-frequency = <10000000>;
- Vdd-supply = <&vdd_supply>;
- adi,use-external-reference;
- REF-supply = <&vref_supply>;
- };
diff --git a/Documentation/devicetree/bindings/iio/dac/adi,ad7303.yaml b/Documentation/devicetree/bindings/iio/dac/adi,ad7303.yaml
new file mode 100644
index 000000000000..1f0037152095
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/adi,ad7303.yaml
@@ -0,0 +1,50 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/dac/adi,ad7303.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Analog Devices AD7303 DAC
+
+maintainers:
+ - Lars-Peter Clausen <lars@metafoo.de>
+
+properties:
+ compatible:
+ const: adi,ad7303
+
+ reg:
+ maxItems: 1
+
+ Vdd-supply:
+ description:
+ Used to calculate output channel scalling if REF-supply not specified.
+ REF-supply:
+ description:
+ If not provided, Vdd/2 is used as the reference voltage.
+
+ spi-max-frequency:
+ maximum: 30000000
+
+required:
+ - compatible
+ - reg
+ - Vdd-supply
+
+additionalProperties: false
+
+examples:
+ - |
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ dac@4 {
+ compatible = "adi,ad7303";
+ reg = <4>;
+ spi-max-frequency = <10000000>;
+ Vdd-supply = <&vdd_supply>;
+ REF-supply = <&vref_supply>;
+ };
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 18/29] dt-bindings:iio:dac:maxim,ds4424 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (16 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 17/29] dt-bindings:iio:dac:adi,ad7303 " Jonathan Cameron
@ 2020-10-31 13:40 ` Jonathan Cameron
2020-10-31 13:41 ` [PATCH v2 19/29] dt-bindings:iio:dac:fsl,vf610-dac " Jonathan Cameron
` (11 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:40 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Ismail H . Kose
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Simple conversion of this straight forward binding.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Cc: Ismail H. Kose <ihkose@gmail.com>
---
.../devicetree/bindings/iio/dac/ds4424.txt | 20 ---------
.../bindings/iio/dac/maxim,ds4424.yaml | 45 +++++++++++++++++++
2 files changed, 45 insertions(+), 20 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/dac/ds4424.txt b/Documentation/devicetree/bindings/iio/dac/ds4424.txt
deleted file mode 100644
index eaebbf8dab40..000000000000
--- a/Documentation/devicetree/bindings/iio/dac/ds4424.txt
+++ /dev/null
@@ -1,20 +0,0 @@
-Maxim Integrated DS4422/DS4424 7-bit Sink/Source Current DAC Device Driver
-
-Datasheet publicly available at:
-https://datasheets.maximintegrated.com/en/ds/DS4422-DS4424.pdf
-
-Required properties:
- - compatible: Should be one of
- maxim,ds4422
- maxim,ds4424
- - reg: Should contain the DAC I2C address
-
-Optional properties:
- - vcc-supply: Power supply is optional. If not defined, driver will ignore it.
-
-Example:
- ds4224@10 {
- compatible = "maxim,ds4424";
- reg = <0x10>; /* When A0, A1 pins are ground */
- vcc-supply = <&vcc_3v3>;
- };
diff --git a/Documentation/devicetree/bindings/iio/dac/maxim,ds4424.yaml b/Documentation/devicetree/bindings/iio/dac/maxim,ds4424.yaml
new file mode 100644
index 000000000000..264fa7c5fe3a
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/maxim,ds4424.yaml
@@ -0,0 +1,45 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/dac/maxim,ds4424.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Maxim Integrated DS4422/DS4424 7-bit Sink/Source Current DAC
+
+maintainers:
+ - Ismail Kose <ihkose@gmail.com>
+
+description: |
+ Datasheet publicly available at:
+ https://datasheets.maximintegrated.com/en/ds/DS4422-DS4424.pdf
+
+properties:
+ compatible:
+ enum:
+ - maxim,ds4422
+ - maxim,ds4424
+
+ reg:
+ maxItems: 1
+
+ vcc-supply: true
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ dac@10 {
+ compatible = "maxim,ds4424";
+ reg = <0x10>; /* When A0, A1 pins are ground */
+ vcc-supply = <&vcc_3v3>;
+ };
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 19/29] dt-bindings:iio:dac:fsl,vf610-dac yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (17 preceding siblings ...)
2020-10-31 13:40 ` [PATCH v2 18/29] dt-bindings:iio:dac:maxim,ds4424 " Jonathan Cameron
@ 2020-10-31 13:41 ` Jonathan Cameron
2020-10-31 13:41 ` [PATCH v2 20/29] dt-bindings:iio:dac:microchip,mcp4725 " Jonathan Cameron
` (10 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:41 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Sanchayan Maity
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Simple binding to convert. Example expanded a little to include
an example bus.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Cc: Sanchayan Maity <maitysanchayan@gmail.com>
---
.../bindings/iio/dac/fsl,vf610-dac.yaml | 55 +++++++++++++++++++
.../devicetree/bindings/iio/dac/vf610-dac.txt | 20 -------
2 files changed, 55 insertions(+), 20 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/dac/fsl,vf610-dac.yaml b/Documentation/devicetree/bindings/iio/dac/fsl,vf610-dac.yaml
new file mode 100644
index 000000000000..999c715c6179
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/fsl,vf610-dac.yaml
@@ -0,0 +1,55 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/dac/fsl,vf610-dac.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Freescale vf610 Digital to Analog Converter
+
+maintainers:
+ - Sanchayan Maity <maitysanchayan@gmail.com>
+
+properties:
+ compatible:
+ const: fsl,vf610-dac
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+ clocks:
+ maxItems: 1
+
+ clock-names:
+ const: dac
+
+required:
+ - compatible
+ - reg
+ - interrupts
+ - clocks
+ - clock-names
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+ #include <dt-bindings/clock/vf610-clock.h>
+ bus@40000000 {
+ compatible = "fsl,aips-bus", "simple-bus";
+ reg = <0x40000000 0x00070000>;
+ ranges;
+ #address-cells = <1>;
+ #size-cells = <1>;
+ dac@400cc000 {
+ compatible = "fsl,vf610-dac";
+ reg = <0x400cc000 0x1000>;
+ interrupts = <55 IRQ_TYPE_LEVEL_HIGH>;
+ clock-names = "dac";
+ clocks = <&clks VF610_CLK_DAC0>;
+ };
+ };
+...
diff --git a/Documentation/devicetree/bindings/iio/dac/vf610-dac.txt b/Documentation/devicetree/bindings/iio/dac/vf610-dac.txt
deleted file mode 100644
index 20c6c7ae9687..000000000000
--- a/Documentation/devicetree/bindings/iio/dac/vf610-dac.txt
+++ /dev/null
@@ -1,20 +0,0 @@
-Freescale vf610 Digital to Analog Converter bindings
-
-The devicetree bindings are for the new DAC driver written for
-vf610 SoCs from Freescale.
-
-Required properties:
-- compatible: Should contain "fsl,vf610-dac"
-- reg: Offset and length of the register set for the device
-- interrupts: Should contain the interrupt for the device
-- clocks: The clock is needed by the DAC controller
-- clock-names: Must contain "dac" matching entry in the clocks property.
-
-Example:
-dac0: dac@400cc000 {
- compatible = "fsl,vf610-dac";
- reg = <0x400cc000 0x1000>;
- interrupts = <55 IRQ_TYPE_LEVEL_HIGH>;
- clock-names = "dac";
- clocks = <&clks VF610_CLK_DAC0>;
-};
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 20/29] dt-bindings:iio:dac:microchip,mcp4725 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (18 preceding siblings ...)
2020-10-31 13:41 ` [PATCH v2 19/29] dt-bindings:iio:dac:fsl,vf610-dac " Jonathan Cameron
@ 2020-10-31 13:41 ` Jonathan Cameron
2020-10-31 13:41 ` [PATCH v2 21/29] dt-bindings:iio:dac:maxim,max5821 " Jonathan Cameron
` (9 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:41 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Tomas Novotny
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
I'm not sure vdd-supply absolutely has to be provided if vref-supply
is, but as the previous binding docs stated it was required it seems
reasonable to leave it as such.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Cc: Tomas Novotny <tomas@novotny.cz>
---
.../devicetree/bindings/iio/dac/mcp4725.txt | 35 ---------
.../bindings/iio/dac/microchip,mcp4725.yaml | 71 +++++++++++++++++++
2 files changed, 71 insertions(+), 35 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/dac/mcp4725.txt b/Documentation/devicetree/bindings/iio/dac/mcp4725.txt
deleted file mode 100644
index 1bc6c093fbfe..000000000000
--- a/Documentation/devicetree/bindings/iio/dac/mcp4725.txt
+++ /dev/null
@@ -1,35 +0,0 @@
-Microchip mcp4725 and mcp4726 DAC device driver
-
-Required properties:
- - compatible: Must be "microchip,mcp4725" or "microchip,mcp4726"
- - reg: Should contain the DAC I2C address
- - vdd-supply: Phandle to the Vdd power supply. This supply is used as a
- voltage reference on mcp4725. It is used as a voltage reference on
- mcp4726 if there is no vref-supply specified.
-
-Optional properties (valid only for mcp4726):
- - vref-supply: Optional phandle to the Vref power supply. Vref pin is
- used as a voltage reference when this supply is specified.
- - microchip,vref-buffered: Boolean to enable buffering of the external
- Vref pin. This boolean is not valid without the vref-supply. Quoting
- the datasheet: This is offered in cases where the reference voltage
- does not have the current capability not to drop its voltage when
- connected to the internal resistor ladder circuit.
-
-Examples:
-
- /* simple mcp4725 */
- mcp4725@60 {
- compatible = "microchip,mcp4725";
- reg = <0x60>;
- vdd-supply = <&vdac_vdd>;
- };
-
- /* mcp4726 with the buffered external reference voltage */
- mcp4726@60 {
- compatible = "microchip,mcp4726";
- reg = <0x60>;
- vdd-supply = <&vdac_vdd>;
- vref-supply = <&vdac_vref>;
- microchip,vref-buffered;
- };
diff --git a/Documentation/devicetree/bindings/iio/dac/microchip,mcp4725.yaml b/Documentation/devicetree/bindings/iio/dac/microchip,mcp4725.yaml
new file mode 100644
index 000000000000..271998610ceb
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/microchip,mcp4725.yaml
@@ -0,0 +1,71 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/dac/microchip,mcp4725.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Microchip mcp4725 and mcp4726 DAC
+
+maintainers:
+ - Tomas Novotny <tomas@novotny.cz>
+
+properties:
+ compatible:
+ enum:
+ - microchip,mcp4725
+ - microchip,mcp4726
+
+ reg:
+ maxItems: 1
+
+ vdd-supply:
+ description: |
+ Provides both power and acts as the reference supply on the mcp4725.
+ For the mcp4726 it will be used as the reference voltage if vref-supply
+ is not provided.
+
+ vref-supply:
+ description:
+ Vref pin is used as a voltage reference when this supply is specified.
+
+ microchip,vref-buffered:
+ type: boolean
+ description: |
+ Enable buffering of the external Vref pin. This boolean is not valid
+ without the vref-supply. Quoting the datasheet: This is offered in
+ cases where the reference voltage does not have the current
+ capability not to drop its voltage when connected to the internal
+ resistor ladder circuit.
+
+allOf:
+ - if:
+ not:
+ properties:
+ compatible:
+ contains:
+ const: microchip,mcp4726
+ then:
+ properties:
+ vref-supply: false
+ microchip,vref-buffered: false
+
+required:
+ - compatible
+ - reg
+ - vdd-supply
+
+additionalProperties: false
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ mcp4725@60 {
+ compatible = "microchip,mcp4725";
+ reg = <0x60>;
+ vdd-supply = <&vdac_vdd>;
+ };
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 21/29] dt-bindings:iio:dac:maxim,max5821 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (19 preceding siblings ...)
2020-10-31 13:41 ` [PATCH v2 20/29] dt-bindings:iio:dac:microchip,mcp4725 " Jonathan Cameron
@ 2020-10-31 13:41 ` Jonathan Cameron
2020-10-31 13:41 ` [PATCH v2 22/29] dt-bindings:iio:dac:nxp,lpc1850-dac " Jonathan Cameron
` (8 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:41 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Philippe Reynes
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Simple txt to yaml conversion for this binding description.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Cc: Philippe Reynes <tremyfr@yahoo.fr>
---
.../devicetree/bindings/iio/dac/max5821.txt | 14 ------
.../bindings/iio/dac/maxim,max5821.yaml | 44 +++++++++++++++++++
2 files changed, 44 insertions(+), 14 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/dac/max5821.txt b/Documentation/devicetree/bindings/iio/dac/max5821.txt
deleted file mode 100644
index 54276ce8c971..000000000000
--- a/Documentation/devicetree/bindings/iio/dac/max5821.txt
+++ /dev/null
@@ -1,14 +0,0 @@
-Maxim max5821 DAC device driver
-
-Required properties:
- - compatible: Must be "maxim,max5821"
- - reg: Should contain the DAC I2C address
- - vref-supply: Phandle to the vref power supply
-
-Example:
-
- max5821@38 {
- compatible = "maxim,max5821";
- reg = <0x38>;
- vref-supply = <®_max5821>;
- };
diff --git a/Documentation/devicetree/bindings/iio/dac/maxim,max5821.yaml b/Documentation/devicetree/bindings/iio/dac/maxim,max5821.yaml
new file mode 100644
index 000000000000..c43fb5f3f8ac
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/maxim,max5821.yaml
@@ -0,0 +1,44 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/dac/maxim,max5821.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Maxim max5821 dual 10-bit DAC
+
+maintainers:
+ - Philippe Reynes <tremyfr@yahoo.fr>
+
+description: |
+ Datasheet publicly available at:
+ https://datasheets.maximintegrated.com/en/ds/MAX5821.pdf
+
+properties:
+ compatible:
+ const: maxim,max5821
+
+ reg:
+ maxItems: 1
+
+ vref-supply: true
+
+required:
+ - compatible
+ - reg
+ - vref-supply
+
+additionalProperties: false
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ dac@38 {
+ compatible = "maxim,max5821";
+ reg = <0x38>;
+ vref-supply = <®_max5821>;
+ };
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 22/29] dt-bindings:iio:dac:nxp,lpc1850-dac yaml conversion.
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (20 preceding siblings ...)
2020-10-31 13:41 ` [PATCH v2 21/29] dt-bindings:iio:dac:maxim,max5821 " Jonathan Cameron
@ 2020-10-31 13:41 ` Jonathan Cameron
2020-10-31 13:41 ` [PATCH v2 23/29] dt-bindings:iio:dac:adi,ad5758 " Jonathan Cameron
` (7 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:41 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Vladimir Zapolskiy
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Very similar binding to that for the ADC on the same device.
Conversion from txt to yaml format.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Acked-by: Vladimir Zapolskiy <vz@mleia.com>
---
.../bindings/iio/dac/lpc1850-dac.txt | 19 ------
.../bindings/iio/dac/nxp,lpc1850-dac.yaml | 58 +++++++++++++++++++
2 files changed, 58 insertions(+), 19 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/dac/lpc1850-dac.txt b/Documentation/devicetree/bindings/iio/dac/lpc1850-dac.txt
deleted file mode 100644
index 42db783c4e75..000000000000
--- a/Documentation/devicetree/bindings/iio/dac/lpc1850-dac.txt
+++ /dev/null
@@ -1,19 +0,0 @@
-NXP LPC1850 DAC bindings
-
-Required properties:
-- compatible: Should be "nxp,lpc1850-dac"
-- reg: Offset and length of the register set for the ADC device
-- interrupts: The interrupt number for the ADC device
-- clocks: The root clock of the ADC controller
-- vref-supply: The regulator supply ADC reference voltage
-- resets: phandle to reset controller and line specifier
-
-Example:
-dac: dac@400e1000 {
- compatible = "nxp,lpc1850-dac";
- reg = <0x400e1000 0x1000>;
- interrupts = <0>;
- clocks = <&ccu1 CLK_APB3_DAC>;
- vref-supply = <®_vdda>;
- resets = <&rgu 42>;
-};
diff --git a/Documentation/devicetree/bindings/iio/dac/nxp,lpc1850-dac.yaml b/Documentation/devicetree/bindings/iio/dac/nxp,lpc1850-dac.yaml
new file mode 100644
index 000000000000..595f481c548e
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/nxp,lpc1850-dac.yaml
@@ -0,0 +1,58 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/dac/nxp,lpc1850-dac.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: NXP LPC1850 DAC bindings
+
+maintainers:
+ - Jonathan Cameron <jic23@kernel.org>
+
+description:
+ Supports the DAC found on the LPC1850 SoC.
+
+properties:
+ compatible:
+ const: nxp,lpc1850-dac
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+ clocks:
+ maxItems: 1
+
+ vref-supply: true
+
+ resets:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+ - interrupts
+ - clocks
+ - vref-supply
+ - resets
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/clock/lpc18xx-ccu.h>
+ soc {
+ #address-cells = <1>;
+ #size-cells = <1>;
+ dac: dac@400e1000 {
+ compatible = "nxp,lpc1850-dac";
+ reg = <0x400e1000 0x1000>;
+ interrupts = <0>;
+ clocks = <&ccu1 CLK_APB3_DAC>;
+ vref-supply = <®_vdda>;
+ resets = <&rgu 42>;
+ };
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 23/29] dt-bindings:iio:dac:adi,ad5758 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (21 preceding siblings ...)
2020-10-31 13:41 ` [PATCH v2 22/29] dt-bindings:iio:dac:nxp,lpc1850-dac " Jonathan Cameron
@ 2020-10-31 13:41 ` Jonathan Cameron
2020-10-31 13:41 ` [PATCH v2 24/29] dt-bindings:iio:temperature:melexis,mlx90614 " Jonathan Cameron
` (6 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:41 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Michael Hennerich
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
I have put Michael as maintainer on this one. Happy to change it to
someone else though.
One issue in here, is I cannot have an example with a negative
limit on the range. There are very few such yaml bindings in existence
but the thermal-zones.yaml has the same problem. If there is
any means of fixing this let me know. For now I'm sticking to
positive range values in the example.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Cc: Michael Hennerich <Michael.Hennerich@analog.com>
---
.../devicetree/bindings/iio/dac/ad5758.txt | 83 -----------
.../bindings/iio/dac/adi,ad5758.yaml | 129 ++++++++++++++++++
2 files changed, 129 insertions(+), 83 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/dac/ad5758.txt b/Documentation/devicetree/bindings/iio/dac/ad5758.txt
deleted file mode 100644
index 2f607f41f9d3..000000000000
--- a/Documentation/devicetree/bindings/iio/dac/ad5758.txt
+++ /dev/null
@@ -1,83 +0,0 @@
-Analog Devices AD5758 DAC device driver
-
-Required properties for the AD5758:
- - compatible: Must be "adi,ad5758"
- - reg: SPI chip select number for the device
- - spi-max-frequency: Max SPI frequency to use (< 50000000)
- - spi-cpha: is the only mode that is supported
-
-Required properties:
-
- - adi,dc-dc-mode: Mode of operation of the dc-to-dc converter
- Dynamic Power Control (DPC)
- In this mode, the AD5758 circuitry senses the output
- voltage and dynamically regulates the supply voltage,
- VDPC+, to meet compliance requirements plus an optimized
- headroom voltage for the output buffer.
-
- Programmable Power Control (PPC)
- In this mode, the VDPC+ voltage is user-programmable to
- a fixed level that needs to accommodate the maximum output
- load required.
-
- The output of the DAC core is either converted to a
- current or voltage output at the VIOUT pin. Only one mode
- can be enabled at any one time.
-
- The following values are currently supported:
- * 1: DPC current mode
- * 2: DPC voltage mode
- * 3: PPC current mode
-
- Depending on the selected output mode (voltage or current) one of the
- two properties must
- be present:
-
- - adi,range-microvolt: Voltage output range
- The array of voltage output ranges must contain two fields:
- * <0 5000000>: 0 V to 5 V voltage range
- * <0 10000000>: 0 V to 10 V voltage range
- * <(-5000000) 5000000>: ±5 V voltage range
- * <(-10000000) 10000000>: ±10 V voltage range
- - adi,range-microamp: Current output range
- The array of current output ranges must contain two fields:
- * <0 20000>: 0 mA to 20 mA current range
- * <0 24000>: 0 mA to 24 mA current range
- * <4 24000>: 4 mA to 20 mA current range
- * <(-20000) 20000>: ±20 mA current range
- * <(-24000) 24000>: ±24 mA current range
- * <(-1000) 22000>: −1 mA to +22 mA current range
-
-Optional properties:
-
- - reset-gpios : GPIO spec for the RESET pin. If specified, it will be
- asserted during driver probe.
-
- - adi,dc-dc-ilim-microamp: The dc-to-dc converter current limit
- The following values are currently supported [uA]:
- * 150000
- * 200000
- * 250000
- * 300000
- * 350000
- * 400000
-
- - adi,slew-time-us: The time it takes for the output to reach the
- full scale [uS]
- The supported range is between 133us up to 1023984375us
-
-AD5758 Example:
-
- dac@0 {
- compatible = "adi,ad5758";
- reg = <0>;
- spi-max-frequency = <1000000>;
- spi-cpha;
-
- reset-gpios = <&gpio 22 0>;
-
- adi,dc-dc-mode = <2>;
- adi,range-microvolt = <0 10000000>;
- adi,dc-dc-ilim-microamp = <200000>;
- adi,slew-time-us = <125000>;
- };
diff --git a/Documentation/devicetree/bindings/iio/dac/adi,ad5758.yaml b/Documentation/devicetree/bindings/iio/dac/adi,ad5758.yaml
new file mode 100644
index 000000000000..626ccb6fe21e
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/dac/adi,ad5758.yaml
@@ -0,0 +1,129 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/dac/adi,ad5758.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Analog Devices AD5758 DAC
+
+maintainers:
+ - Michael Hennerich <Michael.Hennerich@analog.com>
+
+properties:
+ compatible:
+ const: adi,ad5758
+
+ reg:
+ maxItems: 1
+
+ spi-max-frequency: true
+ spi-cpha: true
+
+ adi,dc-dc-mode:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ enum: [1, 2, 3]
+ description: |
+ Mode of operation of the dc-to-dc converter
+ Dynamic Power Control (DPC)
+ In this mode, the AD5758 circuitry senses the output voltage and
+ dynamically regulates the supply voltage, VDPC+, to meet compliance
+ requirements plus an optimized headroom voltage for the output buffer.
+
+ Programmable Power Control (PPC)
+ In this mode, the VDPC+ voltage is user-programmable to a fixed level
+ that needs to accommodate the maximum output load required.
+
+ The output of the DAC core is either converted to a current or
+ voltage output at the VIOUT pin. Only one mode can be enabled at
+ any one time.
+
+ The following values are currently supported:
+ * 1: DPC current mode
+ * 2: DPC voltage mode
+ * 3: PPC current mode
+
+ Depending on the selected output mode (voltage or current) one of the
+ two properties must be present:
+
+ adi,range-microvolt:
+ $ref: /schemas/types.yaml#/definitions/int32-array
+ description: |
+ Voltage output range specified as <minimum, maximum>
+ enum:
+ - [[0, 5000000]]
+ - [[0, 10000000]]
+ - [[-5000000, 5000000]]
+ - [[-10000000, 10000000]]
+
+ adi,range-microamp:
+ $ref: /schemas/types.yaml#/definitions/int32-array
+ description: |
+ Current output range specified as <minimum, maximum>
+ enum:
+ - [[0, 20000]]
+ - [[0, 24000]]
+ - [[4, 24000]]
+ - [[-20000, 20000]]
+ - [[-24000, 24000]]
+ - [[-1000, 22000]]
+
+ reset-gpios: true
+
+ adi,dc-dc-ilim-microamp:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ enum: [150000, 200000, 250000, 300000, 350000, 400000]
+ description: |
+ The dc-to-dc converter current limit.
+
+ adi,slew-time-us:
+ description: |
+ The time it takes for the output to reach the full scale [uS]
+ minimum: 133
+ maximum: 1023984375
+
+required:
+ - compatible
+ - reg
+ - spi-cpha
+ - adi,dc-dc-mode
+
+allOf:
+ - if:
+ properties:
+ adi,dc-dc-mode:
+ contains:
+ enum: [1, 3]
+ then:
+ properties:
+ adi,range-microvolt: false
+ required:
+ - adi,range-microamp
+ else:
+ properties:
+ adi,range-microamp: false
+ required:
+ - adi,range-microvolt
+
+additionalProperties: false
+
+examples:
+ - |
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ dac@0 {
+ compatible = "adi,ad5758";
+ reg = <0>;
+ spi-max-frequency = <1000000>;
+ spi-cpha;
+
+ reset-gpios = <&gpio 22 0>;
+
+ adi,dc-dc-mode = <2>;
+ adi,range-microvolt = <0 10000000>;
+ adi,dc-dc-ilim-microamp = <200000>;
+ adi,slew-time-us = <125000>;
+ };
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 24/29] dt-bindings:iio:temperature:melexis,mlx90614 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (22 preceding siblings ...)
2020-10-31 13:41 ` [PATCH v2 23/29] dt-bindings:iio:dac:adi,ad5758 " Jonathan Cameron
@ 2020-10-31 13:41 ` Jonathan Cameron
2020-11-02 9:12 ` Crt Mori
2020-10-31 13:41 ` [PATCH v2 25/29] dt-bindings:iio:temperature:melexis,mlx90632 conversion to yaml Jonathan Cameron
` (5 subsequent siblings)
29 siblings, 1 reply; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:41 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Crt Mori, Peter Meerwald
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Simple conversion from txt to yaml.
I've listed all 3 authors of the driver as maintainers.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Acked-by: Crt Mori <cmo@melexis.com>
Cc: Peter Meerwald <pmeerw@pmeerw.net>
---
.../iio/temperature/melexis,mlx90614.yaml | 50 +++++++++++++++++++
.../bindings/iio/temperature/mlx90614.txt | 24 ---------
2 files changed, 50 insertions(+), 24 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/temperature/melexis,mlx90614.yaml b/Documentation/devicetree/bindings/iio/temperature/melexis,mlx90614.yaml
new file mode 100644
index 000000000000..d6965a0c1cf3
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/temperature/melexis,mlx90614.yaml
@@ -0,0 +1,50 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/temperature/melexis,mlx90614.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Melexis MLX90614 contactless IR temperature sensor
+
+maintainers:
+ - Peter Meerwald <pmeerw@pmeerw.net>
+ - Crt Mori <cmo@melexis.com>
+
+description: |
+ http://melexis.com/Infrared-Thermometer-Sensors/Infrared-Thermometer-Sensors/MLX90614-615.aspx
+
+properties:
+ compatible:
+ const: melexis,mlx90614
+
+ reg:
+ maxItems: 1
+
+ wakeup-gpios:
+ description:
+ GPIO connected to the SDA line to hold low in order to wake up the
+ device. In normal operation, the GPIO is set as input and will
+ not interfere in I2C communication. There is no need for a GPIO
+ driving the SCL line. If no GPIO is given, power management is disabled.
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ temp-sensor@5a {
+ compatible = "melexis,mlx90614";
+ reg = <0x5a>;
+ wakeup-gpios = <&gpio0 2 GPIO_ACTIVE_HIGH>;
+ };
+ };
+...
diff --git a/Documentation/devicetree/bindings/iio/temperature/mlx90614.txt b/Documentation/devicetree/bindings/iio/temperature/mlx90614.txt
deleted file mode 100644
index 9be57b036092..000000000000
--- a/Documentation/devicetree/bindings/iio/temperature/mlx90614.txt
+++ /dev/null
@@ -1,24 +0,0 @@
-* Melexis MLX90614 contactless IR temperature sensor
-
-http://melexis.com/Infrared-Thermometer-Sensors/Infrared-Thermometer-Sensors/MLX90614-615.aspx
-
-Required properties:
-
- - compatible: should be "melexis,mlx90614"
- - reg: the I2C address of the sensor
-
-Optional properties:
-
- - wakeup-gpios: device tree identifier of the GPIO connected to the SDA line
- to hold low in order to wake up the device. In normal operation, the
- GPIO is set as input and will not interfere in I2C communication. There
- is no need for a GPIO driving the SCL line. If no GPIO is given, power
- management is disabled.
-
-Example:
-
-mlx90614@5a {
- compatible = "melexis,mlx90614";
- reg = <0x5a>;
- wakeup-gpios = <&gpio0 2 GPIO_ACTIVE_HIGH>;
-};
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* Re: [PATCH v2 24/29] dt-bindings:iio:temperature:melexis,mlx90614 yaml conversion
2020-10-31 13:41 ` [PATCH v2 24/29] dt-bindings:iio:temperature:melexis,mlx90614 " Jonathan Cameron
@ 2020-11-02 9:12 ` Crt Mori
2020-11-02 17:39 ` Jonathan Cameron
0 siblings, 1 reply; 40+ messages in thread
From: Crt Mori @ 2020-11-02 9:12 UTC (permalink / raw)
To: Jonathan Cameron
Cc: Linux Iio, Rob Herring, devicetree, Jonathan Cameron,
Rob Herring, Peter Meerwald
Hi Jonathan,
The commit message should change here as now you did not list all 3
authors as maintainers, because one has a bouncy email address.
Best regards,
Crt
On Sat, 31 Oct 2020 at 14:44, Jonathan Cameron <jic23@kernel.org> wrote:
>
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> Simple conversion from txt to yaml.
> I've listed all 3 authors of the driver as maintainers.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Acked-by: Crt Mori <cmo@melexis.com>
> Cc: Peter Meerwald <pmeerw@pmeerw.net>
> ---
> .../iio/temperature/melexis,mlx90614.yaml | 50 +++++++++++++++++++
> .../bindings/iio/temperature/mlx90614.txt | 24 ---------
> 2 files changed, 50 insertions(+), 24 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/iio/temperature/melexis,mlx90614.yaml b/Documentation/devicetree/bindings/iio/temperature/melexis,mlx90614.yaml
> new file mode 100644
> index 000000000000..d6965a0c1cf3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/temperature/melexis,mlx90614.yaml
> @@ -0,0 +1,50 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/temperature/melexis,mlx90614.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Melexis MLX90614 contactless IR temperature sensor
> +
> +maintainers:
> + - Peter Meerwald <pmeerw@pmeerw.net>
> + - Crt Mori <cmo@melexis.com>
> +
> +description: |
> + http://melexis.com/Infrared-Thermometer-Sensors/Infrared-Thermometer-Sensors/MLX90614-615.aspx
> +
> +properties:
> + compatible:
> + const: melexis,mlx90614
> +
> + reg:
> + maxItems: 1
> +
> + wakeup-gpios:
> + description:
> + GPIO connected to the SDA line to hold low in order to wake up the
> + device. In normal operation, the GPIO is set as input and will
> + not interfere in I2C communication. There is no need for a GPIO
> + driving the SCL line. If no GPIO is given, power management is disabled.
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + temp-sensor@5a {
> + compatible = "melexis,mlx90614";
> + reg = <0x5a>;
> + wakeup-gpios = <&gpio0 2 GPIO_ACTIVE_HIGH>;
> + };
> + };
> +...
> diff --git a/Documentation/devicetree/bindings/iio/temperature/mlx90614.txt b/Documentation/devicetree/bindings/iio/temperature/mlx90614.txt
> deleted file mode 100644
> index 9be57b036092..000000000000
> --- a/Documentation/devicetree/bindings/iio/temperature/mlx90614.txt
> +++ /dev/null
> @@ -1,24 +0,0 @@
> -* Melexis MLX90614 contactless IR temperature sensor
> -
> -http://melexis.com/Infrared-Thermometer-Sensors/Infrared-Thermometer-Sensors/MLX90614-615.aspx
> -
> -Required properties:
> -
> - - compatible: should be "melexis,mlx90614"
> - - reg: the I2C address of the sensor
> -
> -Optional properties:
> -
> - - wakeup-gpios: device tree identifier of the GPIO connected to the SDA line
> - to hold low in order to wake up the device. In normal operation, the
> - GPIO is set as input and will not interfere in I2C communication. There
> - is no need for a GPIO driving the SCL line. If no GPIO is given, power
> - management is disabled.
> -
> -Example:
> -
> -mlx90614@5a {
> - compatible = "melexis,mlx90614";
> - reg = <0x5a>;
> - wakeup-gpios = <&gpio0 2 GPIO_ACTIVE_HIGH>;
> -};
> --
> 2.28.0
>
^ permalink raw reply [flat|nested] 40+ messages in thread* Re: [PATCH v2 24/29] dt-bindings:iio:temperature:melexis,mlx90614 yaml conversion
2020-11-02 9:12 ` Crt Mori
@ 2020-11-02 17:39 ` Jonathan Cameron
0 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-11-02 17:39 UTC (permalink / raw)
To: Crt Mori
Cc: Jonathan Cameron, Linux Iio, Rob Herring, devicetree,
Rob Herring, Peter Meerwald
On Mon, 2 Nov 2020 10:12:57 +0100
Crt Mori <cmo@melexis.com> wrote:
> Hi Jonathan,
> The commit message should change here as now you did not list all 3
> authors as maintainers, because one has a bouncy email address.
Good point. I can clean that up whilst applying if we don't need
a v3.
Jonathan
>
> Best regards,
> Crt
>
> On Sat, 31 Oct 2020 at 14:44, Jonathan Cameron <jic23@kernel.org> wrote:
> >
> > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> >
> > Simple conversion from txt to yaml.
> > I've listed all 3 authors of the driver as maintainers.
> >
> > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > Reviewed-by: Rob Herring <robh@kernel.org>
> > Acked-by: Crt Mori <cmo@melexis.com>
> > Cc: Peter Meerwald <pmeerw@pmeerw.net>
> > ---
> > .../iio/temperature/melexis,mlx90614.yaml | 50 +++++++++++++++++++
> > .../bindings/iio/temperature/mlx90614.txt | 24 ---------
> > 2 files changed, 50 insertions(+), 24 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/iio/temperature/melexis,mlx90614.yaml b/Documentation/devicetree/bindings/iio/temperature/melexis,mlx90614.yaml
> > new file mode 100644
> > index 000000000000..d6965a0c1cf3
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/temperature/melexis,mlx90614.yaml
> > @@ -0,0 +1,50 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/iio/temperature/melexis,mlx90614.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Melexis MLX90614 contactless IR temperature sensor
> > +
> > +maintainers:
> > + - Peter Meerwald <pmeerw@pmeerw.net>
> > + - Crt Mori <cmo@melexis.com>
> > +
> > +description: |
> > + http://melexis.com/Infrared-Thermometer-Sensors/Infrared-Thermometer-Sensors/MLX90614-615.aspx
> > +
> > +properties:
> > + compatible:
> > + const: melexis,mlx90614
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + wakeup-gpios:
> > + description:
> > + GPIO connected to the SDA line to hold low in order to wake up the
> > + device. In normal operation, the GPIO is set as input and will
> > + not interfere in I2C communication. There is no need for a GPIO
> > + driving the SCL line. If no GPIO is given, power management is disabled.
> > + maxItems: 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/gpio/gpio.h>
> > + i2c {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + temp-sensor@5a {
> > + compatible = "melexis,mlx90614";
> > + reg = <0x5a>;
> > + wakeup-gpios = <&gpio0 2 GPIO_ACTIVE_HIGH>;
> > + };
> > + };
> > +...
> > diff --git a/Documentation/devicetree/bindings/iio/temperature/mlx90614.txt b/Documentation/devicetree/bindings/iio/temperature/mlx90614.txt
> > deleted file mode 100644
> > index 9be57b036092..000000000000
> > --- a/Documentation/devicetree/bindings/iio/temperature/mlx90614.txt
> > +++ /dev/null
> > @@ -1,24 +0,0 @@
> > -* Melexis MLX90614 contactless IR temperature sensor
> > -
> > -http://melexis.com/Infrared-Thermometer-Sensors/Infrared-Thermometer-Sensors/MLX90614-615.aspx
> > -
> > -Required properties:
> > -
> > - - compatible: should be "melexis,mlx90614"
> > - - reg: the I2C address of the sensor
> > -
> > -Optional properties:
> > -
> > - - wakeup-gpios: device tree identifier of the GPIO connected to the SDA line
> > - to hold low in order to wake up the device. In normal operation, the
> > - GPIO is set as input and will not interfere in I2C communication. There
> > - is no need for a GPIO driving the SCL line. If no GPIO is given, power
> > - management is disabled.
> > -
> > -Example:
> > -
> > -mlx90614@5a {
> > - compatible = "melexis,mlx90614";
> > - reg = <0x5a>;
> > - wakeup-gpios = <&gpio0 2 GPIO_ACTIVE_HIGH>;
> > -};
> > --
> > 2.28.0
> >
^ permalink raw reply [flat|nested] 40+ messages in thread
* [PATCH v2 25/29] dt-bindings:iio:temperature:melexis,mlx90632 conversion to yaml
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (23 preceding siblings ...)
2020-10-31 13:41 ` [PATCH v2 24/29] dt-bindings:iio:temperature:melexis,mlx90614 " Jonathan Cameron
@ 2020-10-31 13:41 ` Jonathan Cameron
2020-10-31 13:41 ` [PATCH v2 26/29] dt-bindings:iio:temperature:meas,tsys01 move to trivial-devices.yaml Jonathan Cameron
` (4 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:41 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Crt Mori
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Technically this could have gone in trivial-devices.yaml, but I have
kept it as a separate binding due to the detailed additional description
from the text file.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Acked-by: Crt Mori <cmo@melexis.com>
Cc: Crt Mori <cmo@melexis.com>
---
.../iio/temperature/melexis,mlx90632.yaml | 55 +++++++++++++++++++
.../bindings/iio/temperature/mlx90632.txt | 28 ----------
2 files changed, 55 insertions(+), 28 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/temperature/melexis,mlx90632.yaml b/Documentation/devicetree/bindings/iio/temperature/melexis,mlx90632.yaml
new file mode 100644
index 000000000000..b547ddcd544a
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/temperature/melexis,mlx90632.yaml
@@ -0,0 +1,55 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/temperature/melexis,mlx90632.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Melexis MLX90632 contactless Infra Red temperature sensor
+
+maintainers:
+ - Crt Mori <cmo@melexis.com>
+
+description: |
+ https://www.melexis.com/en/documents/documentation/datasheets/datasheet-mlx90632
+
+ There are various applications for the Infra Red contactless temperature
+ sensor and MLX90632 is most suitable for consumer applications where
+ measured object temperature is in range between -20 to 200 degrees
+ Celsius with relative error of measurement below 1 degree Celsius in
+ object temperature range for industrial applications. Since it can
+ operate and measure ambient temperature in range of -20 to 85 degrees
+ Celsius it is suitable also for outdoor use.
+
+ Be aware that electronics surrounding the sensor can increase ambient
+ temperature. MLX90632 can be calibrated to reduce the housing effect via
+ already existing EEPROM parameters.
+
+ Since measured object emissivity effects Infra Red energy emitted,
+ emissivity should be set before requesting the object temperature.
+
+properties:
+ compatible:
+ const: melexis,mlx90632
+
+ reg:
+ maxItems: 1
+ description: Default is 0x3a, but can be reprogrammed.
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ temp-sensor@3a {
+ compatible = "melexis,mlx90632";
+ reg = <0x3a>;
+ };
+ };
+...
diff --git a/Documentation/devicetree/bindings/iio/temperature/mlx90632.txt b/Documentation/devicetree/bindings/iio/temperature/mlx90632.txt
deleted file mode 100644
index 0b05812001f8..000000000000
--- a/Documentation/devicetree/bindings/iio/temperature/mlx90632.txt
+++ /dev/null
@@ -1,28 +0,0 @@
-* Melexis MLX90632 contactless Infra Red temperature sensor
-
-Link to datasheet: https://www.melexis.com/en/documents/documentation/datasheets/datasheet-mlx90632
-
-There are various applications for the Infra Red contactless temperature sensor
-and MLX90632 is most suitable for consumer applications where measured object
-temperature is in range between -20 to 200 degrees Celsius with relative error
-of measurement below 1 degree Celsius in object temperature range for
-industrial applications. Since it can operate and measure ambient temperature
-in range of -20 to 85 degrees Celsius it is suitable also for outdoor use.
-
-Be aware that electronics surrounding the sensor can increase ambient
-temperature. MLX90632 can be calibrated to reduce the housing effect via
-already existing EEPROM parameters.
-
-Since measured object emissivity effects Infra Red energy emitted, emissivity
-should be set before requesting the object temperature.
-
-Required properties:
- - compatible: should be "melexis,mlx90632"
- - reg: the I2C address of the sensor (default 0x3a)
-
-Example:
-
-mlx90632@3a {
- compatible = "melexis,mlx90632";
- reg = <0x3a>;
-};
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 26/29] dt-bindings:iio:temperature:meas,tsys01 move to trivial-devices.yaml
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (24 preceding siblings ...)
2020-10-31 13:41 ` [PATCH v2 25/29] dt-bindings:iio:temperature:melexis,mlx90632 conversion to yaml Jonathan Cameron
@ 2020-10-31 13:41 ` Jonathan Cameron
2020-11-01 15:25 ` Manivannan Sadhasivam
2020-10-31 13:41 ` [PATCH v2 27/29] dt-bindings:iio:temperature:maxim,max31856 yaml conversion Jonathan Cameron
` (3 subsequent siblings)
29 siblings, 1 reply; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:41 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Manivannan Sadhasivam
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
The existing binding description brings little value and the similar
meas,* parts are in trivial-devices.yaml so move this one there
to join them.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
---
.../bindings/iio/temperature/tsys01.txt | 19 -------------------
.../devicetree/bindings/trivial-devices.yaml | 2 ++
2 files changed, 2 insertions(+), 19 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/temperature/tsys01.txt b/Documentation/devicetree/bindings/iio/temperature/tsys01.txt
deleted file mode 100644
index 0d5cc5595d0c..000000000000
--- a/Documentation/devicetree/bindings/iio/temperature/tsys01.txt
+++ /dev/null
@@ -1,19 +0,0 @@
-* TSYS01 - Measurement Specialties temperature sensor
-
-Required properties:
-
- - compatible: should be "meas,tsys01"
- - reg: I2C address of the sensor (changeable via CSB pin)
-
- ------------------------
- | CSB | Device Address |
- ------------------------
- 1 0x76
- 0 0x77
-
-Example:
-
-tsys01@76 {
- compatible = "meas,tsys01";
- reg = <0x76>;
-};
diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml
index 8d8eadbab473..cb4fd8f29675 100644
--- a/Documentation/devicetree/bindings/trivial-devices.yaml
+++ b/Documentation/devicetree/bindings/trivial-devices.yaml
@@ -144,6 +144,8 @@ properties:
- meas,ms8607-humidity
# Measurement Specialities temp and pressure part of ms8607 device
- meas,ms8607-temppressure
+ # Measurement Specialties temperature sensor
+ - meas,tsys01
# Microchip differential I2C ADC, 1 Channel, 18 bit
- microchip,mcp3421
# Microchip differential I2C ADC, 2 Channel, 18 bit
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* Re: [PATCH v2 26/29] dt-bindings:iio:temperature:meas,tsys01 move to trivial-devices.yaml
2020-10-31 13:41 ` [PATCH v2 26/29] dt-bindings:iio:temperature:meas,tsys01 move to trivial-devices.yaml Jonathan Cameron
@ 2020-11-01 15:25 ` Manivannan Sadhasivam
0 siblings, 0 replies; 40+ messages in thread
From: Manivannan Sadhasivam @ 2020-11-01 15:25 UTC (permalink / raw)
To: Jonathan Cameron
Cc: linux-iio, Rob Herring, devicetree, Jonathan Cameron, Rob Herring
On Sat, Oct 31, 2020 at 01:41:07PM +0000, Jonathan Cameron wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> The existing binding description brings little value and the similar
> meas,* parts are in trivial-devices.yaml so move this one there
> to join them.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Acked-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Thanks,
Mani
> Reviewed-by: Rob Herring <robh@kernel.org>
> Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> .../bindings/iio/temperature/tsys01.txt | 19 -------------------
> .../devicetree/bindings/trivial-devices.yaml | 2 ++
> 2 files changed, 2 insertions(+), 19 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/iio/temperature/tsys01.txt b/Documentation/devicetree/bindings/iio/temperature/tsys01.txt
> deleted file mode 100644
> index 0d5cc5595d0c..000000000000
> --- a/Documentation/devicetree/bindings/iio/temperature/tsys01.txt
> +++ /dev/null
> @@ -1,19 +0,0 @@
> -* TSYS01 - Measurement Specialties temperature sensor
> -
> -Required properties:
> -
> - - compatible: should be "meas,tsys01"
> - - reg: I2C address of the sensor (changeable via CSB pin)
> -
> - ------------------------
> - | CSB | Device Address |
> - ------------------------
> - 1 0x76
> - 0 0x77
> -
> -Example:
> -
> -tsys01@76 {
> - compatible = "meas,tsys01";
> - reg = <0x76>;
> -};
> diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml
> index 8d8eadbab473..cb4fd8f29675 100644
> --- a/Documentation/devicetree/bindings/trivial-devices.yaml
> +++ b/Documentation/devicetree/bindings/trivial-devices.yaml
> @@ -144,6 +144,8 @@ properties:
> - meas,ms8607-humidity
> # Measurement Specialities temp and pressure part of ms8607 device
> - meas,ms8607-temppressure
> + # Measurement Specialties temperature sensor
> + - meas,tsys01
> # Microchip differential I2C ADC, 1 Channel, 18 bit
> - microchip,mcp3421
> # Microchip differential I2C ADC, 2 Channel, 18 bit
> --
> 2.28.0
>
^ permalink raw reply [flat|nested] 40+ messages in thread
* [PATCH v2 27/29] dt-bindings:iio:temperature:maxim,max31856 yaml conversion.
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (25 preceding siblings ...)
2020-10-31 13:41 ` [PATCH v2 26/29] dt-bindings:iio:temperature:meas,tsys01 move to trivial-devices.yaml Jonathan Cameron
@ 2020-10-31 13:41 ` Jonathan Cameron
2020-10-31 13:41 ` [PATCH v2 28/29] dt-bindings:iio:temperature:maxim_thermocouple.txt to maxim,max31855k.yaml Jonathan Cameron
` (2 subsequent siblings)
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:41 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree; +Cc: Jonathan Cameron, Rob Herring
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Simple txt to yaml conversion of this binding.
Paresh Chaudhary's email is bouncing so for now I've listed
myself as maintainer.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
---
.../bindings/iio/temperature/max31856.txt | 24 ---------
.../iio/temperature/maxim,max31856.yaml | 54 +++++++++++++++++++
2 files changed, 54 insertions(+), 24 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/temperature/max31856.txt b/Documentation/devicetree/bindings/iio/temperature/max31856.txt
deleted file mode 100644
index 06ab43bb4de8..000000000000
--- a/Documentation/devicetree/bindings/iio/temperature/max31856.txt
+++ /dev/null
@@ -1,24 +0,0 @@
-Maxim MAX31856 thermocouple support
-
-https://datasheets.maximintegrated.com/en/ds/MAX31856.pdf
-
-Optional property:
- - thermocouple-type: Type of thermocouple (THERMOCOUPLE_TYPE_K if
- omitted). Supported types are B, E, J, K, N, R, S, T.
-
-Required properties:
- - compatible: must be "maxim,max31856"
- - reg: SPI chip select number for the device
- - spi-max-frequency: As per datasheet max. supported freq is 5000000
- - spi-cpha: must be defined for max31856 to enable SPI mode 1
-
- Refer to spi/spi-bus.txt for generic SPI slave bindings.
-
- Example:
- temp-sensor@0 {
- compatible = "maxim,max31856";
- reg = <0>;
- spi-max-frequency = <5000000>;
- spi-cpha;
- thermocouple-type = <THERMOCOUPLE_TYPE_K>;
- };
diff --git a/Documentation/devicetree/bindings/iio/temperature/maxim,max31856.yaml b/Documentation/devicetree/bindings/iio/temperature/maxim,max31856.yaml
new file mode 100644
index 000000000000..873b34766676
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/temperature/maxim,max31856.yaml
@@ -0,0 +1,54 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/temperature/maxim,max31856.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Maxim MAX31856 thermocouple support
+
+maintainers:
+ - Jonathan Cameron <jic23@kernel.org>
+
+description: |
+ https://datasheets.maximintegrated.com/en/ds/MAX31856.pdf
+
+properties:
+ compatible:
+ const: maxim,max31856
+
+ reg:
+ maxItems: 1
+
+ spi-max-frequency: true
+ spi-cpha: true
+
+ thermocouple-type:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description:
+ Type of thermocouple (THERMOCOUPLE_TYPE_K if omitted).
+ Use defines in dt-bindings/iio/temperature/thermocouple.h.
+ Supported types are B, E, J, K, N, R, S, T.
+
+required:
+ - compatible
+ - reg
+ - spi-cpha
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/iio/temperature/thermocouple.h>
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ temp-sensor@0 {
+ compatible = "maxim,max31856";
+ reg = <0>;
+ spi-max-frequency = <5000000>;
+ spi-cpha;
+ thermocouple-type = <THERMOCOUPLE_TYPE_K>;
+ };
+ };
+...
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 28/29] dt-bindings:iio:temperature:maxim_thermocouple.txt to maxim,max31855k.yaml
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (26 preceding siblings ...)
2020-10-31 13:41 ` [PATCH v2 27/29] dt-bindings:iio:temperature:maxim,max31856 yaml conversion Jonathan Cameron
@ 2020-10-31 13:41 ` Jonathan Cameron
2020-10-31 13:41 ` [PATCH v2 29/29] dt-bindings:iio:temperature:ti,tmp07 yaml conversion Jonathan Cameron
2020-11-16 20:17 ` [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:41 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Matt Ranostay
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Given we already have another maxim thermocouple driver that isn't
covered by this binding it seems a better idea to chose to name it
after a specific part.
I added an additional example for the maxim,max6755 to illustrate
the need for spi-cpha for that part.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Acked-by: Matt Ranostay <matt.ranostay@konsulko.com>
---
.../iio/temperature/maxim,max31855k.yaml | 76 +++++++++++++++++++
.../iio/temperature/maxim_thermocouple.txt | 24 ------
2 files changed, 76 insertions(+), 24 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/temperature/maxim,max31855k.yaml b/Documentation/devicetree/bindings/iio/temperature/maxim,max31855k.yaml
new file mode 100644
index 000000000000..9969bac66aa1
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/temperature/maxim,max31855k.yaml
@@ -0,0 +1,76 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/temperature/maxim,max31855k.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Maxim MAX31855 and similar thermocouples
+
+maintainers:
+ - Matt Ranostay <matt.ranostay@konsulko.com>
+
+description: |
+ https://datasheets.maximintegrated.com/en/ds/MAX6675.pdf
+ https://datasheets.maximintegrated.com/en/ds/MAX31855.pdf
+
+properties:
+ compatible:
+ description:
+ The generic maxim,max31855 compatible is deprecated in favour of
+ the thermocouple type specific variants.
+ enum:
+ - maxim,max6675
+ - maxim,max31855
+ - maxim,max31855k
+ - maxim,max31855j
+ - maxim,max31855n
+ - maxim,max31855s
+ - maxim,max31855t
+ - maxim,max31855e
+ - maxim,max31855r
+
+ reg:
+ maxItems: 1
+
+ spi-max-frequency: true
+ spi-cpha: true
+
+required:
+ - compatible
+ - reg
+
+allOf:
+ - if:
+ properties:
+ compatible:
+ contains:
+ enum:
+ - maxim,max6675
+ then:
+ required:
+ - spi-cpha
+ else:
+ properties:
+ spi-cpha: false
+
+additionalProperties: false
+
+examples:
+ - |
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ temp-sensor@0 {
+ compatible = "maxim,max31855k";
+ reg = <0>;
+ spi-max-frequency = <4300000>;
+ };
+ temp-sensor@1 {
+ compatible = "maxim,max6675";
+ reg = <1>;
+ spi-max-frequency = <4300000>;
+ spi-cpha;
+ };
+ };
+...
diff --git a/Documentation/devicetree/bindings/iio/temperature/maxim_thermocouple.txt b/Documentation/devicetree/bindings/iio/temperature/maxim_thermocouple.txt
deleted file mode 100644
index bb85cd0e039c..000000000000
--- a/Documentation/devicetree/bindings/iio/temperature/maxim_thermocouple.txt
+++ /dev/null
@@ -1,24 +0,0 @@
-Maxim thermocouple support
-
-* https://datasheets.maximintegrated.com/en/ds/MAX6675.pdf
-* https://datasheets.maximintegrated.com/en/ds/MAX31855.pdf
-
-Required properties:
-
- - compatible: must be "maxim,max6675" or one of the following:
- "maxim,max31855k", "maxim,max31855j", "maxim,max31855n",
- "maxim,max31855s", "maxim,max31855t", "maxim,max31855e",
- "maxim,max31855r"; the generic "max,max31855" is deprecated.
- - reg: SPI chip select number for the device
- - spi-max-frequency: must be 4300000
- - spi-cpha: must be defined for max6675 to enable SPI mode 1
-
- Refer to spi/spi-bus.txt for generic SPI slave bindings.
-
-Example:
-
- max31855@0 {
- compatible = "maxim,max31855k";
- reg = <0>;
- spi-max-frequency = <4300000>;
- };
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* [PATCH v2 29/29] dt-bindings:iio:temperature:ti,tmp07 yaml conversion
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (27 preceding siblings ...)
2020-10-31 13:41 ` [PATCH v2 28/29] dt-bindings:iio:temperature:maxim_thermocouple.txt to maxim,max31855k.yaml Jonathan Cameron
@ 2020-10-31 13:41 ` Jonathan Cameron
2020-11-16 20:17 ` [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-10-31 13:41 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree
Cc: Jonathan Cameron, Rob Herring, Manivannan Sadhasivam
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Simple conversion from txt to yaml.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Acked-by: Manivannan Sadhasivam <mani@kernel.org>
---
.../bindings/iio/temperature/ti,tmp007.yaml | 57 +++++++++++++++++++
.../bindings/iio/temperature/tmp007.txt | 33 -----------
2 files changed, 57 insertions(+), 33 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/temperature/ti,tmp007.yaml b/Documentation/devicetree/bindings/iio/temperature/ti,tmp007.yaml
new file mode 100644
index 000000000000..3c2b7189fa2e
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/temperature/ti,tmp007.yaml
@@ -0,0 +1,57 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/temperature/ti,tmp007.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: IR thermopile sensor with integrated math engine
+
+maintainers:
+ - Manivannan Sadhasivam <manivannanece23@gmail.com>
+
+description: |
+ http://www.ti.com/lit/ds/symlink/tmp007.pdf
+
+properties:
+ compatible:
+ const: ti,tmp007
+
+ reg:
+ description: |
+ The I2C address of the sensor (changeable via ADR pins)
+ ------------------------------
+ |ADR1 | ADR0 | Device Address|
+ ------------------------------
+ 0 0 0x40
+ 0 1 0x41
+ 0 SDA 0x42
+ 0 SCL 0x43
+ 1 0 0x44
+ 1 1 0x45
+ 1 SDA 0x46
+ 1 SCL 0x47
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ temp-sensor@40 {
+ compatible = "ti,tmp007";
+ reg = <0x40>;
+ interrupt-parent = <&gpio0>;
+ interrupts = <5 0x08>;
+ };
+ };
+...
diff --git a/Documentation/devicetree/bindings/iio/temperature/tmp007.txt b/Documentation/devicetree/bindings/iio/temperature/tmp007.txt
deleted file mode 100644
index da0af234a357..000000000000
--- a/Documentation/devicetree/bindings/iio/temperature/tmp007.txt
+++ /dev/null
@@ -1,33 +0,0 @@
-* TI TMP007 - IR thermopile sensor with integrated math engine
-
-Link to datasheet: http://www.ti.com/lit/ds/symlink/tmp007.pdf
-
-Required properties:
-
- - compatible: should be "ti,tmp007"
- - reg: the I2C address of the sensor (changeable via ADR pins)
- ------------------------------
- |ADR1 | ADR0 | Device Address|
- ------------------------------
- 0 0 0x40
- 0 1 0x41
- 0 SDA 0x42
- 0 SCL 0x43
- 1 0 0x44
- 1 1 0x45
- 1 SDA 0x46
- 1 SCL 0x47
-
-Optional properties:
-
- - interrupts: interrupt mapping for GPIO IRQ (level active low)
-
-Example:
-
-tmp007@40 {
- compatible = "ti,tmp007";
- reg = <0x40>;
- interrupt-parent = <&gpio0>;
- interrupts = <5 0x08>;
-};
-
--
2.28.0
^ permalink raw reply related [flat|nested] 40+ messages in thread* Re: [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions.
2020-10-31 13:40 [PATCH v2 00/29] dt-bindings:iio: Another set of yaml conversions Jonathan Cameron
` (28 preceding siblings ...)
2020-10-31 13:41 ` [PATCH v2 29/29] dt-bindings:iio:temperature:ti,tmp07 yaml conversion Jonathan Cameron
@ 2020-11-16 20:17 ` Jonathan Cameron
29 siblings, 0 replies; 40+ messages in thread
From: Jonathan Cameron @ 2020-11-16 20:17 UTC (permalink / raw)
To: linux-iio, Rob Herring, devicetree; +Cc: Jonathan Cameron
On Sat, 31 Oct 2020 13:40:41 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> This set mostly consists of low hanging fruit along the way to converting
> all the existing IIO bindings.
>
> @Rob, I've dropped your Reviewed-by for patch 16 because of the major
> change introducing checking on spi-cpol XOR spi-cpha.
> It works, but I'm not sure there isn't a more minimal way of doing it.
>
> I could just have picked up the majority of these, but I forgot to
> cc the dt mailing list last time so want to resend them anyway.
Applied all but patch 16 where there are questions outstanding.
Thanks,
Jonathan
>
> Changes since v1:
> * Updated various maintainers to reflect email bounces.
> * dht11 - added note on aosong as probably manufacturer
> * hoperf,hp03 - fixed description
> * ti,dac082s085
> - Family typo
> - Put back the reference regulator in example.
> - Added checking of XOR of spi-cpha and spi-cpol
> * adi,ad7303 - drop adi,use-external-reference from example as no such thing.
>
> Jonathan Cameron (29):
> dt-bindings:iio:humidity:hdc100x Drop separate doc + add to
> trivial-devices
> dt-bindings:iio:humidity:htu21 Drop separate doc + add to
> trivial-devices
> dt-bindings:iio:humidity:st,hts221 yaml conversion.
> dt-bindings:iio:humidity:dht11 yaml conversion
> dt-bindings:iio:pressure:ms5637 Drop separate doc + add to
> trivial-devices
> dt-bindings:iio:pressure:murata,zpa2326 yaml conversion
> dt-bindings:iio:pressure:meas,ms5611 yaml conversion.
> dt-bindings:iio:pressure:hoperf,hp03 yaml conversion
> dt-bindings:iio:proximity:semtech,sx9500 yaml conversion.
> dt-bindings:iio:proximity:st,vl53l0x yaml conversion
> dt-bindings:iio:proximity:ams,as3935 yaml conversion
> dt-bindings:iio:dac:ti,dac5571 yaml conversion.
> dt-bindings:iio:dac:ti,dac7311 yaml conversion
> dt-bindings:iio:dac:ti,dac7512 yaml conversion
> dt-bindings:iio:dac:ti,dac7612 yaml conversion
> dt-bindings:iio:dac:ti,dac082s085 yaml conversion
> dt-bindings:iio:dac:adi,ad7303 yaml conversion
> dt-bindings:iio:dac:maxim,ds4424 yaml conversion
> dt-bindings:iio:dac:fsl,vf610-dac yaml conversion
> dt-bindings:iio:dac:microchip,mcp4725 yaml conversion
> dt-bindings:iio:dac:maxim,max5821 yaml conversion
> dt-bindings:iio:dac:nxp,lpc1850-dac yaml conversion.
> dt-bindings:iio:dac:adi,ad5758 yaml conversion
> dt-bindings:iio:temperature:melexis,mlx90614 yaml conversion
> dt-bindings:iio:temperature:melexis,mlx90632 conversion to yaml
> dt-bindings:iio:temperature:meas,tsys01 move to trivial-devices.yaml
> dt-bindings:iio:temperature:maxim,max31856 yaml conversion.
> dt-bindings:iio:temperature:maxim_thermocouple.txt to
> maxim,max31855k.yaml
> dt-bindings:iio:temperature:ti,tmp07 yaml conversion
>
> .../devicetree/bindings/iio/dac/ad5758.txt | 83 -----------
> .../devicetree/bindings/iio/dac/ad7303.txt | 23 ----
> .../bindings/iio/dac/adi,ad5758.yaml | 129 ++++++++++++++++++
> .../bindings/iio/dac/adi,ad7303.yaml | 50 +++++++
> .../devicetree/bindings/iio/dac/ds4424.txt | 20 ---
> .../bindings/iio/dac/fsl,vf610-dac.yaml | 55 ++++++++
> .../bindings/iio/dac/lpc1850-dac.txt | 19 ---
> .../devicetree/bindings/iio/dac/max5821.txt | 14 --
> .../bindings/iio/dac/maxim,ds4424.yaml | 45 ++++++
> .../bindings/iio/dac/maxim,max5821.yaml | 44 ++++++
> .../devicetree/bindings/iio/dac/mcp4725.txt | 35 -----
> .../bindings/iio/dac/microchip,mcp4725.yaml | 71 ++++++++++
> .../bindings/iio/dac/nxp,lpc1850-dac.yaml | 58 ++++++++
> .../bindings/iio/dac/ti,dac082s085.yaml | 79 +++++++++++
> .../bindings/iio/dac/ti,dac5571.txt | 24 ----
> .../bindings/iio/dac/ti,dac5571.yaml | 52 +++++++
> .../bindings/iio/dac/ti,dac7311.txt | 23 ----
> .../bindings/iio/dac/ti,dac7311.yaml | 49 +++++++
> .../bindings/iio/dac/ti,dac7512.txt | 20 ---
> .../bindings/iio/dac/ti,dac7512.yaml | 42 ++++++
> .../bindings/iio/dac/ti,dac7612.txt | 28 ----
> .../bindings/iio/dac/ti,dac7612.yaml | 53 +++++++
> .../bindings/iio/dac/ti-dac082s085.txt | 34 -----
> .../devicetree/bindings/iio/dac/vf610-dac.txt | 20 ---
> .../bindings/iio/humidity/dht11.txt | 14 --
> .../bindings/iio/humidity/dht11.yaml | 41 ++++++
> .../bindings/iio/humidity/hdc100x.txt | 17 ---
> .../bindings/iio/humidity/hts221.txt | 30 ----
> .../bindings/iio/humidity/htu21.txt | 13 --
> .../bindings/iio/humidity/st,hts221.yaml | 52 +++++++
> .../bindings/iio/pressure/hoperf,hp03.yaml | 47 +++++++
> .../devicetree/bindings/iio/pressure/hp03.txt | 17 ---
> .../bindings/iio/pressure/meas,ms5611.yaml | 57 ++++++++
> .../bindings/iio/pressure/ms5611.txt | 19 ---
> .../bindings/iio/pressure/ms5637.txt | 17 ---
> .../bindings/iio/pressure/murata,zpa2326.yaml | 62 +++++++++
> .../bindings/iio/pressure/zpa2326.txt | 29 ----
> .../bindings/iio/proximity/ams,as3935.yaml | 71 ++++++++++
> .../bindings/iio/proximity/as3935.txt | 34 -----
> .../iio/proximity/semtech,sx9500.yaml | 50 +++++++
> .../bindings/iio/proximity/st,vl53l0x.yaml | 42 ++++++
> .../bindings/iio/proximity/sx9500.txt | 23 ----
> .../bindings/iio/proximity/vl53l0x.txt | 18 ---
> .../bindings/iio/temperature/max31856.txt | 24 ----
> .../iio/temperature/maxim,max31855k.yaml | 76 +++++++++++
> .../iio/temperature/maxim,max31856.yaml | 54 ++++++++
> .../iio/temperature/maxim_thermocouple.txt | 24 ----
> .../iio/temperature/melexis,mlx90614.yaml | 50 +++++++
> .../iio/temperature/melexis,mlx90632.yaml | 55 ++++++++
> .../bindings/iio/temperature/mlx90614.txt | 24 ----
> .../bindings/iio/temperature/mlx90632.txt | 28 ----
> .../bindings/iio/temperature/ti,tmp007.yaml | 57 ++++++++
> .../bindings/iio/temperature/tmp007.txt | 33 -----
> .../bindings/iio/temperature/tsys01.txt | 19 ---
> .../devicetree/bindings/trivial-devices.yaml | 24 ++++
> 55 files changed, 1465 insertions(+), 726 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/ad5758.txt
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/ad7303.txt
> create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5758.yaml
> create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad7303.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/ds4424.txt
> create mode 100644 Documentation/devicetree/bindings/iio/dac/fsl,vf610-dac.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/lpc1850-dac.txt
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/max5821.txt
> create mode 100644 Documentation/devicetree/bindings/iio/dac/maxim,ds4424.yaml
> create mode 100644 Documentation/devicetree/bindings/iio/dac/maxim,max5821.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/mcp4725.txt
> create mode 100644 Documentation/devicetree/bindings/iio/dac/microchip,mcp4725.yaml
> create mode 100644 Documentation/devicetree/bindings/iio/dac/nxp,lpc1850-dac.yaml
> create mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac5571.txt
> create mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac5571.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac7311.txt
> create mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac7311.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac7512.txt
> create mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac7512.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac7612.txt
> create mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac7612.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/ti-dac082s085.txt
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/vf610-dac.txt
> delete mode 100644 Documentation/devicetree/bindings/iio/humidity/dht11.txt
> create mode 100644 Documentation/devicetree/bindings/iio/humidity/dht11.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/humidity/hdc100x.txt
> delete mode 100644 Documentation/devicetree/bindings/iio/humidity/hts221.txt
> delete mode 100644 Documentation/devicetree/bindings/iio/humidity/htu21.txt
> create mode 100644 Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml
> create mode 100644 Documentation/devicetree/bindings/iio/pressure/hoperf,hp03.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/pressure/hp03.txt
> create mode 100644 Documentation/devicetree/bindings/iio/pressure/meas,ms5611.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/pressure/ms5611.txt
> delete mode 100644 Documentation/devicetree/bindings/iio/pressure/ms5637.txt
> create mode 100644 Documentation/devicetree/bindings/iio/pressure/murata,zpa2326.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/pressure/zpa2326.txt
> create mode 100644 Documentation/devicetree/bindings/iio/proximity/ams,as3935.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/proximity/as3935.txt
> create mode 100644 Documentation/devicetree/bindings/iio/proximity/semtech,sx9500.yaml
> create mode 100644 Documentation/devicetree/bindings/iio/proximity/st,vl53l0x.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/proximity/sx9500.txt
> delete mode 100644 Documentation/devicetree/bindings/iio/proximity/vl53l0x.txt
> delete mode 100644 Documentation/devicetree/bindings/iio/temperature/max31856.txt
> create mode 100644 Documentation/devicetree/bindings/iio/temperature/maxim,max31855k.yaml
> create mode 100644 Documentation/devicetree/bindings/iio/temperature/maxim,max31856.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/temperature/maxim_thermocouple.txt
> create mode 100644 Documentation/devicetree/bindings/iio/temperature/melexis,mlx90614.yaml
> create mode 100644 Documentation/devicetree/bindings/iio/temperature/melexis,mlx90632.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/temperature/mlx90614.txt
> delete mode 100644 Documentation/devicetree/bindings/iio/temperature/mlx90632.txt
> create mode 100644 Documentation/devicetree/bindings/iio/temperature/ti,tmp007.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/temperature/tmp007.txt
> delete mode 100644 Documentation/devicetree/bindings/iio/temperature/tsys01.txt
>
^ permalink raw reply [flat|nested] 40+ messages in thread