- 05 Dec, 2013 1 commit
-
-
Jingoo Han authored
Don't use DEFINE_PCI_DEVICE_TABLE macro, because this macro is not preferred. Signed-off-by:
Jingoo Han <jg1.han@samsung.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
- 03 Dec, 2013 30 commits
-
-
Geert Uytterhoeven authored
device_driver.name is "const char *" Signed-off-by:
Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by:
-
Geert Uytterhoeven authored
device_driver.name is "const char *" Signed-off-by:
-
Geert Uytterhoeven authored
device_driver.name is "const char *" Signed-off-by:
-
Oliver Neukum authored
It is useless now. Straight removal. Signed-off-by:
Oliver Neukum <oneukum@suse.de> Signed-off-by:
-
Oliver Neukum authored
In the drivers that no longer need it, it is removed. It is removed from the Makefile. Drivers not fully converted to dynamic debug have it shifted down into the individual drivers. Signed-off-by:
-
Oliver Neukum authored
With dynamic debugging this log level is no longer supported. The decision which messages are interesting is done in user space. Signed-off-by:
-
Oliver Neukum authored
This allows removal of much conditional compilation. Signed-off-by:
-
Oliver Neukum authored
This is a step in the conversion to only use dynamic debugging. Signed-off-by:
-
Oliver Neukum authored
That logging is overkill. Simply remove it. Signed-off-by:
-
Oliver Neukum authored
These helpers are used only during setup of a HCD. A small overhead is no problem. Signed-off-by:
-
Oliver Neukum authored
This makes sure the header files are all there Signed-off-by:
-
Oliver Neukum authored
To allow a full switch to dynamic debugging make the debug parameter conditional on defined(DEBUF) || defined(CONFIG_DYNAMIC_DEBUG) Signed-off-by:
-
Oliver Neukum authored
This gets rid of conditional compilation. Signed-off-by:
-
Oliver Neukum authored
The decision what is interesting is shifted to user space by dynamic debugging. Signed-off-by:
-
Oliver Neukum authored
The decision what is interesting is made in user space. Signed-off-by:
-
Oliver Neukum authored
For dynamic debug the overhead for evaluating parameters must be sacrificed only if the message is actually printed Signed-off-by:
-
Oliver Neukum authored
Simply remove the conditional compilation and remove the empty stubs. Signed-off-by:
-
Oliver Neukum authored
Always compile in the debugfs support Signed-off-by: -
Oliver Neukum authored
This is overkill. Just removeit. Signed-off-by:
-
Oliver Neukum authored
Simple elemination of the conditional compilation Signed-off-by:
-
Oliver Neukum authored
With dynamic debugging the selection is done in user space Signed-off-by:
-
Oliver Neukum authored
Just remove the conditional compilation. Signed-off-by:
-
Oliver Neukum authored
With the introduction of dynamic debugging it has become redundant. Collapse it with ohci_dbg() Signed-off-by:
-
Oliver Neukum authored
Conditional compilation for debugging is removed in favor of dynamic debugging. To do so 1. the support for debugfs is always compiled 2. the support for the ancient print_urb debugging aid is removed Signed-off-by:
-
Oliver Neukum authored
An ioctl that does depends on communication with a device should prevent suspension of teh device. Signed-off-by:
-
Oliver Neukum authored
Simple straightforward implementation. Just returning the statistics gathered for TIOCMIWAIT Signed-off-by:
-
Oliver Neukum authored
This implements TIOCMIWAIT for TIOCM_DSR, TIOCM_RI and TIOCM_CD Disconnect is handled as TIOCM_CD or an error. Signed-off-by:
-
Jingoo Han authored
Don't use DEFINE_PCI_DEVICE_TABLE macro, because this macro is not preferred. Signed-off-by:
-
Fabio Estevam authored
Commit 40ed51a4 (usb: chipidea: host: add vbus regulator control) introduced a smatch complaint because regulator_disable() is called without checking whether ci->platdata->reg_vbus is not NULL. Fix this by adding the check. Reported-by:
Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com> Signed-off-by:
-
Greg Kroah-Hartman authored
Merge tag 'for-usb-next-2013-12-02' of git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci into usb-next Sarah writes: xhci: Cleanup for 3.14: Sparse fixes, replace xhci_read/write, misc Hi Greg, Here's fifteen patches for 3.14. They include some non-urgent cleanups, and the patches to replace the xhci_read/write variants with standard read/write calls. As you asked, the big endian fixes are being queued for 3.14 and they aren't marked for stable. This also includes a couple of streams fixes, but not the full set from Hans. (I'll test those later this week.) The goal is to get both the xHCI driver streams support and the UAS driver fixed up for 3.14. We don't want to mark the fixes for stable, as all the code changes are really too big for stable. Please queue for 3.14. Sarah Sharp
-
- 02 Dec, 2013 9 commits
-
-
Xenia Ragiadakou authored
Function xhci_write_64() is used to write 64bit xHC registers residing in MMIO. On 32bit systems, xHC registers need to be written with 32bit accesses by writing first the lower 32bits and then the higher 32bits. The header file asm-generic/io-64-nonatomic-lo-hi.h ensures that on 32bit systems writeq() will will write 64bit registers in 32bit chunks with low-high order. Replace all calls to xhci_write_64() with calls to writeq(). This is done to reduce code duplication since 64bit low-high write logic is already implemented and to take advantage of inherent "atomic" 64bit write operations on 64bit systems. Signed-off-by:
Xenia Ragiadakou <burzalodowa@gmail.com> Signed-off-by:
Sarah Sharp <sarah.a.sharp@linux.intel.com>
-
Xenia Ragiadakou authored
Function xhci_read_64() is used to read 64bit xHC registers residing in MMIO. On 32bit systems, xHC registers need to be read with 32bit accesses by reading first the lower 32bits and then the higher 32bits. Replace all calls to xhci_read_64() with calls to readq() and include asm-generic/io-64-nonatomic-lo-hi.h header file, so that if the system is not 64bit, readq() will read registers in 32bit chunks with low-high order. This is done to reduce code duplication since 64bit low-high read logic is already implemented and to take advantage of inherent "atomic" 64bit read operations on 64bit systems. Signed-off-by:
-
Xenia Ragiadakou authored
Function xhci_writel() is used to write a 32bit value in xHC registers residing in MMIO address space. It takes as first argument a pointer to the xhci_hcd although it does not use it. xhci_writel() internally simply calls writel(). This creates an illusion that xhci_writel() is an xhci specific function that has to be called in a context where a pointer to xhci_hcd is available. Remove xhci_writel() wrapper function and replace its calls with calls to writel() to make the code more straight-forward. Signed-off-by:
-
Xenia Ragiadakou authored
Function xhci_readl() is used to read 32bit xHC registers residing in MMIO address space. It takes as first argument a pointer to the xhci_hcd although it does not use it. xhci_readl() internally simply calls readl(). This creates an illusion that xhci_readl() is an xhci specific function that has to be called in a context where a pointer to xhci_hcd is available. Remove the unnecessary xhci_readl() wrapper function and replace its calls to with calls to readl() to make the code more straightforward. Signed-off-by:
-
Xenia Ragiadakou authored
This patch removes the to_pci_dev() conversion performed to generic struct device since it is not actually useful (the pointer to the generic device can be used directly rather through a conversion to pci_dev) and it is pci bus specific. This isn't stable material because this code will produce harmless behavior on non-PCI xHCI hosts. The pci_device pointer is never dereferenced, only used to re-calculate the underlying device pointer. Signed-off-by:
-
Xenia Ragiadakou authored
The fields 'add_flags' and 'drop_flags' in struct xhci_input_control_ctx have type __le32 and need to be converted to CPU byteorder before being used to derive the number of dropped endpoints. This bug was found using sparse. This patch is not suitable for stable, since the bug would only be triggered on big endian systems, and the code only runs for Intel xHCI host controllers, which are always integrated into little endian systems. Signed-off-by:
-
Xenia Ragiadakou authored
The fields 'add_flags' and 'drop_flags' in struct xhci_input_control_ctx have type __le32 and need to be converted to CPU byteorder before being used to derive the number of added endpoints. This bug was found using sparse. This patch is not suitable for stable, since the bug would only be triggered on big endian systems, and the code only runs for Intel xHCI host controllers, which are always integrated into little endian systems. Signed-off-by:
-
Xenia Ragiadakou authored
This patch removes the unneccessary check 'if (stream_info)' because there is already a check few lines above which ensures that stream_info is not NULL. Signed-off-by:
-
Xenia Ragiadakou authored
SCT_FOR_CTX(p) is defined as (((p) << 1) & 0x7) in which case if we want to set the stream context type to SCT_SSA_256 i.e 0x7 (although secondary stream arrays are not yet supported) using this macro definition we will get actually 0x6 which is not what we want. This patch fixes the above issue by defining the SCT_FOR_CTX(p) macro as (((p) & 0x7) << 1) Signed-off-by:
-
