- 14 May, 2012 23 commits
-
-
Lars-Peter Clausen authored
iio_device_free has to be called regardless of whether the device has been registered or not when freeing it. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Acked-by:
Jonathan Cameron <jic23@kernel.org> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Maxime Ripard authored
Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by:
Nicolas Ferre <nicolas.ferre@atmel.com> Acked-by:
Arnd Bergmann <arnd@arndb.de> Signed-off-by:
-
Maxime Ripard authored
Signed-off-by:
-
Maxime Ripard authored
Signed-off-by:
-
Maxime Ripard authored
Signed-off-by:
-
Maxime Ripard authored
Signed-off-by:
-
Maxime Ripard authored
This patch adds platform data for the AT91 ADC driver support for the AT91SAM9M10G45-EK board. Signed-off-by:
-
Maxime Ripard authored
This patch adds platform data for the AT91 ADC driver support for the AT91SAM9G20-EK board. Signed-off-by:
-
Maxime Ripard authored
Add the ADC driver for Atmel's AT91SAM9G20-EK, AT91SAM9M10G45-EK and AT91SAM9X5 family boards. It has support for both software and hardware triggers. Signed-off-by:
-
Maxime Ripard authored
The AT91 SoCs often embeds an ADC. This patch adds the needed platform data to specify the informations required by the driver to work properly. For now, we only need the reference voltage and which channels are available on the board. Signed-off-by:
-
Michael Hennerich authored
Changes since V1: Apply review feedback: Introduce and use IIO_CHAN_INFO_HARDWAREGAIN Introduce and use Use IIO_VAL_INT_PLUS_MICRO_DB Modify out of staging include paths. Convert to new iio core API naming. Changes since V2: more sanity checking in write_raw Signed-off-by:
Michael Hennerich <michael.hennerich@analog.com> Acked-by:
-
Michael Hennerich authored
Signed-off-by:
-
Michael Hennerich authored
Signed-off-by:
-
Dan Magenheimer authored
RAMster does many zcache-like things. In order to avoid major merge conflicts at 3.4, ramster used lzo1x directly for compression and retained a local copy of xvmalloc, while zcache moved to the new zsmalloc allocator and the crypto API. This patch moves ramster forward to use zsmalloc and crypto. Signed-off-by:
Dan Magenheimer <dan.magenheimer@oracle.com> Signed-off-by:
-
Johannes Thumshirn authored
Kill unused debugging macro CHECKPOINT Signed-off-by:
Johannes Thumshirn <morbidrsa@googlemail.com> Signed-off-by:
-
H Hartley Sweeten authored
Currently the sysfs device attributes are created by the comedi core after each comedi device is created. This can lead to a race condition where userspace gets an add event before the files are created. Register the device attributes with the comedi class so that the driver core handles creating them and we avoid the race. 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:
-
Anton Vorontsov authored
A corresponding function to persistent_ram_new(). Signed-off-by:
Anton Vorontsov <anton.vorontsov@linaro.org> Signed-off-by:
-
Anton Vorontsov authored
This includes devices' memory (e.g. framebuffers or memory mapped EEPROMs on a local bus), as well as the normal RAM that we don't use for the main memory. For the normal (but unused) ram we could use kmaps, but this assumes highmem support, so we don't bother and just use the memory via ioremap. As a side effect, the following hack is possible: when used together with pstore_ram (new ramoops) module, we can limit the normal RAM region with mem= and then point ramoops to use the rest of the memory, e.g. mem=128M ramoops.mem_address=0x8000000 Sure, we could just reserve the region with memblock_reserve() early in the arch/ code, and then register a pstore_ram platform device pointing to the reserved region. It's still a viable option if platform wants to do so. Also, we might want to use IO accessors in case of a real device, but for now we don't bother (the old ramoops wasn't using it either, so at least we don't make things worse). Signed-off-by:
-
Anton Vorontsov authored
Factor out vmap logic out of persistent_ram_buffer_map(), this will make the code a bit more understandable when we'll add support for non-bootmem memory. Signed-off-by:
-
Anton Vorontsov authored
The routine just creates a persistent ram zone at a specified address. For persistent_ram_init_ringbuffer() we'd need to add a 'struct persistent_ram' to the global list, and associate it with a device. We don't need all this complexity in pstore_ram, so we introduce the simple function. Signed-off-by:
-
Anton Vorontsov authored
Factor post init logic out of __persistent_ram_init(), we'll need it for the new persistent_ram_new() routine. Signed-off-by:
-
Anton Vorontsov authored
This is a longstanding bug, almost unnoticeable when calling persistent_ram_write() for small buffers. But when called for large data buffers, the write routine behaves incorrectly, as the size may never update: instead of clamping the size to the maximum buffer size, buffer_size_add_clamp() returns an error (which is never checked by the write routine, btw). To fix this, we now use buffer_size_add() that actually clamps the size to the max value. Also remove buffer_size_add_clamp(), it is no longer needed. Signed-off-by:
Colin Cross <ccross@android.com> Cc: stable <stable@vger.kernel.org> Signed-off-by:
-
Anton Vorontsov authored
The 'node' struct member is unused, so remove it. Signed-off-by:
-
- 10 May, 2012 17 commits
-
-
Tim Bird authored
Fix a few sparse warnings, and improve whitespace. Cc: Brian Swetland <swetland@google.com> Signed-off-by:
Tim Bird <tim.bird@am.sony.com> Signed-off-by:
-
Tim Bird authored
This changes the log initialization to be dynamic, but still at boot time. These changes are a predecessor to implementing runtime allocation and freeing of logs, to make the Android logger less hard-coded. Change from a fixed set of static log structures, to allocation at init time into a list. Return proper error numbers on log allocation failure. Cc: Brian Swetland <swetland@google.com> Signed-off-by:
-
Paul Gortmaker authored
This driver had headers like big_endian.h, little_endian.h, swab.h and yet we can throw them all in the trash can and the thing still builds on x86-64 and ppc, just by deleting the references to the deleted files. Cc: Larry Finger <Larry.Finger@lwfinger.net> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by:Paul Gortmaker <paul.gortmaker@windriver.com>
-
Paul Gortmaker authored
This driver should not be carrying around ancient copies of headers like <linux/ip.h> for its own use. Mapping it onto the mainline one uncovers no build issues. Cc: Larry Finger <Larry.Finger@lwfinger.net> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: -
Paul Gortmaker authored
This driver should not be carrying around ancient copies of headers like <linux/if_ether.h> for its own use. Mapping it onto the mainline one uncovers no build issues. Cc: Larry Finger <Larry.Finger@lwfinger.net> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: -
Oleksij Rempel authored
Signed-off-by:
Oleksij Rempel <bug-track@fisher-privat.net> Acked-by:
Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
-
Oleksij Rempel authored
the SENSE_TYPE_FORMAT_IN_PROGRESS was checked by rts51x_scsi.c but never set. Signed-off-by:
-
Oleksij Rempel authored
Signed-off-by:
-
Oleksij Rempel authored
Signed-off-by:
-
Oleksij Rempel authored
Signed-off-by:
-
Oleksij Rempel authored
Signed-off-by:
-
Oleksij Rempel authored
Signed-off-by:
-
Oleksij Rempel authored
module parametr needs_remote_wakeup sets option->needs_remote_wakeup and rts51x->pusb_intf->needs_remote_wakeup the second may be used, the first one is never used Signed-off-by:
-
Oleksij Rempel authored
Signed-off-by:
-
Oleksij Rempel authored
Signed-off-by:
-
Oleksij Rempel authored
Signed-off-by:
-
Oleksij Rempel authored
Signed-off-by:
-
