- 10 Dec, 2011 1 commit
-
-
Haiyang Zhang authored
The ring buffer is only used to pass meta data for outbound packets. The actual payload is accessed by DMA from the host. So the stop/wake queue mechanism based on counting and comparing number of pages sent v.s. number of pages in the ring buffer is wrong. Also, there is a race condition in the stop/wake queue calls, which can stop xmit queue forever. The new stop/wake queue mechanism is based on the actual bytes used by outbound packets in the ring buffer. The check for number of outstanding sends after stop queue prevents the race condition that can cause wake queue happening earlier than stop queue. Signed-off-by:
Haiyang Zhang <haiyangz@microsoft.com> Signed-off-by:
K. Y. Srinivasan <kys@microsoft.com> Reported-by:
Long Li <longli@microsoft.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
- 09 Dec, 2011 5 commits
-
-
Lars-Peter Clausen authored
The ad5790 has a binary compatible interface to ad5791, so we just have to add an entry to the drivers device table to add support for it. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
-
Ravishankar karkala Mallikarjunayya authored
This is a patch to the cb_das16_cs.c file that fixes up a initialise statics to 0 or NULL warning found by the checkpatch.pl tool. Signed-off-by:
Ravishankar Karkala Mallikarjunayya <ravishankar.km@greenturtles.in> Signed-off-by:
-
Ravishankar karkala Mallikarjunayya authored
This is a patch to the dt3000.c file that fixes up a initialise statics to 0 or NULL warning found by the checkpatch.pl tool. Signed-off-by:
-
Ravishankar karkala Mallikarjunayya authored
This is a patch to the cb_pcimdda.c file that fixes up a line over 80 character warning found by the checkpatch.pl tool. Signed-off-by:
-
Ravishankar karkala Mallikarjunayya authored
This is a patch to the daqboard2000.c file that fixes up a brace warning found by the checkpatch.pl tool. Signed-off-by:
-
- 08 Dec, 2011 34 commits
-
-
Florian Schmaus authored
This became unnecessary with the previous commit. Improved the readability of the remaining check, by using UINT_MAX. Signed-off-by:
Florian Schmaus <fschmaus@gmail.com> Signed-off-by:
-
Florian Schmaus authored
As reported by checkpatch.pl strict_strtoul should be replaced. It was replaced with kstrtouint since async->max_bufsize is an unsigned int anyway. Signed-off-by:
-
Greg Kroah-Hartman authored
The "proper" way to do this is to work with the existing in-kernel tracing subsystem and work to get the missing features that are in lttng into those subsystems. Cc: Ingo Molnar <mingo@elte.hu> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com> Signed-off-by: -
Greg Kroah-Hartman authored
Intel has asked that this driver now be removed from the tree, and I am happy to oblige. Cc: Vinod Koul <vinod.koul@intel.com> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com> Cc: Alan Cox <alan@lxorguk.ukuu.org.uk> Signed-off-by: -
Mathieu Desnoyers authored
The user-space tracer, along with the control tools, now support longer event name strings (up to 256 chars, including \0). Signed-off-by:
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> Signed-off-by:
-
Mathieu Desnoyers authored
The patch "lttng: Fix recent modifications to string_from_user operation" has been confirmed to fix the corrupted trace problem experienced on -rt kernel by the original bug reporter. Remove the entry from the LTTng TODO list. Reported-by:
Yannick Brosseau <yannick.brosseau@gmail.com> Signed-off-by:
-
Yannick Brosseau authored
Include: a fix for a recently introduced change: obviously max_t should be used instead of min_t here. Also, a likely should apply to the result of the comparison, not the variable per se. Signed-off-by:
-
Rob Clark authored
TILER/DMM provides two features for omapdrm GEM objects: 1) providing a physically contiguous view to discontiguous memory for hw initiators that cannot otherwise support discontiguous buffers (DSS scanout, IVAHD video decode/encode, etc) 2) providing untiling for 2d tiled buffers, which are used in some cases to provide rotation and reduce memory bandwidth for hw initiators that tend to access data in 2d block patterns. For 2d tiled buffers, there are some additional complications when it comes to userspace mmap'ings. For non-tiled buffers, the original (potentially physically discontiguous) pages are used to back the mmap. For tiled buffers, we need to mmap via the tiler/dmm region to provide an unswizzled view of the buffer. But (a) the buffer is not necessarily pinned in TILER all the time (it can be unmapped when there is no DMA access to the buffer), and (b) when they are they are pinned, they not necessarily page aligned from the perspective of the CPU. And non-page aligned userspace buffer mapping is evil. To solve this, we reserve one or more small regions in each of the 2d containers when the driver is loaded to use as a "user-GART" where we can create a second page-aligned mapping of parts of the buffer being accessed from userspace. Page faulting is used to evict and remap different regions of whichever buffers are being accessed from user- space. Signed-off-by:
Rob Clark <rob@ti.com> Signed-off-by:
-
Andy Gross authored
Dynamic Memory Manager (DMM) is a hardware block in the OMAP4+ processor that contains at least one TILER instance. TILER, or Tiling and Isometric Lightweight Engine for Rotation, provides IOMMU capabilities through the use of a physical address translation table. The TILER also provides zero cost rotation and mirroring. The TILER provides both 1D and 2D access by providing different views or address ranges that can be used to access the physical memory that has been mapped in through the PAT. Access to the 1D view results in linear access to the underlying memory. Access to the 2D views result in tiled access to the underlying memory resulted in increased efficiency. The TILER address space is managed by a tiler container manager (TCM) and allocates the address space through the use of the Simple Tiler Allocation algorithm (SiTA). The purpose of the algorithm is to keep fragmentation of the address space as low as possible. Signed-off-by:
Andy Gross <andy.gross@ti.com> Signed-off-by:
-
Mark Einon authored
In commit 834d0ee3 (uintxy_t removal) not all changes were trival text replacements, some converted u64 -> dma_addr_t. In some configurations dma_addr_t is a u32, meaning that some bit operations cause build warnings. From Randy Dunlap: ---------------- on i386 (X86_32) builds: drivers/staging/et131x/et131x.c:2483:8: warning: right shift count >= width of type drivers/staging/et131x/et131x.c:2531:8: warning: right shift count >= width of type ---------------- Removed these by reverting dma_addr_t back to u64 types, as well as reverting some other non-trivial changes from the aforementioned commit. Reported-by:
Randy Dunlap <rdunlap@xenotime.net> Signed-off-by:
Mark Einon <mark.einon@gmail.com> Acked-by:
-
Valentin Rothberg authored
As Dan mentioned, dcon_write() will only write u16 values. The appropriate parts have been changed. As a result of module_param() not accepting u16 as a valid data type, ushort is used. Signed-off-by:
Valentin Rothberg <valentinrothberg@googlemail.com> Signed-off-by:
-
Valentin Rothberg authored
As noted by the checkpatch script, strict_strtoul is obsolete. Unsigned longs are used, so it seems good to take kstrtoul. Signed-off-by:
-
Oren Weil authored
The following changes were made in the document: 1. Update URLs to working links 2. remove old information about module parameters 3. Add IOCTL information. 4. cleanups and fix spelling 5. driver changed from character device to misc character device Signed-off-by:
Oren Weil <oren.jer.weil@intel.com> Signed-off-by:
Tomas Winkler <tomas.winkler@intel.com> Signed-off-by:
-
Natalia Ovsyanikov authored
The irq handler processes queued mei clients connect requests, which were not transferred to the device in ioctl context due to unavailability of the write buffer. The handler may transfer the connection request only if there is no other ongoing requests for the same mei id. This condition was implemented inversely which depending on the write buffer availability lead to seemingly random failures during connection attempts. Cc: Oren Weil <oren.jer.weil@intel.com> Signed-off-by:
Natalia Ovsyanikov <natalia.ovsyanikov@intel.com> Signed-off-by:
-
Tomas Winkler authored
list_for_each_entry_safe(pos, next, &head, list) if (pos) { .... } This check isn't needed. The list cursor in a list_for_each() loop is always a valid pointer Cc: Oren Weil <oren.jer.weil@intel.com> Reported-by:Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
-
Xi Wang authored
Change ->read_status() by separating the error handling and the status bits. This also fixes a signedness bug in dcon_interrupt() that would break the error handling. Signed-off-by:
Xi Wang <xi.wang@gmail.com> Acked-by:
Andres Salomon <dilinger@queued.net> Cc: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
-
Jerome Marchand authored
The allocation of zram->compress_buffer is misssing a GFP_* specifier. This is equivalent to GFP_NOWAIT but it is more likely a omission. Since the allocation just above it uses GFP_KERNEL, there is no reason to use GFP_NOWAIT here. Therefore, add GFP_KERNEL. Signed-off-by:
Jerome Marchand <jmarchan@redhat.com> Signed-off-by:
-
Sergey Datsevich authored
As reported by checkpatch.pl strict_strtoX is obsolet and should be replaced by kstrtoX. Signed-off-by:
Sergey Datsevich <srgdts@gmail.com> Signed-off-by:
Bjoern Meier <bjoernmeier@hotmail.com> Signed-off-by:
-
K. Y. Srinivasan authored
Set the length field of the scatter gather elements correctly when we create the bounce buffer. When we use the bounce buffer for a "write" operation, the act of copying to the bounce buffer, correctly deals with this issue. However, on the "read" side, the current code was not correctly setting the buffer length. Fix this bug. Note that when we copy from the bounce buffer (for the read case), the amount we copy is controlled by the original scatter gather list given to the driver. Signed-off-by:
Dadok Milan <dadok@kvados.cz> Signed-off-by:
-
Johannes Tenschert authored
Signed-off-by:
Johannes Tenschert <Johannes.Tenschert@informatik.stud.uni-erlangen.de> Reviewed-by:
-
Johannes Tenschert authored
Signed-off-by:
-
Johannes Tenschert authored
Signed-off-by:
-
Johannes Tenschert authored
Signed-off-by:
-
Johannes Tenschert authored
Signed-off-by:
-
Kevin McKinney authored
In this clean up patch, I altered functions: copy_to/ from_user() to return -EFAULT when an error occurs. I also replaced break statements when an error occurs from copy_to/from_user() with direct returns of -EFAULT. Signed-off-by:
Kevin McKinney <klmckinney1@gmail.com> Signed-off-by:
-
Kevin McKinney authored
Staging: bcm: Alter code to move error handling closer to the calls; and remove white space, IOCTL_BCM_NVM_WRITE. This is a clean up patch for IOCTL_BCM_NVM_WRITE that replaces the assignment of the Status variable with direct returns of the error code, replaces the break statements with direct returns, and removes a white space. Signed-off-by:
-
Kevin McKinney authored
This patch fixes a memory error in ioctl, IOCTL_BCM_NVM_WRITE. While copying data to user space, if an error occurs, pReadData is freed. Then, at the end of the ioctl, pReadData was being freed again. Signed-off-by:
-
Markus Grabner authored
This patch refactors the device information code and adds preliminary support for the POD HD 500 device. Signed-off-by:
Markus Grabner <grabner@icg.tugraz.at> Signed-off-by:
-
Markus Grabner authored
This patch removes experimental code which is no longer used. Signed-off-by:
-
Andor Daam authored
The obsolete function strict_strtoul should be replaced by the kstrto* functions. In this context kstrtou16 should be use, as midi_mask_receive is only used as unsigned short. All corresponding datatypes were adapted accordingly. Signed-off-by:
Andor Daam <andor.daam@googlemail.com> Signed-off-by:
-
Andor Daam authored
The function strict_strtoul is obsolete and should be replaced by the new kstrto* functions. The variable midi_mask_transmit is only used as unsigned short and the datatypes of all affected variables were adjusted accordingly. Signed-off-by:
-
Dan Carpenter authored
We should release the udev->sem lock before returning. Signed-off-by:
-
Dan Carpenter authored
If we had an invalid trignum (anything other than zero is invalid) then we returned without unlocking. I've modified this function to just have one return point. Signed-off-by:
-
Aaro Koskinen authored
Enable forcecrt2type as a module parameter. Signed-off-by:
Aaro Koskinen <aaro.koskinen@iki.fi> Signed-off-by:
-
