On 02/11/2014 06:35 PM, Hans de Goede wrote:
The initial versions of the devicetree enablement patches for ohci-platform
used ohci-platform as compatible string. However this was disliked by
various
reviewers because the platform bus is a Linux invention and devicetree is
supposed to be OS
On Wednesday 29 January 2014 08:17 PM, Heikki Krogerus wrote:
Hi,
On Tue, Jan 28, 2014 at 10:30:36AM -0600, Felipe Balbi wrote:
On Tue, Jan 28, 2014 at 05:32:30PM +0200, Heikki Krogerus wrote:
On Mon, Jan 27, 2014 at 10:05:20AM -0600, Felipe Balbi wrote:
For the controller drivers the PHYs
This is to re-notify you that you have $500,000.00 waiting for pick-up at Money
Gram, Contact
Mrs Hillary Florence via email : heritd...@xtra.co.nz for claims.
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More
On Mon, Feb 10, 2014 at 01:33:39PM +0800, liujunliang_...@163.com wrote:
From: Liu Junliang liujunliang_...@163.com
Signed-off-by: Liu Junliang liujunliang_...@163.com
---
drivers/net/usb/Kconfig | 16 +
drivers/net/usb/Makefile |1 +
drivers/net/usb/sr9800.c | 873
fixed a potential NULL pointer dereference.
Rationale:
this is the only location in the musb driver where the
otg-gadget pointer is dereferenced. Assuming that it
is never NULL is not only potentially unsafe but was
observed in the wild on a GTA04 (OMAP3/TPS65950 based
Remove non-compatible id from examples.
CC: Alan Stern st...@rowland.harvard.edu
Signed-off-by: Roger Quadros rog...@ti.com
---
Documentation/devicetree/bindings/usb/ehci-omap.txt | 2 +-
Documentation/devicetree/bindings/usb/ohci-omap3.txt | 2 +-
2 files changed, 2 insertions(+), 2
The necessary clock phandle for the EHCI clock is now provided
via device tree so we no longer need this legacy method.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/pdata-quirks.c | 16
1 file changed, 16 deletions(-)
diff --git
The USB PHY gets its clock from AUXCLK3. Provide this
information.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi
The OMAP EHCI and OHCI controllers are not compatible with drivers
other than ti,ehci-omap and ti,ohci-omap3 respectively, so get
rid of the incompatible ids.
CC: Alan Stern st...@rowland.harvard.edu
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap3.dtsi | 4 ++--
The omap-usb-host driver expects certained named clocks.
Add this information to the DT binding document.
CC: Lee Jones lee.jo...@linaro.org
CC: Samuel Ortiz sa...@linux.intel.com
Signed-off-by: Roger Quadros rog...@ti.com
---
.../devicetree/bindings/mfd/omap-usb-host.txt | 23
The omap-usb-host driver expects a certain name for internal
and external reference clocks. Provide these clocks.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap4.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi
Use devm_clk_get() instead of clk_get().
CC: Lee Jones lee.jo...@linaro.org
CC: Samuel Ortiz sa...@linux.intel.com
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Lee Jones lee.jo...@linaro.org
---
drivers/mfd/omap-usb-host.c | 81 +
1 file
Not all revisions have all the clocks so get the necessary clocks
based on hardware revision.
This should avoid un-necessary clk_get failure messages that were
observed earlier.
Be more strict and always fail on clk_get() error.
CC: Lee Jones lee.jo...@linaro.org
CC: Samuel Ortiz
Use a meaningful name for the reference clocks so that it indicates the
function.
CC: Lee Jones lee.jo...@linaro.org
CC: Samuel Ortiz sa...@linux.intel.com
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/mfd/omap-usb-host.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Hi Benoit, Tony Lee,
This patchset brings up USB Host ports and Ethernet port on
the OMAP5 uEVM board. Please queue these for -next.
Tested on:
- OMAP5 uEVM
- Pandaboard ES Rev. B1
- Beagleboard-XM Rev C2
- Beagleboard Rev C4.
Changelog:
v7:
- Rebased on 3.14-rc2
- Removed incompatible
From: Jean-Jacques Hiblot jjhib...@traphandler.com
When using dt resources retrieval (interrupts and reg properties) there is
no predefined order for these resources in the platform dev resource
table. Also don't expect the number of resource to be always 2.
Signed-off-by: Jean-Jacques Hiblot
On Wed, Feb 12, 2014 at 11:08:22AM +0100, Dr. H. Nikolaus Schaller wrote:
fixed a potential NULL pointer dereference.
Rationale:
this is the only location in the musb driver where the
otg-gadget pointer is dereferenced. Assuming that it
is never NULL is not only
When the PXS8 and PHS8 devices show up with PID 0x0053 they will expose both a
QMI port and a WWAN interface.
CC: Hans-Christoph Schemmel hans-christoph.schem...@gemalto.com
CC: Christian Schmiedl christian.schmi...@gemalto.com
CC: Nicolaus Colberg nicolaus.colb...@gemalto.com
CC: David
On Tue, Feb 11, 2014 at 04:26:16PM +0100, Hans de Goede wrote:
I'm even OK with removing usb-ehci and usb-ohci compatibles
from all OMAP dts files since they aren't really compatible with
the original PPC driver.
I don't think that is necessary, as your grep has shown there are a
lot of
This interface is to be handled by the qmi_wwan driver.
CC: Hans-Christoph Schemmel hans-christoph.schem...@gemalto.com
CC: Christian Schmiedl christian.schmi...@gemalto.com
CC: Nicolaus Colberg nicolaus.colb...@gemalto.com
CC: David McCullough david.mccullo...@accelecon.com
Signed-off-by:
On Wed, 12 Feb 2014, Peter Chen wrote:
In your case, the wakeup condition will be present while the bus uses
high-speed terminations, but when the bus switches over to full-speed
idle the wakeup condition will go away. Thus, I assume the wakeup
signal will turn off after a few
Aleksander Morgado aleksan...@aleksander.es writes:
When the PXS8 and PHS8 devices show up with PID 0x0053 they will expose both a
QMI port and a WWAN interface.
CC: Hans-Christoph Schemmel hans-christoph.schem...@gemalto.com
CC: Christian Schmiedl christian.schmi...@gemalto.com
CC:
Am 12.02.2014 um 15:29 schrieb Greg Kroah-Hartman:
On Wed, Feb 12, 2014 at 11:08:22AM +0100, Dr. H. Nikolaus Schaller wrote:
fixed a potential NULL pointer dereference.
Rationale:
this is the only location in the musb driver where the
otg-gadget pointer is dereferenced. Assuming
On Wed, 12 Feb 2014, Stefani Seibold wrote:
Hi,
Am Dienstag, den 11.02.2014, 11:30 -0500 schrieb Alan Stern:
On Mon, 10 Feb 2014, Stefani Seibold wrote:
I have more information about the bug. I tested with a USB 3.0
Expresscard and this works with 3.13.
I also found
Am Mittwoch, den 12.02.2014, 10:37 -0500 schrieb Alan Stern:
On Wed, 12 Feb 2014, Stefani Seibold wrote:
Hi,
Am Dienstag, den 11.02.2014, 11:30 -0500 schrieb Alan Stern:
On Mon, 10 Feb 2014, Stefani Seibold wrote:
I have more information about the bug. I tested with a USB
On 02/12/2014 04:47 PM, Stefani Seibold wrote:
Am Mittwoch, den 12.02.2014, 10:37 -0500 schrieb Alan Stern:
On Wed, 12 Feb 2014, Stefani Seibold wrote:
Hi,
Am Dienstag, den 11.02.2014, 11:30 -0500 schrieb Alan Stern:
On Mon, 10 Feb 2014, Stefani Seibold wrote:
I have more information
On Wed, Feb 12, 2014 at 04:35:12PM +0100, Dr. H. Nikolaus Schaller wrote:
Am 12.02.2014 um 15:29 schrieb Greg Kroah-Hartman:
On Wed, Feb 12, 2014 at 11:08:22AM +0100, Dr. H. Nikolaus Schaller wrote:
fixed a potential NULL pointer dereference.
Rationale:
this is the only
Am Mittwoch, den 12.02.2014, 16:57 +0100 schrieb Michael Opdenacker:
On 02/12/2014 04:47 PM, Stefani Seibold wrote:
Am Mittwoch, den 12.02.2014, 10:37 -0500 schrieb Alan Stern:
On Wed, 12 Feb 2014, Stefani Seibold wrote:
Hi,
Am Dienstag, den 11.02.2014, 11:30 -0500 schrieb Alan Stern:
On Wed, Feb 12, 2014 at 05:20:10PM +0100, Stefani Seibold wrote:
Am Mittwoch, den 12.02.2014, 16:57 +0100 schrieb Michael Opdenacker:
On 02/12/2014 04:47 PM, Stefani Seibold wrote:
Am Mittwoch, den 12.02.2014, 10:37 -0500 schrieb Alan Stern:
On Wed, 12 Feb 2014, Stefani Seibold wrote:
Am Mittwoch, den 12.02.2014, 08:28 -0800 schrieb Greg KH:
On Wed, Feb 12, 2014 at 05:20:10PM +0100, Stefani Seibold wrote:
Am Mittwoch, den 12.02.2014, 16:57 +0100 schrieb Michael Opdenacker:
On 02/12/2014 04:47 PM, Stefani Seibold wrote:
Am Mittwoch, den 12.02.2014, 10:37 -0500 schrieb
Hi guys,
I just tried today's Linus' master (45f7fdc2ff) with usb-linus (3635c7e2d5)
merged on top to give the latest dwc2 fixes another try.
Unfortunately I'm getting various crashes on system startup. Kernel boots
fine, dwc2 and the integrated smsc95xx are detected, but somewhere in the
init
Updated patch, moved blacklisted vid/pid from usbhid/hid-quirks.c's
hid_blacklist to hid-core.c's hid_ignore_list as proposed by Greg KH.
It's supposed to suppress binding of usbhid to a USB connected LED
supported by usbled. It isn't useful as a input device and produces
kernel complaints about
The Webmail Notifier is a USB controlled LED that appears as a HID
device. When trying to change the LED via hidraw it returns malformed
reports. As usbled supports it, we blacklist it in usbhid.
Signed-off-by: Christian Vogel vogel...@vogel.cx
---
drivers/hid/hid-core.c | 1 +
On Wed, 12 Feb 2014, Stefani Seibold wrote:
Okay, the debugging info in your dmesg log indicates the cause of the
problem. It looks like the bug is related to commit 88ed9fd50e57
(usb/hcd: remove unnecessary local_irq_save) by Michael Opdenacker.
For the benefit of people who
Well, here is a quick-and-dirty proof-of-concept. Warning: it's ugly
and you might go blind. Having said that, the code works well enough
to detect
all USB devices I tried and HID devices as well as USB mass storage
seem to work fine.
I'm not terribly familiar with the details of USB and/or the
This patch removes a generic hard_header_len check from the usbnet
module that is causing dropped packages under certain circumstances
for devices that send rx packets that cross urb boundaries.
One example is the AX88772B which occasionally send rx packets that
cross urb boundaries where the
In a couple of places, we were checking qtd-urb for NULL after
we had already dereferenced it. Fix this by moving the check to
before the dereference.
Signed-off-by: Paul Zimmerman pa...@synopsys.com
---
This is not a regression fix, so it should be queued for 3.15.
drivers/usb/dwc2/hcd_intr.c
To avoid buffer overflow while reading a corrupted or possibly
modified port file we validate the length of each part of the port
record to ensure it doesn't exceed the length of the destination
buffer.
https://bugzilla.kernel.org/show_bug.cgi?id=69931
Signed-off-by: Mark Asselstine
On 02/12/2014 11:52 AM, Andre Heider wrote:
Hi guys,
I just tried today's Linus' master (45f7fdc2ff) with usb-linus (3635c7e2d5)
merged on top to give the latest dwc2 fixes another try.
Unfortunately I'm getting various crashes on system startup. Kernel boots
fine, dwc2 and the integrated
From: Liu Junliang liujunliang_...@163.com
Signed-off-by: Liu Junliang liujunliang_...@163.com
---
drivers/net/usb/Kconfig |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/usb/Kconfig b/drivers/net/usb/Kconfig
index 2551bf6..82df7c3 100644
--- a/drivers/net/usb/Kconfig
+++
Dear Thierry :
For this driver, we can set it as 'n', and There is no
rule of thumb as to which should default to y.
Thanks for your advice.
Thanks again.
2014-02-13
liujunliang_ljl
Hi,
The bugreport on Bugzilla is Bug 70361:
https://bugzilla.kernel.org/show_bug.cgi?id=70361
I have a Thinkpad OneLink dock, which is a USB dock and has a USB 3.0
hub, a USB 2.0 hub, and ax88179 ethernet.
This dock's USB 3.0 hub is disconnected for no reason.
This occurs even when the ethernet
At my case, the wakeup condition isn't existed before glue layer code
has run (put the phy enter low power mode).
wakeup condition = bus condition (SE0) + PHY condition (low power mode)
The wakeup condition should not be there, or the system can't enter
suspend, it is not we
43 matches
Mail list logo
