- 14 Feb, 2020 24 commits
-
-
Jean-Baptiste Maneyrol authored
Add missing mpu6000 and new icm20609, icm20689, icm20690, and iam20680. Signed-off-by:
Jean-Baptiste Maneyrol <jmaneyrol@invensense.com> Signed-off-by:
Jonathan Cameron <Jonathan.Cameron@huawei.com>
-
Jean-Baptiste Maneyrol authored
As every chip has some little variant in LPF bandwidth values, use common values that are working for all chips. Simplify the LPF setting function. Signed-off-by:
-
Jean-Baptiste Maneyrol authored
Same generation as ICM20602 but different registers. Signed-off-by:
-
Jean-Baptiste Maneyrol authored
Automotive certified IMU, similar to ICM20608. Signed-off-by:
-
Jean-Baptiste Maneyrol authored
They are similar to ICM20608 chip. Signed-off-by:
-
Jean-Baptiste Maneyrol authored
Use device_get_match_data for using of and acpi tables. In spi support add missing mpu6515 and of match table. Reorganize Kconfig to display chips grouped by generations. Signed-off-by:
-
Tomer Maimon authored
Modify NPCM ADC reset support from direct register access to reset controller support. please make sure to modify NPCM adc device tree parameters as described at nuvoton,npcm-adc.txt document for using this change. Note for anyone noting that this is a breaking change, this is on a BMC and effectively in a close ecosystem so it is fine to rely on DT and kernel being updated together. Signed-off-by:
Tomer Maimon <tmaimon77@gmail.com> Signed-off-by:
-
Tomer Maimon authored
Add NPCM ADC reset binding documentation. Signed-off-by:
Rob Herring <robh@kernel.org> Signed-off-by:
-
Guido Günther authored
This is modelled after the vcnl4035 driver. For the vcnl40{0,1,2}0 we don't do anything since they use on demand measurement. Signed-off-by:Guido Günther <agx@sigxcpu.org> Signed-off-by:
-
Guido Günther authored
This will be useful when introducing runtime pm. Signed-off-by:
-
Uwe Kleine-König authored
These two defines are unused since the driver was introduced in commit 02b829f9 ("iio: dac: Add support for ltc2632 DACs"). Signed-off-by:
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by:
-
Uwe Kleine-König authored
The only difference between LTC2632 and LTC2636 is that the former has two DAC channels while the latter has eight. Signed-off-by:
-
Uwe Kleine-König authored
The channel data for ltc2632l12 and ltc2632h12 are identical. So there is no gain in using two different (but identical) channel descriptions. The only side effect of this change is some memory savings. Signed-off-by:
-
Uwe Kleine-König authored
The ltc2636 family of devices is register compatible with the ltc2636 chips, it just features 8 instead of 2 channels. Signed-off-by:
-
Andreas Klinger authored
Add suspend and resume operations for being used by optional power management. The suspend function is switching off an GPIO which can be used by the hardware to switch power off. The resume function is switching the GPIO on and sleeps an adjustable time to give the device a chance to be up and running. If activated the driver gets into autosuspend after some time of inactivity. Suggested-by:
Franz Parzer <rpi-receiver@htl-steyr.ac.at> Signed-off-by:
Andreas Klinger <ak@it-klinger.de> Signed-off-by:
-
Andreas Klinger authored
Add GPIO line and startup time for usage of power management Reviewed-by:
-
Colin Ian King authored
A null pointer deference on pdata can occur if the allocation of pdata fails. Fix this by adding a null pointer check and handle the -ENOMEM failure in the caller. Addresses-Coverity: ("Dereference null return value") Fixes: 3ce85cc4 ("iio: st_sensors: get platform data from device tree") Signed-off-by:Colin Ian King <colin.king@canonical.com> Reviewed-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
-
Alexandru Tachici authored
This patch adds the LOW_PASS_FILTER_3DB_FREQUENCY attribute in iio_chan_spec for each channel. The used filters are sinc3 or sinc4. The filter type with the highest output data rate is used when setting a low pass frequency in the channel's sysfs. Signed-off-by:
Alexandru Tachici <alexandru.tachici@analog.com> Signed-off-by:
-
Colin Ian King authored
There is a spelling mistake and grammar mistake in a dev_err message. Fix it. Also include Joe Perches' additional suggestions around: * Missing newlines * Excess braces * Odd indentation * Some grammar Signed-off-by:
Alexandru Ardelean <alexandru.ardelean@analog.com> Suggested-by: Joe Perches <joe@perches.com> # Additional cleanups etc. Signed-off-by:
-
Linus Walleij authored
This driver handles two different Sharp sensors that have been proposed for merging to the mainline kernel over the years, and already has a limited proximity-only driver in the input subsystem. These components are completely different from the confusingly similarly named Sharp GP2AP020A00F, for which we have a driver in drivers/iio/light/gp2ap020a00f.c The two components GP2AP002A00F and GP2AP002S00F are distinctively different but similar: they share the same set of registers but differ slightly in the I2C protocol. Instead of the approach by the previous input driver, we create a combined IIO proximity and light sensor driver. The plan is to merge this driver and delete the input driver. The pieces for the driver are picked all over the place after researching and grepping through a few different vendor trees and driver submissions. We merge it under the light sensors because: - It has similarities with the Capella CM3605 light sensor and proximity driver which is there. - It is related to the GP2AP020A00F driver which is also there. This driver was tested with the Samsung GT-S7710 mobile phone which has the GP2AP002S00F proximity sensor mounted. The suspend/resume cycle will disable the interrupt from the sensor. If someone would desire to use this interrupt for wakeup, the driver will need modifications. Cc: Stephan Gerhold <stephan@gerhold.net> Cc: Minkyu Kang <mk7.kang@samsung.com> Cc: Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com> Cc: Jonathan Bakker <xc-racer2@live.ca> Cc: Oskar Andero <oskar.andero@gmail.com> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com> Tested-by:
Jonathan Bakker <xc-racer2@live.ca> Signed-off-by:
-
Linus Walleij authored
This adds device tree bindings for the GP2AP002 light and proximity sensor. As with other early proximity sensors (~2010) the light sensor and proximity sensors were combined into a single component. Cc: Stephan Gerhold <stephan@gerhold.net> Cc: Minkyu Kang <mk7.kang@samsung.com> Cc: Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com> Cc: Jonathan Bakker <xc-racer2@live.ca> Cc: Oskar Andero <oskar.andero@gmail.com> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com> Cc: devicetree@vger.kernel.org Reviewed-by:
-
JieunKim authored
odr to odr_table gain to fs_table 'gain' is actually in 'st_lsm6dsx_fs' structure of 'fs_table' Signed-off-by:
JieunKim <jieun.kim4758@gmail.com> Signed-off-by:
-
Andy Shevchenko authored
Use st_sensors_dev_name_probe() instead open coded variant. Signed-off-by:
Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by:
-
Fabrice Gasnier authored
Convert the STM32 ADC binding to DT schema format using json-schema Signed-off-by:
Fabrice Gasnier <fabrice.gasnier@st.com> Reviewed-by:
-
- 12 Feb, 2020 14 commits
-
-
Chris Packham authored
This reverts commit 075a1e87. Now that the build issues have been fixed we can resume build testing. Signed-off-by:
Chris Packham <chris.packham@alliedtelesis.co.nz> Link: https://lore.kernel.org/r/20200205001116.14096-7-chris.packham@alliedtelesis.co.nzSigned-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Chris Packham authored
Remove the typedef and update usage to use the union. Signed-off-by:
-
Chris Packham authored
Remove declaration of union cvmx_helper_link_info as typedef and update uses to use the union. Signed-off-by:
-
Chris Packham authored
Remove typedef declaration from struct cvmx_wqe and replace its previous uses with new struct declaration. Signed-off-by:
-
Chris Packham authored
This reverts commit 710d7fbe. Re-instate the code so subsequent commits can clean it up and get it building properly. Signed-off-by:
-
Chris Packham authored
This reverts commit 95ace52e. Re-instate the code so subsequent commits can clean it up and get it building properly. Signed-off-by:
-
Greg Kroah-Hartman authored
It's been over 6 months, and no one has noticed that these drivers are deleted, probably because no one actually has this hardware. As no one has volunteered to maintain the code, let's drop it for good. Link: https://lore.kernel.org/r/20200210231417.GA1736729@kroah.comSigned-off-by:
-
Ajay Singh authored
Refactor handling of P2P specific action frames. Make use of 'struct' to handle the P2P frames instead of manipulating using 'buf' pointer. Signed-off-by:
Ajay Singh <ajay.kathat@microchip.com> Link: https://lore.kernel.org/r/20200212154503.8835-1-ajay.kathat@microchip.comSigned-off-by:
-
Marcelo Diop-Gonzalez authored
There are a few places where a service's reference count is incremented, something quick is done, and the refcount is dropped. This can be made a little simpler/faster by not grabbing a reference in these cases. Signed-off-by:
Marcelo Diop-Gonzalez <marcgonzalez@google.com> Link: https://lore.kernel.org/r/ac6186ac888f1acf489b5b504efcba8b0d6a8b25.1581532523.git.marcgonzalez@google.comSigned-off-by:
-
Marcelo Diop-Gonzalez authored
Currently reference counts are implemented by locking service_spinlock and then incrementing the service's ->ref_count field, calling kfree() when the last reference has been dropped. But at the same time, there's code in multiple places that dereferences pointers to services without having a reference, so there could be a race there. It should be possible to avoid taking any lock in unlock_service() or service_release() because we are setting a single array element to NULL, and on service creation, a mutex is locked before looking for a NULL spot to put the new service in. Using a struct kref and RCU-delaying the freeing of services fixes this race condition while still making it possible to skip grabbing a reference in many places. Also it avoids the need to acquire a single spinlock when e.g. taking a reference on state->services[i] when somebody else is in the middle of taking a reference on state->services[j]. Signed-off-by:
-
Kaaira Gupta authored
Fix three checkpatch.pl warnings of 'quoted string split across lines' in gasket_core.c by merging the strings in one line. Though some strings are over 80 characters long, fixing this warning is necessary to ease grep-ing the source for printk. Signed-off-by:
Kaaira Gupta <kgupta@es.iitr.ac.in> Link: https://lore.kernel.org/r/20200212175826.GA5967@kaaira-HP-Pavilion-NotebookSigned-off-by:
-
Marcelo Diop-Gonzalez authored
This fixes some checkpatch warnings about incorrect indentation levels Signed-off-by:
-
Marcelo Diop-Gonzalez authored
there are extra parentheses around many conditional statements that make things a little harder to read Signed-off-by:
-
Marcelo Diop-Gonzalez authored
vchiq_get_service_fourcc() doesn't seem to be used anywhere Signed-off-by:
-
- 11 Feb, 2020 2 commits
-
-
Gustavo A. R. Silva authored
The current codebase makes use of the zero-length array language extension to the C90 standard, but the preferred mechanism to declare variable-length types such as these ones is a flexible array member[1][2], introduced in C99: struct foo { int stuff; struct boo array[]; }; By making use of the mechanism above, we will get a compiler warning in case the flexible array does not occur last in the structure, which will help us prevent some kind of undefined behavior bugs from being inadvertenly introduced[3] to the codebase from now on. This issue was found with the help of Coccinelle. [1] https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html [2] https://github.com/KSPP/linux/issues/21 [3] commit 76497732 ("cxgb3/l2t: Fix undefined behaviour") Signed-off-by:Gustavo A. R. Silva <gustavo@embeddedor.com> Link: https://lore.kernel.org/r/20200211211219.GA673@embeddedorSigned-off-by:
-
Gustavo A. R. Silva authored
The current codebase makes use of the zero-length array language extension to the C90 standard, but the preferred mechanism to declare variable-length types such as these ones is a flexible array member[1][2], introduced in C99: struct foo { int stuff; struct boo array[]; }; By making use of the mechanism above, we will get a compiler warning in case the flexible array does not occur last in the structure, which will help us prevent some kind of undefined behavior bugs from being inadvertenly introduced[3] to the codebase from now on. This issue was found with the help of Coccinelle. [1] https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html [2] https://github.com/KSPP/linux/issues/21 [3] commit 76497732 ("cxgb3/l2t: Fix undefined behaviour") Signed-off-by:
-
