- 30 Apr, 2012 27 commits
-
-
H Hartley Sweeten authored
Move the module_init/module_exit routines and the associated struct comedi_driver and other variables to the end of the source. This is more typical of how other drivers are written and removes the need for the forward declarations. Signed-off-by:
H Hartley Sweeten <hsweeten@visionengravers.com> Cc: Ian Abbott <abbotti@mev.co.uk> Cc: Mori Hess <fmhess@users.sourceforge.net> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
H Hartley Sweeten authored
Move the module_init/module_exit routines and the associated struct comedi_driver and other variables to the end of the source. This is more typical of how other drivers are written and removes the need for the forward declarations. Signed-off-by:
-
H Hartley Sweeten authored
Move the module_init/module_exit routines and the associated struct comedi_driver and other variables to the end of the source. This is more typical of how other drivers are written and removes the need for the forward declarations. Signed-off-by:
-
H Hartley Sweeten authored
Move the module_init/module_exit routines and the associated struct comedi_driver and other variables to the end of the source. This is more typical of how other drivers are written and removes the need for the forward declarations. Signed-off-by:
-
H Hartley Sweeten authored
Move the module_init/module_exit routines and the associated struct comedi_driver and other variables to the end of the source. This is more typical of how other drivers are written and removes the need for the forward declarations. Signed-off-by:
-
H Hartley Sweeten authored
Move the module_init/module_exit routines and the associated struct comedi_driver and other variables to the end of the source. This is more typical of how other drivers are written and removes the need for the forward declarations. Signed-off-by:
-
H Hartley Sweeten authored
Move the module_init/module_exit routines and the associated struct comedi_driver and other variables to the end of the source. This is more typical of how other drivers are written and removes the need for the forward declarations. Signed-off-by:
-
H Hartley Sweeten authored
Move the module_init/module_exit routines and the associated struct comedi_driver and other variables to the end of the source. This is more typical of how other drivers are written and removes the need for the forward declarations. Signed-off-by:
-
H Hartley Sweeten authored
Move the module_init/module_exit routines and the associated struct comedi_driver and other variables to the end of the source. This is more typical of how other drivers are written and removes the need for the forward declarations. Signed-off-by:
-
H Hartley Sweeten authored
Move the module_init/module_exit routines and the associated struct comedi_driver and other variables to the end of the source. This is more typical of how other drivers are written and removes the need for the forward declarations. Signed-off-by:
-
H Hartley Sweeten authored
Move the module_init/module_exit routines and the associated struct comedi_driver and other variables to the end of the source. This is more typical of how other drivers are written and removes the need for the forward declarations. Signed-off-by:
-
H Hartley Sweeten authored
This helper function is used to fetch the comedi_device board_ptr which is used during the attach to pass board specific information to the comedi drivers. Signed-off-by:
-
Kim, Milo authored
(Life cycle of timed output device driver) 1) register the device as the timed output 2) enable() ops is called via the sysfs timeout > 0 : timer is activated and device is turned on timeout = 0 : timer is cancelled and device is off 3) unregister the timed output device if not used any more So the registered device should be disabled explicitly when the module is removed. ('disabled' means the timer is stopped and the device is turned off) Rather than implementing that code in each driver, just call enable() with timeout = 0 to clean up the driver. Signed-off-by:Milo(Woogyom) Kim <milo.kim@ti.com> Cc: Mike Lockwood <lockwood@android.com> Signed-off-by:
-
Javier M. Mellid authored
This patch changes the name of function cfb_blank to smtc_blank. This function is not implemented like a generic function for frame buffer. Having the old prefix becomes confused when reading fb_ops structs. Tested with SM712 Signed-off-by:
Javier M. Mellid <jmunhoz@igalia.com> Signed-off-by:
-
Javier M. Mellid authored
This patch removes non used version support. Code won't show version message almost 4 years old. Tested with SM712 Signed-off-by:
-
Javier M. Mellid authored
With this patch smtcfb_info becomes the main structure to reach/handle state. fb_info struct links this struct via its private data field. This change improves encapsulation in functions. It reduces the number of arguments used in signatures too. Tested with SM712 Signed-off-by:
-
Javier M. Mellid authored
This patch makes happy checkpatch script. It uses dynamic debug support to show info and errors. It unifies the way to report messages in the same way that debug messages. Tested with SM712 Signed-off-by:
-
Javier M. Mellid authored
This patch uses dynamic debug support. Tested with SM712 Signed-off-by:
-
Javier M. Mellid authored
This patch remove dead code. Tested with SM712. Signed-off-by:
-
Javier M. Mellid authored
This patch removes obsolete references to previous code and non updated comments. Tested with SM712 Signed-off-by:
-
Lars-Peter Clausen authored
Add the new out-of-staging IIO directory to the IIO MAINTAINERS file entry. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Acked-by:
Jonathan Cameron <jic23@kernel.org> Signed-off-by:
-
Michael Hennerich authored
There is currently no user, but we might need it in future. So better add it now, before we have to convert drivers afterwards. Signed-off-by:
Michael Hennerich <michael.hennerich@analog.com> Acked-by:
-
Michael Hennerich authored
Signed-off-by:
-
Michael Hennerich authored
Signed-off-by:
-
Michael Hennerich authored
Generalize naming to allow other frequency synthesis techniques as well. No functional changes. Signed-off-by:
-
Lars-Peter Clausen authored
Currently we use two different naming schemes in the IIO API, iio_verb_object and iio_object_verb. E.g iio_device_register and iio_allocate_device. This patches renames instances of the later to the former. The patch also renames allocate to alloc as this seems to be the preferred form throughout the kernel. In particular the following renames are performed by the patch: iio_put_device -> iio_device_put iio_allocate_device -> iio_device_alloc iio_free_device -> iio_device_free iio_get_trigger -> iio_trigger_get iio_put_trigger -> iio_trigger_put iio_allocate_trigger -> iio_trigger_alloc iio_free_trigger -> iio_trigger_free The conversion was done with the following coccinelle patch with manual fixes to comments and documentation. <smpl> @@ @@ -iio_put_device +iio_device_put @@ @@ -iio_allocate_device +iio_device_alloc @@ @@ -iio_free_device +iio_device_free @@ @@ -iio_get_trigger +iio_trigger_get @@ @@ -iio_put_trigger +iio_trigger_put @@ @@ -iio_allocate_trigger +iio_trigger_alloc @@ @@ -iio_free_trigger +iio_trigger_free </smpl> Signed-off-by:
-
Roland Stigge authored
Previously, the touchscreen and ADC drivers of the LPC32xx SoC had a Kconfig conflict declared because they use the same hardware. Upon the introduction of device tree support in both drivers, the conflict must be removed to enable the same kernel to support different hardware (configured via the device tree). Signed-off-by:
Roland Stigge <stigge@antcom.de> Acked-by:
-
- 26 Apr, 2012 2 commits
-
-
Greg Kroah-Hartman authored
This moves the VME core, VME board drivers, and VME bridge drivers out of the drivers/staging/vme/ area to drivers/vme/. The VME device drivers have not moved out yet due to some API questions they are still working through, that should happen soon, hopefully. Cc: Martyn Welch <martyn.welch@ge.com> Cc: Manohar Vanga <manohar.vanga@cern.ch> Cc: Vincent Bossier <vincent.bossier@gmail.com> Cc: "Emilio G. Cota" <cota@braap.org> Signed-off-by: -
Rupesh Gujare authored
Signed-off-by:
Rupesh Gujare <rgujare@ozmodevices.com> Signed-off-by:
Chris Kelly <ckelly@ozmodevices.com> Signed-off-by:
-
- 25 Apr, 2012 11 commits
-
-
Greg Kroah-Hartman authored
Fix up some broken printk strings that were spanning multiple lines, making it hard to search for them. Cc: Manohar Vanga <manohar.vanga@cern.ch> Cc: Martyn Welch <martyn.welch@ge.com> Cc: "Emilio G. Cota" <cota@braap.org> Cc: Dan Carpenter <error27@gmail.com> Signed-off-by: -
Jonathan Cameron authored
This file contains only the most generic elements. Other class specific and device specific ABI documents will follow over time. Signed-off-by:
-
Jonathan Cameron authored
Take the core support + the kfifo buffer implentation out of staging. Whilst we are far from done in improving this subsystem it is now at a stage where the userspae interfaces (provided by the core) can be considered stable. Drivers will follow over a longer time scale. Signed-off-by:
-
Jonathan Cameron authored
Step 1 in moving the IIO core out of staging. Signed-off-by:
-
Jonathan Cameron authored
Just a couple of things I came across whilst reviewing this file for moving out of staging. I doubt anyone cares, but seemed sensible to fix them now! Signed-off-by:
-
Jonathan Cameron authored
These two attributes are only used in the one driver. Whilst they are fairly general I'm not entirely happy committing to them at this stage. Signed-off-by:
-
Masanari Iida authored
Correct spelling in comments withon staging/ozwpan Signed-off-by:
Masanari Iida <standby24x7@gmail.com> Acked-by:
-
Minchan Kim authored
MM code always uses PageXXX to handle page flags. Let's keep the consistency. Signed-off-by:
Minchan Kim <minchan@kernel.org> Acked-by:
Nitin Gupta <ngupta@vflare.org> Signed-off-by:
-
Lars-Peter Clausen authored
There is one device supported by the driver which is not listed in the Kconfig help test. This patch adds it. Also we are past the point were we can possible fit all devices supported by the driver in the Kconfig entry title, so just list the initial device that was supported by this driver and note that similar devices are supported as well. Signed-off-by:
-
Lars-Peter Clausen authored
The AD5662 is compatible to the AD5660, but uses an external reference instead of an internal. Signed-off-by:
-
Lars-Peter Clausen authored
We can not read back the value from the device, but we cache the value anyway so we might as well return the cached value instead of an error. Signed-off-by:
-
