- 22 Dec, 2011 24 commits
-
-
Sean MacLennan authored
Convert rtllib to use lib80211_crypt_info. Signed-off-by:
Sean MacLennan <seanm@seanm.ca> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Sean MacLennan authored
Convert rtllib_crypt_data to lib80211_crypt_data and rtllib_crypt_ops to lib80211_crypt_ops. This is almost a 1:1 replacement, only extra_prefix_len and extra_postfix_len changed. Signed-off-by:
-
Sean MacLennan authored
Add lib80211.h header file to rtllib.h and get it compiling. Signed-off-by:
-
Tomas Winkler authored
add mei_watchdog_register/unregister wrappers for cleaner encapsulation Signed-off-by:
Tomas Winkler <tomas.winkler@intel.com> Signed-off-by:
-
Rob Clark authored
Uncached/writecombine buffers need to be clean before creating uc/wc userspace mappings, lest dirty cache lines fall down and corrupt the contents of the buffer. Signed-off-by:
Rob Clark <rob@ti.com> Signed-off-by:
-
Marcos Paulo de Souza authored
This patch removes the int return of function INTnsProcessData, because nobody uses this return. Signed-off-by:
Marcos Paulo de Souza <marcos.mage@gmail.com> Signed-off-by:
-
Bart Westgeest authored
Removed remnants of old function definitions which have since been removed in earlier cleanup work. Signed-off-by:
Bart Westgeest <bart@elbrys.com> Signed-off-by:
-
Bart Westgeest authored
The usbip_xmit function supported sending and receiving data, however the sending part of the function was never used/executed. Renamed the function to usbip_recv, and removed the unused code. Signed-off-by:
-
Lars-Peter Clausen authored
These callbacks are currently used by the individual buffer implementations to ensure that the request_update callback is not issued while the buffer is in use. But the core already provides sufficient measures to prevent this from happening in the first place. So it is safe to remove them. There is one functional change due to this patch. Since the buffer is no longer marked as in use when the chrdev is opened, it is now possible to enable the buffer while it is opened. This did not work before, because mark_param_change did fail if the buffer was marked as in use. Acked-by:
Jonathan Cameron <jic23@kernel.org> Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
-
Lars-Peter Clausen authored
Right now we have a mark_param_change callback in the buffer access functions struct, which should be called whenever the parameters (length, bytes per datum) of the buffer change. But it is only called when the user changes the buffer size, not when the bytes per datum change. Additionally each buffer implementation already keeps track internally whether its parameters have changed, making the call to mark_param_change after changing the buffer length redundant. Since each buffer implementation knows best when one of its parameters has changed just make tracking of this internal and drop the mark_param_change callback. Acked-by:
-
Lars-Peter Clausen authored
Currently none of the buffer implementations implements the enable() or is_enable() nor does core code try to call these. So it is safe to remove them. Acked-by:
-
Lars-Peter Clausen authored
The flag is only cleared, never set or tested, so it is safe to remove it. Acked-by:
-
Lars-Peter Clausen authored
Our buffer implementation does not support multiple concurrent readers. So we have to ensure that a device is only opened once at a time. So do the same thing we do for the event fd and introduce a per device busy flag. The flag gets set when opening the device and gets cleared when closing the device. If a open is attempted while the busy flag is set we return -EBUSY. Acked-by:
-
Lars-Peter Clausen authored
The buffer buffer storage is only update when enabling the buffer. Changing the buffer size while the buffer is enabled will confuse the buffer in regard to its actual buffer size and can cause potential memory corruption. Thus it is only safe to modify the buffer size when the buffer is disabled. Acked-by:
-
Lars-Peter Clausen authored
Currently we only disallow changing the scan elements, while the buffer is enabled, in triggered buffer mode. This patch changes it to disallow it for all buffered modes. Disabling or enabling scan elements while the buffer is enabled will cause undefined behavior since the reader will not be able to tell samples with the new and old scan element set apart and thus wont be able to extract any meaningful data from the buffer. Acked-by:
-
Lars-Peter Clausen authored
Acked-by:
-
Marcos Paulo de Souza authored
This patch removes the return of the function CARDbSetMediaChannel, that always return TRUE value. Signed-off-by:
-
Marcos Paulo de Souza authored
This function always return TRUE, and it is not used by the funtions who calls it. Signed-off-by:
-
Lars-Peter Clausen authored
Fixes the following warning: drivers/staging/iio/industrialio-buffer.c: In function ‘iio_scan_mask_query’: drivers/staging/iio/industrialio-buffer.c:620: warning: unused variable ‘mask’ Signed-off-by:
-
Marco Navarra authored
This patch fixes some 80 chatacters limit warnings in the lowmemorykiller.c file Signed-off-by:
Marco Navarra <fromenglish@gmail.com> Signed-off-by:
-
Marco Navarra authored
This patch fixes a simple tab-space warning in binder.h found by checkpatch tool Signed-off-by:
-
Rakib Mullick authored
gma_resume_display() wants 'struct pci_dev *' as it's parameter, so lets pass dev->pdev instead of dev. Fixes the following warning. drivers/staging/gma500/power.c: In function ‘gma_power_begin’: drivers/staging/gma500/power.c:269:3: warning: passing argument 1 of ‘gma_resume_display’ from incompatible pointer type drivers/staging/gma500/power.c:99:13: note: expected ‘struct pci_dev *’ but argument is of type ‘struct drm_device *’ Signed-off-by:
Rakib Mullick <rakib.mullick@gmail.com> Signed-off-by:
-
Kevin McKinney authored
Variable IoBuffer.InputLength is chosen from userspace, and can therefore be less than the intended size. In this case,the memory from the kmalloc call is eventually cast to a PBULKWRM_BUFFER. If the IoBuffer.InputLength does not meet the minimum size of PBULKWRM_BUFFER, then we will get a kernel Oops. To resolve this issue, this patch verifies IoBuffer.InputLength meets the minimum size before invoking the kmalloc call. Signed-off-by:
Kevin McKinney <klmckinney1@gmail.com> Reviewed-by:
Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
-
Kevin McKinney authored
This ioctl, IOCTL_BCM_GET_DRIVER_VERSION, is responsible for sending the driver version to userspace. However, the requested size stored in IoBuffer.OutputLength may be incorrect. Therefore, we altered the code to send the exact length of the version, plus one for the null character. Signed-off-by:
-
- 21 Dec, 2011 8 commits
-
-
Mathieu Desnoyers authored
LTTng has been removed from the staging tree. Complete this removal by removing the LTTng entry from the MAINTAINERS file. Signed-off-by:
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> CC: Ingo Molnar <mingo@elte.hu> CC: Peter Zijlstra <peterz@infradead.org> Signed-off-by:
-
John Stultz authored
Fixes checkpatch warnings with the ashmem.c file CC: Brian Swetland <swetland@google.com> CC: Colin Cross <ccross@android.com> CC: Arve Hjønnevåg <arve@android.com> CC: Dima Zavin <dima@android.com> CC: Robert Love <rlove@google.com> Signed-off-by:
John Stultz <john.stultz@linaro.org> Signed-off-by:
-
Colin Cross authored
The arguments to shrink functions have changed, update ashmem_shrink to match. Signed-off-by:
Colin Cross <ccross@android.com> [jstultz: tweaked commit subject] CC: Brian Swetland <swetland@google.com> CC: Colin Cross <ccross@android.com> CC: Arve Hjønnevåg <arve@android.com> CC: Dima Zavin <dima@android.com> CC: Robert Love <rlove@google.com> Signed-off-by:
-
Bjorn Bringert authored
Signed-off-by:
Bjorn Bringert <bringert@android.com> [jstultz: tweaked commit subject] CC: Brian Swetland <swetland@google.com> CC: Colin Cross <ccross@android.com> CC: Arve Hjønnevåg <arve@android.com> CC: Dima Zavin <dima@android.com> CC: Robert Love <rlove@google.com> Signed-off-by:
-
Colin Cross authored
Signed-off-by:
Colin Cross <ccross@google.com> CC: Brian Swetland <swetland@google.com> CC: Colin Cross <ccross@android.com> CC: Arve Hjønnevåg <arve@android.com> CC: Dima Zavin <dima@android.com> CC: Robert Love <rlove@google.com> Signed-off-by:
-
Arve Hjønnevåg authored
Signed-off-by:
Arve Hjønnevåg <arve@android.com> CC: Brian Swetland <swetland@google.com> CC: Colin Cross <ccross@android.com> CC: Arve Hjønnevåg <arve@android.com> CC: Dima Zavin <dima@android.com> CC: Robert Love <rlove@google.com> Signed-off-by:
-
Bjorn Bringert authored
Signed-off-by:
-
Robert Love authored
The anonymous shared memory (ashmem) subsystem provides a Unix-y,file-based shared memory interface to user-space. It works like anonymous memory (e.g. mmapping fd=0) except if you share the file descriptor via the usual means, you will share the mapping. The shared memory can be accessed via both mmap or file I/O. The backing store is a simple shmem file. Additionally, ashmem introduces the concept of page pinning. Pinned pages (the default) behave like any anonymous memory. Unpinned pages are available to the kernel for eviction during VM pressure. When repinning the pages, the return value instructs user-space as to any eviction. In this manner, user-space processes may implement caching and similar resource management that efficiently integrates with kernel memory management. Signed-off-by:
Robert Love <rlove@google.com> ashmem: Don't install fault handler for private mmaps. Ashmem is used to create named private heaps. If this heap is backed by a tmpfs file it will allocate two pages for every page touched. In 2.6.27, the extra page would later be freed, but 2.6.29 does not scan anonymous pages when running without swap so the memory is not freed while the file is referenced. This change changes the behavior of private ashmem mmaps to match /dev/zero instead tmpfs. Signed-off-by:
Marco Nelissen <marcone@android.com> [jstultz: Improved commit subject and included patch description from rlove. Also moved ashmem files to staging dir, and reworked code to avoid touching mm/shmem.c while we're in staging.] CC: Brian Swetland <swetland@google.com> CC: Colin Cross <ccross@android.com> CC: Arve Hjønnevåg <arve@android.com> CC: Dima Zavin <dima@android.com> CC: Robert Love <rlove@google.com> Signed-off-by:
-
- 16 Dec, 2011 8 commits
-
-
Rebecca Schultz authored
This adds the Android pmem driver to the staging tree. [At this point in time, it is dependent on the ARM platform, due to some build issues that require it. - gregkh] Signed-off-by:
Rebecca Schultz <rschultz@google.com> Signed-off-by:
Rebecca Schultz Zavin <rebecca@android.com> Signed-off-by:
Dima Zavin <dima@android.com> Signed-off-by:
Jamie Gennis <jgennis@google.com> Cc: Brian Swetland <swetland@google.com> Cc: Arve Hjønnevåg <arve@android.com> Cc: Colin Cross <ccross@android.com> Signed-off-by:
-
Greg Kroah-Hartman authored
This fixes a number of minor space issues in the Android switch code. Signed-off-by: -
Mike Lockwood authored
This adds the Android switch driver code to the staging tree. [Note, this code was located in drivers/switch/ in the Android kernel releases, but as that api wasn't generally accepted, and the interface is working toward changing to the newly proposed extcon inteface, this driver was placed here until the extcon code is merged into mainline and the Android userspace code is converted over to using it. - gregkh] Signed-off-by:
Mike Lockwood <lockwood@android.com> Cc: MyungJoo Ham <myungjoo.ham@samsung.com> Cc: Kyungmin Park <kyungmin.park@samsung.com> Cc: Donggeun Kim <dg77.kim@samsung.com> Cc: Arnd Bergmann <arnd@arndb.de> Cc: MyungJoo Ham <myungjoo.ham@gmail.com> Cc: Linus Walleij <linus.walleij@linaro.org> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com> Cc: NeilBrown <neilb@suse.de> Cc: Morten CHRISTIANSEN <morten.christiansen@stericsson.com> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com> Cc: John Stultz <john.stultz@linaro.org> Signed-off-by:
-
Andy Gross authored
Right now just a tiler_map file to dump a 2d map of which areas in tiler/dmm have pinned buffers (or reservations). In the future more could be added. Signed-off-by:
-
Rob Clark authored
omap_gem_roll() could be called by fbcon in atomic context or when struct_mutext is held. Avoid aquiring mutex (deadlock), or calling tiler_pin() (which itself is not safe for atomic context) in these cases. Signed-off-by:
-
Rob Clark authored
Can be set at boot or module load time to prevent YWRAP scrolling from being enabled. Signed-off-by:
-
Sean MacLennan authored
The rtllib and rtllib_crypt drivers are both required for a fully functional rtllib. Make sure both are always available by having rtllib select rtllib_crypt. Reported-by:
Randy Dunlap <rdunlap@xenotime.net> Signed-off-by:
-
Jonathan Cameron authored
This field moved into the trigger_ops structure a while back, but somehow never quite got cleared up. This clears the last few drivers to set it (nothing uses it) and gets rid of it entirely. Signed-off-by:
-
