- 21 Nov, 2020 15 commits
-
-
Alexandru Ardelean authored
It seems that when this was tested the happy case was more tested. A few of the userspace apps rely on this returning negative error codes in case an ioctl() is not available. When running multiple ioctl() handlers or when calling an ioctl() that doesn't exist, IIO_IOCTL_UNHANDLED is returned. In that case -EINVAL should be returned. Fixes: 8dedcc3e ("iio: core: centralize ioctl() calls to the main chardev") Signed-off-by:
Alexandru Ardelean <alexandru.ardelean@analog.com> Link: https://lore.kernel.org/r/20201117095154.7189-1-alexandru.ardelean@analog.comSigned-off-by:
Jonathan Cameron <Jonathan.Cameron@huawei.com>
-
Alexandru Ardelean authored
The change is mostly cosmetic. This organizes the order of assignment of the members of 'iio_buffer_fileops' to be similar to the one as defined in the 'struct file_operations' type. Signed-off-by:
-
Alexandru Ardelean authored
There is no matching spi_get_drvdata() in the driver. This looks like a left-over from before the driver was converted to device-managed functions. Signed-off-by:
-
Alexandru Ardelean authored
There is no matching spi_get_drvdata() in the driver. This looks like a left-over from before the driver was converted to device-managed functions. Signed-off-by:
-
Alexandru Ardelean authored
This seems to have been copied from a driver that calls spi_set_drvdata() but doesn't call spi_get_drvdata(). Setting a private object on the SPI device's object isn't necessary if it won't be accessed. This change removes the spi_set_drvdata() call. Signed-off-by:
Marcelo Schmitt <marcelo.schmitt1@gmail.com> Reviewed-by:
-
Gustavo A. R. Silva authored
In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning by explicitly adding a break statement instead of letting the code fall through to the next case. Signed-off-by:
Gustavo A. R. Silva <gustavoars@kernel.org> Link: https://github.com/KSPP/linux/issues/115 Link: https://lore.kernel.org/r/b3c1c3f9c76f2f0e832f956587f227e44af57d3d.1605896060.git.gustavoars@kernel.orgSigned-off-by:
-
Alexandru Ardelean authored
The iio_buffer_set_attrs() is no longer used in the drivers, so it can be removed now. Signed-off-by:
Andy Shevchenko <andy.shevchenko@gmail.com> Link: https://lore.kernel.org/r/20200929125949.69934-10-alexandru.ardelean@analog.comSigned-off-by:
-
Alexandru Ardelean authored
This change switches to the new iio_triggered_buffer_setup_ext() function and removes the iio_buffer_set_attrs() call, for assigning the HW FIFO attributes to the buffer. Signed-off-by:
-
Alexandru Ardelean authored
This change switches to the new devm_iio_triggered_buffer_setup_ext() function and removes the iio_buffer_set_attrs() call, for assigning the HW FIFO attributes to the buffer. Signed-off-by:
-
Alexandru Ardelean authored
This change switches to the new devm_iio_triggered_buffer_setup_ext() function and removes the iio_buffer_set_attrs() call, for assigning the HW FIFO attributes to the buffer. Signed-off-by:
-
Alexandru Ardelean authored
This change switches to the new iio_triggered_buffer_setup_ext() function and removes the iio_buffer_set_attrs() call, for assigning the HW FIFO attributes to the buffer. Signed-off-by:
-
Alexandru Ardelean authored
This change switches to the new devm_iio_triggered_buffer_setup_ext() function and removes the iio_buffer_set_attrs() call, for assigning the HW FIFO attributes to the buffer. Signed-off-by:
-
Alexandru Ardelean authored
This change adds a parameter to the {devm_}iio_triggered_buffer_setup() functions to assign the extra sysfs buffer attributes that are typically assigned via iio_buffer_set_attrs(). The functions also get renamed to iio_triggered_buffer_setup_ext() & devm_iio_triggered_buffer_setup_ext(). For backwards compatibility the old {devm_}iio_triggered_buffer_setup() functions are now macros wrap the new (renamed) functions with NULL for the buffer attrs. The aim is to remove iio_buffer_set_attrs(), so in the iio_triggered_buffer_setup_ext() function the attributes are assigned directly to 'buffer->attrs'. When adding multiple IIO buffers per IIO device, it can be pretty cumbersome to first allocate a set of buffers, then to dig them out of IIO to assign extra attributes (with iio_buffer_set_attrs()). Naturally, the best way would be to provide them at allocation time, which is what this change does. At this moment, buffers allocated with {devm_}iio_triggered_buffer_setup() are the only ones in mainline IIO to call iio_buffer_set_attrs(). Signed-off-by: -
Alexandru Ardelean authored
This change is mostly cosmetic, but it's also a pre-cursor to the the change for 'iio_buffer_set_attrs()', where the helper gets updated to better support multiple IIO buffers for 1 IIO device. The only functional change is that the error message for the trigger alloc failure is bound to the parent device vs the IIO device object. Also, the new at91_adc_buffer_and_trigger_init() function was moved after the definition of the 'at91_adc_fifo_attributes'. Signed-off-by:
-
Alexandru Ardelean authored
The iio_buffer_set_attrs() helper will be removed in this series. So, just assign the attributes of the DMAEngine buffer logic directly. This is IIO buffer core context, so there is direct access to the buffer->attrs object. Signed-off-by:
-
- 16 Nov, 2020 25 commits
-
-
Jonathan Cameron authored
No need to maintain a separate document for such a simple binding. Signed-off-by:
Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/20201031182922.743153-8-jic23@kernel.org
-
Jonathan Cameron authored
Extremely simple binding so no need to maintain a separate file. Signed-off-by:
-
Jonathan Cameron authored
This binding is so simple there is no obvious advantage in maintaining a separate binding doc file for it. As such, move it to trivial-devices.yaml Signed-off-by:
-
Jonathan Cameron authored
Simple SPI binding that doesn't need a separate file. During conversion I looked up the individual part number descriptions in the datasheet so that we could give slightly more detail in trivial-device.yaml. Signed-off-by:
Slawomir Stepien <sst@poczta.fm> Reviewed-by:
-
Jonathan Cameron authored
Simple binding where there is no obvious benefit in maintaining a separate file. Hence document in trivial-devices.yaml and drop the txt file. Signed-off-by:
-
Jonathan Cameron authored
Very simple binding so no need to maintain a separate file. Signed-off-by:
-
Jonathan Cameron authored
The binding for this device and the sgpc3 is very simple so lets not maintain a seperate document for this one. Of course we can always add a document again if the binding becomes more complex in future. Signed-off-by:
-
Jonathan Cameron authored
Simple conversion from txt to yaml. Signed-off-by:
Manivannan Sadhasivam <mani@kernel.org> Link: https://lore.kernel.org/r/20201031134110.724233-30-jic23@kernel.org
-
Jonathan Cameron authored
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:
Matt Ranostay <matt.ranostay@konsulko.com> Link: https://lore.kernel.org/r/20201031134110.724233-29-jic23@kernel.org
-
Jonathan Cameron authored
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 authored
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:
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Link: https://lore.kernel.org/r/20201031134110.724233-27-jic23@kernel.org
-
Jonathan Cameron authored
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:
Crt Mori <cmo@melexis.com> Cc: Crt Mori <cmo@melexis.com> Link: https://lore.kernel.org/r/20201031134110.724233-26-jic23@kernel.org
-
Jonathan Cameron authored
Simple conversion from txt to yaml. Signed-off-by:
-
Jonathan Cameron authored
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 authored
Very similar binding to that for the ADC on the same device. Conversion from txt to yaml format. Signed-off-by:
Vladimir Zapolskiy <vz@mleia.com> Link: https://lore.kernel.org/r/20201031134110.724233-23-jic23@kernel.org
-
Jonathan Cameron authored
Simple txt to yaml conversion for this binding description. Signed-off-by:
-
Jonathan Cameron authored
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 authored
Simple binding to convert. Example expanded a little to include an example bus. Signed-off-by:
-
Jonathan Cameron authored
Simple conversion of this straight forward binding. Signed-off-by:
-
Jonathan Cameron authored
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 authored
Simple conversion from txt to yaml. No significant adjustments. Signed-off-by:
Ricardo Ribalda Delgado <ricardo@ribalda.com> Link: https://lore.kernel.org/r/20201031134110.724233-16-jic23@kernel.org
-
Jonathan Cameron authored
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 authored
Very simple conversion of this binding from txt to yaml. Signed-off-by:
-
Jonathan Cameron authored
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:
Sean Nyekjaer <sean@geanix.com> Link: https://lore.kernel.org/r/20201031134110.724233-13-jic23@kernel.org
-
Jonathan Cameron authored
A straight forward conversion of this binding. I have added a maximum SPI frequency from the datasheet. Signed-off-by:
-
