- 23 Oct, 2011 12 commits
-
-
Mark Einon authored
Sharing a common structure by moving common structure items into fbr_lookup. TODO - Currently will not work if USE_FBR0 = 0 as FBR1 uses fbr[1] which is removed in this case Signed-off-by:
Mark Einon <mark.einon@gmail.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Mark Einon authored
Two helper functions for adding 10bit/12bit umbers with wrapping are defined in the header. Moved them to the driver .c file. Signed-off-by:
-
Mark Einon authored
Driver now resides in a single file with a separate header with registers, updated the README TODO list. Signed-off-by:
-
Mark Einon authored
Move et1310_tx.h contents into et131x.c and delete et1310_tx.h Signed-off-by:
-
Mark Einon authored
Move et1310_rx.h contents into et131x.c and delete et1310_rx.h Signed-off-by:
-
Mark Einon authored
Move et131x_defs.h contents into et131x.c and delete et131x_defs.h Signed-off-by:
-
Mark Einon authored
Move et131x_adapter.h contents into et131x.c and delete et131x_adapter.h Signed-off-by:
-
Mark Einon authored
Move et1310_phy.h register defines into et131x.h and delete et1310_phy.h Signed-off-by:
-
Mark Einon authored
Move et1310_address_map.h register defines into et131x.h and delete et1310_address_map.h Signed-off-by:
-
Mark Einon authored
Header file should only have register defines, moved non-register defines to et131x.c Signed-off-by:
-
Mark Einon authored
The function declarations in et131x.h are no longer used now all functions are in one file. Removed declarations from et131x.h and added any required forward declarations to et131x.c. Signed-off-by:
-
Mark Einon authored
Created one big .c file for the driver, moving the contents of all driver .c files into it. Signed-off-by:
-
- 19 Oct, 2011 11 commits
-
-
Lars-Peter Clausen authored
Currently it is possible to write negative values to the ad5686's raw attribute. This will cause undefined behaviour, so reject negative values. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Acked-by:
Jonathan Cameron <jic23@cam.ac.uk> Signed-off-by:
-
Lars-Peter Clausen authored
Scale is currently reported in volts instead of millivolts. This patch fixes it. Signed-off-by:
-
Lars-Peter Clausen authored
Add the missing "voltage" chan_type to the powerdown attributes. Signed-off-by:
-
Lars-Peter Clausen authored
The ad5791 currently assumes that the negative and positive supply have the same absolute value, which is not necessarily true. This patch introduces a offset attribute which will contain the negative supply voltage scaled according to the iio spec. The raw attribute now accepts values in the range of 0 to max instead of -max/2 to max/2. While we are at it also fix the vref span calculation. Since both positive and negative reference voltages are specificed as absolute values we need to add them and not subtract them to get the reference voltage span. Signed-off-by:
-
Lars-Peter Clausen authored
Commit c5b99396 ("staging:iio:dac:ad5791 chan spec conversion.") introduced a small bug, using storagebits instead of realbits throughout the driver, which causes the driver to work incorrectly. This patch fixes it. Signed-off-by:
-
Michael Hennerich authored
Signed-off-by:
Michael Hennerich <michael.hennerich@analog.com> Acked-by:
-
Michael Hennerich authored
No functional changes. Fix Kconfig description. Signed-off-by:
-
Michael Hennerich authored
Signed-off-by:
-
Lars-Peter Clausen authored
This patch adds support for the Analog Devices AD6064, AD6064-1, AD6044, AD6024 quad channel digital-to-analog converter devices. Signed-off-by:
-
Vladimir Zapolskiy authored
According to OMAP3 TRM access to MMU registers shall be strictly 32-bit aligned. Signed-off-by:
Vladimir Zapolskiy <vz@mleia.com> Acked-by:
Omar Ramirez Luna <omar.ramirez@ti.com> Signed-off-by:
-
Dan Carpenter authored
The original code left it up to the user to decide how much data to copy, but that doesn't work with a fixed size array. Signed-off-by:
Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
-
- 18 Oct, 2011 3 commits
-
-
Greg Kroah-Hartman authored
There's a lot of unused and unneeded things in this makefile, so delete it all. Reported-by:
Grant Likely <grant.likely@secretlab.ca> Signed-off-by:
-
Greg Kroah-Hartman authored
There's a lot of unused and unneeded things in this makefile, so delete it all. Reported-by:
-
Greg Kroah-Hartman authored
There's a lot of unused and unneeded things in this makefile, so delete it all. Reported-by:
-
- 17 Oct, 2011 14 commits
-
-
Oren Weil authored
1) We move the AMT Watchdog to use the kernel watchdog core. the new code is still part of the MEI driver. we didn't find any good reason to extract the the MEI driver watchdog code from the MEI Driver to a new module. 2) Since the watchdog remains in the mei driver, exposing in-kernel API just for AMTHI is unnecessary. MEI new Watchdog Core Interface Patches set: https://lkml.org/lkml/2011/9/7/26 3) Code cleanup (init and probe, bug_on usage, headers and etc) was submitted in previous patches. Patches: https://lkml.org/lkml/2011/9/21/231 https://lkml.org/lkml/2011/6/15/358 https://lkml.org/lkml/2011/7/7/177 https://lkml.org/lkml/2011/9/7/38 https://lkml.org/lkml/2011/9/7/37 https://lkml.org/lkml/2011/9/7/28 4) mei.txt was updated with additional information. Patch: https://lkml.org/lkml/2011/10/16/52Acked-by:
Tomas Winkler <tomas.winkler@intel.com> Signed-off-by:
Oren Weil <oren.jer.weil@intel.com> Signed-off-by:
-
Manohar Vanga authored
Signed-off-by:
Manohar Vanga <manohar.vanga@cern.ch> Cc: Martyn Welch <martyn.welch@ge.com> Reviewed-by:
Emilio G. Cota <cota@braap.org> Signed-off-by:
-
Manohar Vanga authored
Previously, the device-driver matching mechanism depended on the vme_device_id structure due to the need for a bind table per driver. This method of matching is no longer used so this patch merges the fields of struct vme_device_id into struct vme_dev. Since this also renders the slot field meaningless, it has also been removed in this patch. Signed-off-by:
-
Manohar Vanga authored
For jumper based boards (non VME64x), there is no mechanism for detecting the card that is plugged into a specific slot. This leads to issues in non-autodiscovery crates/cards when a card is plugged into a slot that is "claimed" by a different driver. In reality, there is no problem, but the driver rejects such a configuration due to its dependence on the concept of slots. This patch makes the concept of slots less critical and pushes the driver match() to individual drivers (similar to what happens in the ISA bus in driver/base/isa.c). This allows drivers to register the number of devices that they expect without any restrictions. Devices in this new model are now formatted as $driver_name-$bus_id.$device_id (as compared to the earlier vme-$bus_id.$slot_number). This model also makes the device model more logical as devices are only registered when they actually exist whereas earlier, a set of devices were being created automatically regardless of them actually being there. Another change introduced in this patch is that devices are now created within the VME driver structure rather than in the VME bridge structure. This way, things don't go haywire if the bridge driver is removed while a driver is using it. Signed-off-by:
-
Manohar Vanga authored
Instead of using a vanilla 'struct device' for VME devices, add new 'struct vme_dev'. Modifications have been made to the VME framework API as well as all in-tree VME drivers. The new vme_dev structure has the following advantages from the current model used by the driver: * Driver functions (probe, remove) now receive a VME device instead of a pointer to the bridge device (cleaner design) * It's easier to differenciate API calls as bridge-based or device-based (ie. cleaner interface). Signed-off-by: -
Jonathan Cameron authored
Very simple buffered reading. Did not provide a trigger as the sysfs trigger already meets that requirement. Signed-off-by:
-
Jonathan Cameron authored
The event generator is not very pretty but does the job and allows this driver to look a lot more like a normal driver than it otherwise would. Signed-off-by:
-
Jonathan Cameron authored
The documenation explaining how to go about writing a driver is lagging horribly, so here is another approach; an actual driver with lots of explanatory comments. Note it is currently minimal in that there are no events and no buffer. With care they can probably be added in additional files without messing up the clarity of what we have here. V2: Addressed some of Manuel Stahl's feedback. Fixed up kernel doc. Added more general description. Signed-off-by:
-
Jonathan Cameron authored
Longs are not known for being 8 bits. Signed-off-by:
-
Jonathan Cameron authored
Fix a dumb lack of consideration of the effect of combining the iio_device_unregister and iio_free_device calls into one. There is no valid place to free some of the sysfs array elements. Signed-off-by:
-
Michael Hennerich authored
Signed-off-by:
-
Jonathan Cameron authored
Numerous drivers either had pointless includes of gpio.h or should have been dependent on GENERIC_GPIO and were not. Conversion of ads1210 to use array registration triggered build failures that highlighted all was not well. Signed-off-by:
Randy Dunlap <rdunlap@xenotime.net> Acked-by:
-
K. Y. Srinivasan authored
Fix checkpatch warnings. Signed-off-by:
K. Y. Srinivasan <kys@microsoft.com> Signed-off-by:
-
K. Y. Srinivasan authored
Fix a checkpatch warning. Signed-off-by:
-
