- 28 Feb, 2024 40 commits
-
-
Peng Fan authored
Per i.MX93 Reference Mannual Rev.4, 12/2013, there is no interrupt 268, so drop it. Signed-off-by:
Peng Fan <peng.fan@nxp.com> Acked-by:
Conor Dooley <conor.dooley@microchip.com> Link: https://lore.kernel.org/r/20240226130826.3824251-1-peng.fan@oss.nxp.comSigned-off-by:
Jonathan Cameron <Jonathan.Cameron@huawei.com>
-
Krzysztof Kozlowski authored
Reference the of_device_id table in the driver structure, so it will be used for module autoloading and device matching. This fixes clang W=1 warning: isl29501.c:999:34: error: unused variable 'isl29501_i2c_matches' [-Werror,-Wunused-const-variable] Signed-off-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Link: https://lore.kernel.org/r/20240225201654.49450-2-krzysztof.kozlowski@linaro.orgSigned-off-by:
-
Krzysztof Kozlowski authored
Drop description of non-existing 'struct pm8xxx_chan_info' member: qcom-pm8xxx-xoadc.c:386: warning: Excess struct member 'scale_fn_type' description in 'pm8xxx_chan_info' Signed-off-by:
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Link: https://lore.kernel.org/r/20240225202744.60500-1-krzysztof.kozlowski@linaro.orgSigned-off-by:
-
Krzysztof Kozlowski authored
dtschema defines label as string, so $ref in other bindings is redundant. Signed-off-by:
-
Marco Felsch authored
Add the support to provide an optional label like we do for ADC channels to identify the device more easily. Signed-off-by:
Marco Felsch <m.felsch@pengutronix.de> Reviewed-by:
-
Ondrej Jirman authored
As I am submitting the driver and have the device to test. I'll maintain the driver. Signed-off-by:
Ondrej Jirman <megi@xff.cz> Link: https://lore.kernel.org/r/20240222011341.3232645-5-megi@xff.czSigned-off-by:
-
Icenowy Zheng authored
AF8133J is a simple I2C-connected magnetometer, without interrupts. Add a simple IIO driver for it. Signed-off-by:
Icenowy Zheng <icenowy@aosc.io> Signed-off-by:
Dalton Durst <dalton@ubports.com> Signed-off-by:
Shoji Keita <awaittrot@shjk.jp> Co-developed-by:
Andrey Skvortsov <andrej.skvortzov@gmail.com> Tested-by:
-
Icenowy Zheng authored
Voltafield AF8133J is a simple magnetometer sensor produced by Voltafield Technology Corp, with dual power supplies (one for core and one for I/O) and active-low reset pin. The sensor has configurable range 1.2 - 2.2 mT and a software controlled standby mode. Add a device tree binding for it. Signed-off-by:
-
Icenowy Zheng authored
Voltafile Technology Corp. is a company that produces MEMS sensors. Add a DT vendor prefix for it. Signed-off-by:
-
Quentin Schulz authored
devm_reset_control_get_optional_exclusive does what this driver is trying to do in its probe function, therefore let's switch over to that subsystem function. Signed-off-by:
Quentin Schulz <quentin.schulz@theobroma-systems.com> Reviewed-by:
Heiko Stuebner <heiko@sntech.de> Reviewed-by:
Andy Shevchenko <andy.shevchenko@gmail.com> Link: https://lore.kernel.org/r/20240223-saradcv2-chan-mask-v1-3-84b06a0f623a@theobroma-systems.comSigned-off-by:
-
Quentin Schulz authored
Some of the registers on the SARADCv2 have bits write protected except if another bit is set. This is usually done by having the lowest 16 bits store the data to write and the highest 16 bits specify which of the 16 lowest bits should have their value written to the hardware block. The write_enable mask for the channel selection was incorrect because it was just the value shifted by 16 bits, which means it would only ever write bits and never clear them. So e.g. if someone starts a conversion on channel 5, the lowest 4 bits would be 0x5, then starts a conversion on channel 0, it would still be 5. Instead of shifting the value by 16 as the mask, let's use the OR'ing of the appropriate masks shifted by 16. Note that this is not an issue currently because the only SARADCv2 currently supported has a reset defined in its Device Tree, that reset resets the SARADC controller before starting a conversion on a channel. However, this reset is handled as optional by the probe function and thus proper masking should be used in the event an SARADCv2 without a reset ever makes it upstream. Fixes: 757953f8 ("iio: adc: rockchip_saradc: Add support for RK3588") Signed-off-by:
-
Quentin Schulz authored
The SARADCv2 on RK3588 (the only SoC currently supported that has an SARADCv2) selects the channel through the channel_sel bitfield which is the 4 lowest bits, therefore the mask should be GENMASK(3, 0) and not GENMASK(15, 0). Fixes: 757953f8 ("iio: adc: rockchip_saradc: Add support for RK3588") Signed-off-by:
-
Javier Carrasco authored
The VEML6075 requires a single supply to operate. The property already exists in the bindings and it is used in the example, but it is still not on the list of required properties. Signed-off-by:
Javier Carrasco <javier.carrasco.cruz@gmail.com> Acked-by:
-
Marius Cristea authored
This is the iio driver for Microchip PAC193X series of Power Monitor with Accumulator chip family. Signed-off-by:
Marius Cristea <marius.cristea@microchip.com> Link: https://lore.kernel.org/r/20240222164206.65700-3-marius.cristea@microchip.comSigned-off-by:
-
Marius Cristea authored
This is the device tree schema for iio driver for Microchip PAC193X series of Power Monitors with Accumulator. Signed-off-by:
-
Nuno Sa authored
Getting the part name with 'spi_get_device_id(spi)->name' is not a very good pattern. Hence, explicitly add the name in the struct chip_info and use that instead. Signed-off-by:
Nuno Sa <nuno.sa@analog.com> Link: https://lore.kernel.org/r/20240222-ltc2983-misc-improv-v1-4-cf7d4457e98c@analog.comSigned-off-by:
-
Nuno Sa authored
Rename ltc2983_parse_dt() to ltc2983_parse_fw() as there's no explicit dependency on devicetree. No functional change intended... Signed-off-by:
-
Nuno Sa authored
Use spi_get_device_match_data() as it simplifies the code. No functional change intended... Signed-off-by:
-
Dan Carpenter authored
The "val" variable comes from the user so we need to ensure that it's not zero. In fact, all negative values are invalid as well. Add a check for that. Fixes: 00ef7708 ("iio: adc: ti-ads1298: Add driver") Acked-by:
Mike Looijmans <mike.looijmans@topic.nl> Signed-off-by:
Dan Carpenter <dan.carpenter@linaro.org> Link: https://lore.kernel.org/r/c32c9087-86de-423b-8101-67b4a7f9d728@moroto.mountainSigned-off-by:
-
Dan Carpenter authored
There is a copy and paste bug here, it should be "reg_vref" instead of "reg_avdd". The "priv->reg_avdd" variable is zero so it ends up returning success. Fixes: 00ef7708 ("iio: adc: ti-ads1298: Add driver") Signed-off-by:
-
Ramona Gradinariu authored
Add documentation for adis16475 driver which describes the driver device files and shows how the user may use the ABI for various scenarios (configuration, measurement, etc.). Signed-off-by:
Ramona Gradinariu <ramona.gradinariu@analog.com> Link: https://lore.kernel.org/r/20240221085848.991413-4-ramona.gradinariu@analog.comSigned-off-by:
-
Ramona Gradinariu authored
Add documentation for IIO device buffers describing buffer attributes and how data is structured in buffers using scan elements. Signed-off-by:
-
Ramona Gradinariu authored
Refactor index.rst such that it contains a section for generic documentation and a section for Kernel Drivers documentation. Signed-off-by:
-
Dumitru Ceclan authored
This adds support for LTC6373 36 V Fully-Differential Programmable-Gain Instrumentation Amplifier with 25 pA Input Bias Current. The user can program the gain to one of seven available settings through a 3-bit parallel interface (A2 to A0). Signed-off-by:
Dumitru Ceclan <mitrutzceclan@gmail.com> Reviewed-by:
-
Dumitru Ceclan authored
Change the match table to use pointers instead of device ids. Remove type from state as it is not used anymore. Also make the chip_info structures const. Signed-off-by:
-
Dumitru Ceclan authored
Move gain-dB<->code conversion logic from read_raw and write_raw to chip_info callbacks. Signed-off-by:
-
Dumitru Ceclan authored
The LTC6373 is a silicon, 3-bit Fully-Differential digital instrumentation amplifier that supports the following programmable gains (Vout/Vin): G = 0.25, 0.5, 1, 2, 4, 8, 16 + Shutdown. Acked-by:
-
Dumitru Ceclan authored
ADRF5740 and HMC540S have a 4 bit parallel interface. Update ctrl-gpios description and min/maxItems values depending on the matched compatible to correctly reflect the hardware properties. Fixes: 79f2ff64 ("dt-bindings: iio: hmc425a: add entry for ADRF5740 Attenuator") Fixes: 20f87a9a ("dt-bindings: iio: hmc425a: add entry for HMC540S") Acked-by:
-
Josua Mayer authored
HDC2010 and HDC2080 humidity sensors both have an interrupt / data-ready signal which can be used for signaling to the host. Add binding for "interrupts" property so that boards wiring this signal may describe the connection. Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Josua Mayer <josua@solid-run.com> Link: https://lore.kernel.org/r/20240219-iio-hdc20x0-interrupt-binding-v7-1-c8ffb39c3768@solid-run.comSigned-off-by:
-
Thomas Haemmerle authored
Add support to specify the VCC supply which is required to power the device. According the datasheet 7.3.1 Power Up, the device needs 1.5ms after the supply voltage reaches the operating range before the communcation can begin. Signed-off-by:
Thomas Haemmerle <thomas.haemmerle@leica-geosystems.com> Signed-off-by:
-
Thomas Haemmerle authored
Add the binding to specify the vcc supply. We can't make it required since this would break the backward compatibility. Reviewed-by:
-
Arturas Moskvinas authored
Use devm_* APIs to enable/disable regulator and to register in IIO infrastructure. Signed-off-by:
Arturas Moskvinas <arturas.moskvinas@gmail.com> Link: https://lore.kernel.org/r/20240219074139.193464-2-arturas.moskvinas@gmail.comSigned-off-by:
-
Sean Rhodes authored
Implement kxj_acpi_orientation to retrieve mount matrix from ACPI ROTM method Cc: Jonathan Cameron <jic23@kernel.org> Cc: Lars-Peter Clausen <lars@metafoo.de> Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de> Signed-off-by:
Sean Rhodes <sean@starlabs.systems> Link: https://lore.kernel.org/r/19d7a10aae5238a2c8db37da1f74edb86480e17e.1708293140.git.sean@starlabs.systemsSigned-off-by:
-
Jonathan Cameron authored
of.h was only included for this definition, so include the correct header instead. Reviewed-by:
Andy Shevchenko <andriy.shevchenko@linux.intel.com> Link: https://lore.kernel.org/r/20240218173323.1023703-9-jic23@kernel.orgSigned-off-by:
-
Jonathan Cameron authored
The only of specific definition used is of_device_id table and that is found in mod_devicetable.h not of.h Reviewed-by:
-
Jonathan Cameron authored
The only of specific definition used is of_device_id table and that is found in mod_devicetable.h not of.h Reviewed-by:
-
Jonathan Cameron authored
The only of specific definition used is of_device_id table and that is found in mod_devicetable.h not of.h Reviewed-by:
-
Jonathan Cameron authored
of.h was only included to get access to this structure, so include the correct header directly instead. Reviewed-by:
-
Jonathan Cameron authored
The only of specific definition used is of_device_id table and that is found in mod_devicetable.h not of.h Reviewed-by:
-
Jonathan Cameron authored
Nothing from linux/of.h used in this driver. Reviewed-by:
-
