- 16 Mar, 2013 5 commits
-
-
Naveen Krishna Chatradhi authored
This patch adds New driver to support: 1. Supports ADC IF found on EXYNOS4412/EXYNOS5250 and future SoCs from Samsung 2. Add ADC driver under iio/adc framework 3. Also adds the Documentation for device tree bindings Signed-off-by:
Naveen Krishna Chatradhi <ch.naveen@samsung.com> Reviewed-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
Jonathan Cameron <jic23@kernel.org>
-
Denis Ciocca authored
Use the new spi_sync_transfer() helper function instead of open-coding it. Signed-off-by:
Denis Ciocca <denis.ciocca@st.com> Signed-off-by:
-
Christophe Leroy authored
This patch adds support for Analog Devices AD7923 ADC in the IIO Subsystem. Signed-off-by:
Patrick Vasseur <patrick.vasseur@c-s.fr> Signed-off-by:
Christophe Leroy <christophe.leroy@c-s.fr> Reviewed-by:
-
Guenter Roeck authored
Provide bindings and parse OF data during initialization. Signed-off-by:
Guenter Roeck <linux@roeck-us.net> Reviewed-by:
-
Lars-Peter Clausen authored
The adt7410 hwmon driver is feature wise more or less on par with the IIO driver. So we can finally remove the IIO driver. Signed-off-by:
-
- 15 Mar, 2013 35 commits
-
-
Ian Abbott authored
`labpc_common_detach()` calls `comedi_pci_disable()` unconditionally. That's okay for PCI devices and harmless for ISA devices (as the `hw_dev` member will be NULL so `comedi_to_pci_dev()` will return NULL and `comedi_pci_disable()` checks for that), but it is disastrous for PCMCIA devices. Those are managed by the "ni_labpc_cs" module but it calls this `labpc_common_detach()` and the `hw_dev` member will be pointing to the `struct device` embedded in a `struct pcmcia_device` in that case. That's enough to confuse `comedi_pci_disable()` into thinking it's a valid PCI device to be disabled. Use the private board information (`thisboard`) to make sure it is a PCI device before calling `comedi_pci_disable()`. Signed-off-by:
Ian Abbott <abbotti@mev.co.uk> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Ian Abbott authored
Some PCI drivers use the "spare" `iobase` member of `struct comedi_device` as a flag to indicate that the call to `comedi_pci_enable()` was successful. This is no longer necessary now that `comedi_pci_enable()` and `comedi_pci_disable()` use the `ioenabled` member of `struct comedi_device` themselves to keep track of what needs to be done. Remove the unnecessary assignments to the `iobase` member in the relevant drivers. Signed-off-by:
-
Ian Abbott authored
Add 1-bit bit-field member `ioenabled` of type `bool` to `struct comedi_device`. Use this to keep track of whether a PCI device and its BARs have been successfully enabled by `comedi_pci_enable()`. This avoids overloading the meaning of the `iobase` member which is used by several drivers to hold the base port I/O address of a board's "main" registers. Other drivers using MMIO use `iobase` as a flag to indicate that the preceding call to `comedi_pci_enable()` was successful. They no longer need to do that. The name `ioenabled` is intended to be PCI-agnostic so it can be used for similar purposes by non-PCI drivers. Signed-off-by:
-
Ian Abbott authored
Change the `in_request_module` member of `struct comedi_device` to a 1-bit bit-field of type `bool` and move it into a suitable hole in the data type to save a few bytes. Change the assigned values to `true` and `false`. Signed-off-by:
-
Ian Abbott authored
Change the `attached` member of `struct comedi_device` to a 1-bit bit-field of type `bool`. Change assigned values to `true` and `false` and replace or remove comparison operations with simple boolean tests. We'll put some extra bit-fields in the gap later to save space. Signed-off-by:
-
Ian Abbott authored
Florent Boudet reports success using a NI PXI-6624 board with a trivially modified version of the "ni_660x" driver (addition to the PCI device ID table and comedi board table). He did this with the out-of-tree Comedi drivers at www.comedi.org, but it applies equally to the in-tree "staging" drivers. He reports the PXI-6624 is basically the same as the PXI-6602, but with isolated channels and external voltage source. Add support for NI PXI-6224 to the "ni_660x" driver. (Maybe the driver should be renamed to "ni_66xx"?) Signed-off-by:
-
Ian Abbott authored
Convert to preferred block comment style. Signed-off-by:
-
Ian Abbott authored
Back in the old days (before "staging") when Comedi only supported manual configuration of devices, the "adv_pci_dio" driver supported both PCI-1753 ("pci1753") and PCI-1753E ("pci1753e"). In actual fact, "pci1753e" is just a PCI-1753 connected by a ribbon cable to a PCI-1753E expansion card, which is plugged into a PCI slot but is not a PCI device itself. Now that the "adv_pci_dio" driver only supports automatic configuration of devices and the main "comedi" module no longer allows auto-configuration to be disabled, a PCI-1753 with a PCI-1753E expansion card is always treated as an unexpanded PCI-1753 ("pci1753") and there is no way to override it. (Recently, an undefined macro `USE_PCI1753E_BOARDINFO` was used to make the driver switch to supporting "pci1753e" instead of "pci1753", but this is less than ideal.) Advantech has their own Linux (non-Comedi) driver for the PCI-1753 which detects whether the PCI-1753E expansion card is connected to the PCI-1753 by fiddling with a register at offset 53 from the main registers base. Use Advantech's test in our "adv_pci_dio" driver. If the board appears to be a PCI-1753 ("pci1753"), check if the expansion card appears to be present, and if so, treat the device as a PCI-1753 plus PCI-1753E expansion card ("pci1753e"). Also, get rid of `enum dio_boardid` (`BOARD_...` enum values) which was added recently and just use the older `TYPE_...` enum values from `enum hw_cards_id` instead as the mapping is now 1-to-1. Signed-off-by: -
H Hartley Sweeten authored
Fix a build error due to a missing ';' at the end of a line. Signed-off-by:
H Hartley Sweeten <hsweeten@visionengravers.com> Reported-by:
Geert Uytterhoeven <geert.uytterhoeven@gmail.com> Cc: Kumar Amit Mehta <gmate.amit@gmail.com> Signed-off-by:
-
Dan Carpenter authored
dwc2_hcd_release() calls dwc2_hcd_free() which frees ->core_params and sets it to NULL. Signed-off-by:
Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
-
Wei Yongjun authored
'lli_array_ptr' etc. are malloced in sep_prepare_input_dma_table() and should be freed before leaving from the error handling case, otherwise it will cause memory leak. Signed-off-by:
Wei Yongjun <yongjun_wei@trendmicro.com.cn> Signed-off-by:
-
Eduardo Valentin authored
Document the helper to validate a struct omap_bandgap and a sensor id. Signed-off-by:
Eduardo Valentin <eduardo.valentin@ti.com> Signed-off-by:
-
Eduardo Valentin authored
Not all APIs exposed today are used. However all unused APIs will be required once the thermal layer allows IRQ based policies. Signed-off-by:
-
Eduardo Valentin authored
It is hard to use regmap because benefit of using regmap cache may not be applicable as there is a specific sequence to restore the bandgap context. Signed-off-by:
-
Eduardo Valentin authored
Because there is a need to lock inside IRQ handler, this patch changes the locking mechanism inside the omap-bandgap.[c,h] to spinlocks. Now this lock is used to protect omap_bandgap struct during APIs exposed (possibly used in sysfs handling functions) and inside the ALERT IRQ handler. Because there are registers shared among the sensors, this lock is global, not per sensor. Signed-off-by:
-
Eduardo Valentin authored
Add myself as maintainer of the TI bandgap and thermal driver. CC: Santosh Shilimkar <santosh.shilimkar@ti.com> CC: Zhang Rui <rui.zhang@intel.com> Signed-off-by:
-
Eduardo Valentin authored
Now arch code has to specify CONFIG_ARCH_HAS_BANDGAP. So, this driver will be selectable only if the platform reports itself as having a bandgap device. Any OMAP variant or any other OMAP version needs to select ARCH_HAS_BANDGAP so that the driver will be applicable. A part from that it is required to device the data structures that maps the registers and their bitfields. The DT compatible list must also be updated. CC: Santosh Shilimkar <santosh.shilimkar@ti.com> CC: Vaibhav Bedia <vaibhav.bedia@ti.com> Signed-off-by:
-
Eduardo Valentin authored
Document function to build omap_bandgap structure Signed-off-by:
-
Eduardo Valentin authored
Document function that sets talert handling up. Signed-off-by:
-
Eduardo Valentin authored
Add documentation for the function to setup TSHUT handling Signed-off-by:
-
Eduardo Valentin authored
Add documentation of the function for reading alert thresholds Signed-off-by:
-
Eduardo Valentin authored
Document function to update alert thresholds. Signed-off-by:
-
Eduardo Valentin authored
Document function to program alert thresholds Signed-off-by:
-
Eduardo Valentin authored
Document function to initialize the conversion state machine. Signed-off-by:
-
Eduardo Valentin authored
Simple update on function documentation. Signed-off-by:
-
Eduardo Valentin authored
This patch names 'enable_continuous_mode' accordingly to the file standard naming. Signed-off-by:
-
Eduardo Valentin authored
Section with platform device callbacks Signed-off-by:
-
Eduardo Valentin authored
Section of helper functions to initilize the bandgap device Signed-off-by:
-
Eduardo Valentin authored
This patch improves the code that handles threshold values by creating single functions that are usable for tcold and thot. This way we won't have duplicated functionality just because it is handling different bitfields. Now the added functions are reused in several places where it is needed to update any threshold. This patch also removes macros that are used only inside the _validate helper function. In this patch there is also an addition of an extra function section for Exposed APIs, used outside the omap-bandgap.c, but inside the omap-thermal driver. Signed-off-by:
-
Eduardo Valentin authored
Proper document the function to configure the IRQ event masks. Signed-off-by:
-
Eduardo Valentin authored
This change improves temp_sensor_unmask_interrupts by: . renaming it to omap_bandgap_unmask_interrupts . making it a void function, as there is nothing really to report an error. Signed-off-by:
-
Eduardo Valentin authored
Section of functions manipulating thresholds for Alert and Shutdown. Signed-off-by:
-
Eduardo Valentin authored
Document function to handle hysteresis. Signed-off-by:
-
Eduardo Valentin authored
This patch improves the add_hyst function by: . Renaming it to omap_bandgap_add_hyst . Moving it to the ADC conversion functions section . Changing its signature to follow the driver standard Signed-off-by:
-
Eduardo Valentin authored
Document the conversion function. Signed-off-by:
-
