Hi,
On Tue, Jun 10, 2014 at 1:52 AM, Julius Werner jwer...@chromium.org wrote:
diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
index 9ffecd5..453d89e 100644
--- a/drivers/usb/host/xhci.h
+++ b/drivers/usb/host/xhci.h
@@ -1582,6 +1582,9 @@ struct xhci_hcd {
u32
Ping
Thanks,
Sundeep.B.S.
On Tue, Jun 10, 2014 at 5:34 PM, subbaraya.sundeep.bha...@xilinx.com wrote:
From: Subbaraya Sundeep Bhatta sbha...@xilinx.com
Add devicetree bindings for Xilinx axi udc driver.
Signed-off-by: Subbaraya Sundeep Bhatta sbha...@xilinx.com
---
Changes for v3:
From: Bryan O'Donoghue bryan.odonog...@intel.com
This patch is to enable USB host controller for Intel Quark X1000. Add pci
quirks
to adjust the packet buffer in/out threshold value, and ensure EHCI packet
buffer
i/o threshold value is reconfigured to half.
Signed-off-by: Bryan O'Donoghue
From: Alvin (Weike) Chen alvin.c...@intel.com
Hi,
Intel Quark X1000 consists of one USB host controller which can be PCI
enumerated.
But the exsiting EHCI-PCI framework doesn't support it. Thus, we enable it to
support
Intel Quark X1000 USB host controller by adding pci quirks to configure
On 06/23/2014 03:44 PM, David Laight wrote:
From: vichy
hi all:
when i trace xhci source, I found in skip_isoc_td, there is a
possibility to increase de-queue pointer twice.
in skip_isoc_td:
/* Update ring dequeue pointer */
while (ep_ring-dequeue != td-last_trb)
Since commit [ac8dde11: “Add flags to descriptors block”] functionfs
supports a new descriptor format, so we update example application
to make it using recomended version of descriptors.
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
There's no power/persist file for hubs. And CONFIG_USB_PERSIST was
removed in v2.6.26. Update the description of power/persist accordingly.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
I don't know anything about USB-Persist. Could Greg and Alan please
check whether the new description does
i'm sorry, i think you said is the patch of my submit yesterday.i misunderstand
you means.
At 2014-06-23 06:52:22, Johan Hovold jo...@kernel.org wrote:
On Mon, Jun 23, 2014 at 06:15:52PM +0800, 刘磊 wrote:
Could you try the first patch (only) and see if it fixes the problem?
Does it also fix
A new book on Android USB :
http://www.amazon.com/dp/1430262087 .
This book covers everything about USB on Android from different USB
Classes supported in device mode to the USB host framework that
manages USB device connected to an Android platform. Each chapter will
explain USB class
CONFIG_USB_PERSIST was removed in v2.6.26. Remove a reference to it from
Documentation. That reference was a bit odd to begin with.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
[...] under certain circumstances [...]? Is that about
USB_QUIRK_RESET_RESUME? Anyhow, I feel this paragraph needs
Adds nodes describing the Marvell Berlin BG2Q USB PHY and USB. The BG2Q
SoC has 3 USB host controller, compatible with ChipIdea.
Signed-off-by: Antoine Ténart antoine.ten...@free-electrons.com
---
arch/arm/boot/dts/berlin2q.dtsi | 52 +
1 file changed, 52
From: Sebastian Hesselbarth sebastian.hesselba...@gmail.com
Adds nodes describing the Marvell Berlin BG2CD USB PHY and USB. The BG2CD
SoC has 2 USB ChipIdea controllers, with usb0 host-only and usb1 dual-role
capable.
Signed-off-by: Sebastian Hesselbarth sebastian.hesselba...@gmail.com
---
From: Sebastian Hesselbarth sebastian.hesselba...@gmail.com
Enable usb1 on Google Chromecast which is connected to micro-USB
plug used for external power supply, too.
Signed-off-by: Sebastian Hesselbarth sebastian.hesselba...@gmail.com
---
arch/arm/boot/dts/berlin2cd-google-chromecast.dts | 4
Add a generic ChipIdea driver, with optional PHY and clock, to support
ChipIdea controllers that doesn't need specific functions.
Needed for the Marvell Berlin SoCs SUB controllers.
Signed-off-by: Antoine Ténart antoine.ten...@free-electrons.com
---
drivers/usb/chipidea/Makefile | 1
Document the bindings of the Marvell Berlin USB PHY driver.
Signed-off-by: Antoine Ténart antoine.ten...@free-electrons.com
---
Documentation/devicetree/bindings/usb/berlin-usb-phy.txt | 16
1 file changed, 16 insertions(+)
create mode 100644
Add the driver driving the Marvell Berlin USB PHY. This allows to
initialize the PHY and to use it from the USB driver later.
Signed-off-by: Antoine Ténart antoine.ten...@free-electrons.com
---
drivers/usb/phy/Kconfig | 9 ++
drivers/usb/phy/Makefile | 1 +
This series adds the support for generic ChipIdea USB controllers,
the USB PHYs of the Marvell Berlin SoCs and also adds a reset
controller for these SoCs.
The reset controller is used by the USB PHY driver and shares the
existing chip controller node with the clocks and one pin controller.
The
On Tuesday, June 24, 2014 7:35 PM, Antoine Tenart wrote:
Add a generic ChipIdea driver, with optional PHY and clock, to support
ChipIdea controllers that doesn't need specific functions.
s/doesn't/don't
Needed for the Marvell Berlin SoCs SUB controllers.
s/SUB/USB
Signed-off-by:
Add missing information about license. Some people will probably want to
reuse this code in their projects released under variety of licenses. For this
reason this example is under Public Domain license to avoid GPL limitations.
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
On 06/23/2014 08:27 PM, Felipe Balbi wrote:
Hi,
On Mon, Jun 23, 2014 at 08:07:43AM +0200, Robert Baldyga wrote:
On 06/19/2014 05:08 PM, Felipe Balbi wrote:
On Mon, Jun 16, 2014 at 10:20:36AM +0200, Robert Baldyga wrote:
This field allows to mark ep as claimed in more clear way. Claiming
Hello.
On 06/24/2014 07:51 PM, Chen, Alvin wrote:
From: Bryan O'Donoghue bryan.odonog...@intel.com
This patch is to enable USB host controller for Intel Quark X1000. Add pci
quirks
to adjust the packet buffer in/out threshold value, and ensure EHCI packet
buffer
i/o threshold value is
At 2014-06-23 10:49:14, Johan Hovold jo...@kernel.org wrote:
On Mon, Jun 23, 2014 at 09:42:08AM -0500, Dan Williams wrote:
On Mon, 2014-06-23 at 18:15 +0800, 刘磊 wrote:
Could you try the first patch (only) and see if it fixes the problem?
Does it also fix the problem you're having with PID
On Tue, Jun 24, 2014 at 09:31:55PM +0900, Taeung wrote:
Hello, linux-usb
I have a question about USB 3.0.
Please help me.
I'm using SMDK5250 hardware and linux-3.0.31.
Why not try using a modern kernel version, like 3.15, first? 3.0 is
very old and obsolete, please don't try to bring up
The Exynos4412 USB 2.0 PHY hardware differs from the description provided
in the documentation. Some register bits have different function. This
patch fixes the defines of register bits and changes the way how phys are
powered on and off.
Signed-off-by: Kamil Debski k.deb...@samsung.com
---
On Wed, Jun 18, 2014 at 11:28:25AM +0200, Daniel Mack wrote:
Hi,
Hi Daniel,
I've been debugging issues with musb in host mode and both full-speed
and high-speed USB audio devices with cppi41 DMA mode enabled.
The effect that was observed with full-speed devices was that CPU load
went up
Can I disable VBUS while keeping the rest of USB functional for a
device that does not require bus power?
unfortunately not, your device would see a disconnection. The reason is
that even though you don't really put any load on the bus, the PHY still
samples VBUS levels to know when the
Johan Hovold jo...@kernel.org writes:
This is a non-standard attribute of this particular laptop. It has three
individual LEDs that can be enabled separately (using standard LED class
attributes), but they will all three be in the same mode (which here
apparently means that they can be fully
On Tue, Jun 24, 2014 at 08:51:43AM -0700, Chen, Alvin wrote:
From: Bryan O'Donoghue bryan.odonog...@intel.com
This patch is to enable USB host controller for Intel Quark X1000. Add pci
quirks
to adjust the packet buffer in/out threshold value, and ensure EHCI packet
buffer
i/o threshold
On Tue, Jun 24, 2014 at 08:51:43AM -0700, Chen, Alvin wrote:
diff --git a/drivers/usb/host/pci-quirks.c b/drivers/usb/host/pci-quirks.c
index 00661d3..1ea8803 100644
--- a/drivers/usb/host/pci-quirks.c
+++ b/drivers/usb/host/pci-quirks.c
@@ -823,6 +823,48 @@ static int handshake(void __iomem
Hi Greg
These xhci fixes are for usb-linus 3.16-rc.
Most of them are small fixes that also go to stable.
Julius Correct last context entry is the only one with a
bit more content.
-Mathias
Julius Werner (1):
usb: xhci: Correct last context entry calculation for Configure
Endpoint
Lu
On Tue, Jun 24, 2014 at 08:43:36PM +0800, 刘磊 wrote:
At 2014-06-23 10:49:14, Johan Hovold jo...@kernel.org wrote:
On Mon, Jun 23, 2014 at 09:42:08AM -0500, Dan Williams wrote:
On Mon, 2014-06-23 at 18:15 +0800, 刘磊 wrote:
i don't know why create the file of zte_ev.c that is not
necessary.
hi David:
2014-06-18 22:33 GMT+08:00 David Laight david.lai...@aculab.com:
From: vichy
...
and I get error message as
platform-xhci: ERROR Transfer event TRB DMA ptr 483702160 not part of
current TD
platform-xhci: trb_comp_code = 0x1, event status -115, buffer
1cd4b590, len 100, flags
hi Mathias:
2014-06-24 16:38 GMT+08:00 Mathias Nyman mathias.ny...@linux.intel.com:
On 06/23/2014 03:44 PM, David Laight wrote:
From: vichy
hi all:
when i trace xhci source, I found in skip_isoc_td, there is a
possibility to increase de-queue pointer twice.
in skip_isoc_td:
/* Update
On Fri, Jun 20, 2014 at 01:40:49PM -0700, Greg KH wrote:
On Fri, Jun 20, 2014 at 09:44:37AM -0500, Felipe Balbi wrote:
Hi Greg,
Here's my first set of fixes for this -rc cycle. Please consider merging
to your usb-linus branch.
I'll do it after Linus picks up my last round of changes I
Command completion events normally include command completion status,
SLOT_ID, and a pointer to the original command. Reset device command
completion SLOT_ID may be zero according to xhci specs 4.6.11.
VIA controllers set the SLOT_ID to zero, triggering a WARN_ON in the
command completion
Grant emailgr...@gmail.com writes:
Can I disable VBUS while keeping the rest of USB functional for a
device that does not require bus power?
unfortunately not, your device would see a disconnection. The reason is
that even though you don't really put any load on the bus, the PHY still
From: Julius Werner jwer...@chromium.org
The current XHCI driver recalculates the Context Entries field in the
Slot Context on every add_endpoint() and drop_endpoint() call. In the
case of drop_endpoint(), it seems to assume that the add_flags will
always contain every endpoint for the new
From: Lu Baolu baolu...@linux.intel.com
When xHCI PCI host is suspended, if do_wakeup is false in xhci_pci_suspend,
xhci_bus_suspend needs to clear all root port wake on bits. Otherwise some Intel
platforms may get a spurious wakeup, even if PCI PME# is disabled.
This patch should be back-ported
The transfer burst count (TBC) field in xhci 1.0 hosts should be set
to the number of bursts needed to transfer all packets in a isoc TD.
Supported values are 0-2 (1 to 3 bursts per service interval).
Formula for TBC calculation is given in xhci spec section 4.11.2.3:
TBC = roundup( Transfer
From: Wang, Yu yu.y.w...@intel.com
The system suspend flow as following:
1, Freeze all user processes and kenrel threads.
2, Try to suspend all devices.
2.1, If pci device is in RPM suspended state, then pci driver will try
to resume it to RPM active state in the prepare stage.
2.2,
On Tue, 24 Jun 2014, Chen, Alvin wrote:
From: Bryan O'Donoghue bryan.odonog...@intel.com
This patch is to enable USB host controller for Intel Quark X1000. Add pci
quirks
to adjust the packet buffer in/out threshold value, and ensure EHCI packet
buffer
i/o threshold value is
From: Of Mathias Nyman
Command completion events normally include command completion status,
SLOT_ID, and a pointer to the original command. Reset device command
completion SLOT_ID may be zero according to xhci specs 4.6.11.
VIA controllers set the SLOT_ID to zero, triggering a WARN_ON in
On Mon, 23 Jun 2014, Dan Williams wrote:
Alan, I'm wondering if we should be looking at a change in the core to
prevent these rpm_suspend() vs dpm_suspend() collisions? I.e. waking
up runtime suspended hubs prior to khubd being frozen?
I don't fully understand the question. What collisions
On Tue, Jun 24, 2014 at 05:14:42PM +0300, Mathias Nyman wrote:
From: Julius Werner jwer...@chromium.org
The current XHCI driver recalculates the Context Entries field in the
Slot Context on every add_endpoint() and drop_endpoint() call. In the
case of drop_endpoint(), it seems to assume that
On Tue, 24 Jun 2014, Paul Bolle wrote:
There's no power/persist file for hubs. And CONFIG_USB_PERSIST was
removed in v2.6.26. Update the description of power/persist accordingly.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
I don't know anything about USB-Persist. Could Greg and Alan
On Tue, 24 Jun 2014, Paul Bolle wrote:
CONFIG_USB_PERSIST was removed in v2.6.26. Remove a reference to it from
Documentation. That reference was a bit odd to begin with.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
[...] under certain circumstances [...]? Is that about
On 06/24/2014 05:10 PM, Greg KH wrote:
On Tue, Jun 24, 2014 at 05:14:42PM +0300, Mathias Nyman wrote:
From: Julius Werner jwer...@chromium.org
The current XHCI driver recalculates the Context Entries field in the
Slot Context on every add_endpoint() and drop_endpoint() call. In the
case of
On Tue, Jun 24, 2014 at 05:51:16PM +0300, Mathias Nyman wrote:
On 06/24/2014 05:10 PM, Greg KH wrote:
On Tue, Jun 24, 2014 at 05:14:42PM +0300, Mathias Nyman wrote:
From: Julius Werner jwer...@chromium.org
The current XHCI driver recalculates the Context Entries field in the
Slot
On Tue, Jun 24, 2014 at 03:10:43PM +0200, Bjørn Mork wrote:
Johan Hovold jo...@kernel.org writes:
This is a non-standard attribute of this particular laptop. It has three
individual LEDs that can be enabled separately (using standard LED class
attributes), but they will all three be in
On Tue, Jun 24, 2014 at 1:54 PM, Kamil Debski k.deb...@samsung.com wrote:
The Exynos4412 USB 2.0 PHY hardware differs from the description provided
in the documentation. Some register bits have different function. This
patch fixes the defines of register bits and changes the way how phys are
Hi Daniel,
From: Daniel Drake [mailto:dr...@endlessm.com]
Sent: Tuesday, June 24, 2014 5:09 PM
On Tue, Jun 24, 2014 at 1:54 PM, Kamil Debski k.deb...@samsung.com
wrote:
The Exynos4412 USB 2.0 PHY hardware differs from the description
provided in the documentation. Some register bits
On Tue, 2014-06-24 at 10:15 -0400, Alan Stern wrote:
The default value for the persist facility depends on the setting of
CONFIG_USB_DEFAULT_PERSIST. If that symbol is set then persist is
enabled by default for all devices, except those which have the
USB_QUIRK_RESET flag set (meaning that
On Tue, 2014-06-24 at 10:25 -0400, Alan Stern wrote:
Also, that Later kernels thing has already arrived. I believe it was
implemented in 2.6.35.
How does the kernel currently call the disconnect method? I can't yet
say for sure, and it seems silly to send a v2 dropping those lines
without
On Tue, Jun 24 2014, Robert Baldyga r.bald...@samsung.com wrote:
Add missing information about license. Some people will probably want
to reuse this code in their projects released under variety of
licenses. For this reason this example is under Public Domain license
to avoid GPL limitations.
On Tue, 24 Jun 2014, Paul Bolle wrote:
On Tue, 2014-06-24 at 10:15 -0400, Alan Stern wrote:
The default value for the persist facility depends on the setting of
CONFIG_USB_DEFAULT_PERSIST. If that symbol is set then persist is
enabled by default for all devices, except those which have
On Tue, 24 Jun 2014, Paul Bolle wrote:
On Tue, 2014-06-24 at 10:25 -0400, Alan Stern wrote:
Also, that Later kernels thing has already arrived. I believe it was
implemented in 2.6.35.
How does the kernel currently call the disconnect method? I can't yet
say for sure, and it seems silly
Takashi and Clemens:
The snd-usb-audio driver has a race between close and disconnect. A
patch I have been testing reliably triggers this race on my machine and
reveals a use-after-free bug.
This happens when a device is disconnected while being used for audio
I/O. Simply unplugging the
On Fri, 20 Jun 2014, Dennis New wrote:
However, lsusb does not work, and I cannot kill it -- it remains in D
(uninterruptible sleep) state. I am also unable to rmmod the
snd_usb_audio module -- rmmod gets stuck in D state too.
When I tried echoing (:00:13.0) to ohci_pci/unbind,
Move led_mode attribute from HID device to led-class devices and rename it
msi_mode.
Signed-off-by: Janne Kanniainen janne.kanniai...@gmail.com
---
.../ABI/testing/sysfs-class-hid-driver-gt683r | 6 ++-
drivers/hid/hid-gt683r.c | 50 +-
2 files
This will fix race condition noticed by Oliver Neukum. Sysfs files are created
before mutex and work are initialized.
Signed-off-by: Janne Kanniainen janne.kanniai...@gmail.com
---
drivers/hid/hid-gt683r.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
On Tue, Jun 24, 2014 at 10:38:38PM +0300, Janne Kanniainen wrote:
Move led_mode attribute from HID device to led-class devices and rename it
msi_mode.
Signed-off-by: Janne Kanniainen janne.kanniai...@gmail.com
---
.../ABI/testing/sysfs-class-hid-driver-gt683r | 6 ++-
On Tue, Jun 24 2014, Robert Baldyga r.bald...@samsung.com wrote:
Since commit [ac8dde11: “Add flags to descriptors block”] functionfs
supports a new descriptor format, so we update example application
to make it using recomended version of descriptors.
Signed-off-by: Robert Baldyga
Hello.
On 06/10/2014 12:22 AM, Julius Werner wrote:
diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
index 9ffecd5..453d89e 100644
--- a/drivers/usb/host/xhci.h
+++ b/drivers/usb/host/xhci.h
@@ -1582,6 +1582,9 @@ struct xhci_hcd {
u32 port_status_u0;
From: Luis R. Rodriguez mcg...@suse.com
vub300 uses the request_firmware() API for downloading
pseudo code twice and if this fails its not considered fatal.
Avoid letting the request linger 60 seconds because of udev if
one of the requests fails by explicitly skipping the udev helper.
This was
On Wednesday, June 25, 2014 12:52 AM, Alvin Chen wrote:
From: Bryan O'Donoghue bryan.odonog...@intel.com
This patch is to enable USB host controller for Intel Quark X1000. Add pci
quirks
to adjust the packet buffer in/out threshold value, and ensure EHCI packet
buffer
i/o threshold
Hi Greg,
On Thu, May 29, 2014 at 12:33:42PM +0800, Pratyush ANAND wrote:
OTG3 and EH Compliance Plan 1.0 talks about Super Speed OTG Verification
system (SS-OVS) which consists of an excersizer and analyzer.
[...]
Signed-off-by: Pratyush Anand pratyush.an...@st.com
Acked-by: Alan Stern
Hi Torben,
On 6/24/2014 6:31 PM, Torben Hohn wrote:
On Wed, Jun 18, 2014 at 11:28:25AM +0200, Daniel Mack wrote:
Hi,
Hi Daniel,
I've been debugging issues with musb in host mode and both full-speed
and high-speed USB audio devices with cppi41 DMA mode enabled.
The effect that was observed
There might be 11 GPIOs in total.
Last three GPIOs (offsets 8-11, 0-based) are shared with FDX, LNKA, SPD
LEDs respectively. The LEDs are driven by chip by default at startup time.
Once the corresponding GPIO is requested, the chip LED drive logic is disabled.
Signed-off-by: Evgeny Boger
Hello,
On 2014-06-24 17:35, Kamil Debski wrote:
On Tue, Jun 24, 2014 at 1:54 PM, Kamil Debski k.deb...@samsung.com
wrote:
The Exynos4412 USB 2.0 PHY hardware differs from the description
provided in the documentation. Some register bits have different
function. This patch fixes the defines of
Hello Taeung,
On Tue, Jun 24, 2014 at 6:22 PM, Greg KH g...@kroah.com wrote:
On Tue, Jun 24, 2014 at 09:31:55PM +0900, Taeung wrote:
Hello, linux-usb
I have a question about USB 3.0.
Please help me.
I'm using SMDK5250 hardware and linux-3.0.31.
Why not try using a modern kernel
HI Sergei,
On Wed, Jun 25, 2014 at 4:04 AM, Sergei Shtylyov
sergei.shtyl...@cogentembedded.com wrote:
Hello.
On 06/10/2014 12:22 AM, Julius Werner wrote:
diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
index 9ffecd5..453d89e 100644
--- a/drivers/usb/host/xhci.h
+++
71 matches
Mail list logo
