On Sun, Nov 2, 2014 at 7:11 PM, Robert Jarzmik robert.jarz...@free.fr wrote:
In order to prepare device-tree conversion, port gpio_vbus to use
gpio_desc.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
Acked-by: Philipp Zabel philipp.za...@gmail.com
regards
Philipp
--
To unsubscribe
On Mon, Nov 03, 2014 at 11:46:09PM +0200, Janne Huttunen wrote:
On Wed, 29 Oct 2014 09:51:28 +0100
Johan Hovold jo...@kernel.org wrote:
Having the driver not reporting overrun (and other) errors will
obviously not fix the underlying issue with your device, which is
generating all these
Hi Robert,
On Sun, Nov 2, 2014 at 7:11 PM, Robert Jarzmik robert.jarz...@free.fr wrote:
Add documentation for device-tree binding of the generic gpio-vbus phy
controller.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
Cc: devicet...@vger.kernel.org
---
Hi Robert,
On Sun, Nov 2, 2014 at 7:11 PM, Robert Jarzmik robert.jarz...@free.fr wrote:
Add device-tree support for the generic gpio-vbus driver.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
Cc: devicet...@vger.kernel.org
---
drivers/usb/phy/phy-gpio-vbus-usb.c | 15 +++
Hello Riku,
Interesting, as the commit itself is a revert from a kernel back to 2.6
somewhere. The problem I had is related to the PHY being reset on
interface-up, can you confirm that you require this? Reverting this
breaks ethtool support in turn.
Kind regards,
Michel Stam
-Original
This reverts commit ff8cbf250b448aac35589f6075082c3fcad8a8fe.
Commit ff8cbf250b448aac35589f6075082c3fcad8a8fe triggers the bug logged at
https://bugzilla.kernel.org/show_bug.cgi?id=85701
Reported-by: Dmitry Nezhevenko d...@inhex.net
Signed-off-by: Lu Baolu baolu...@linux.intel.com
---
According to xHCI specification, PORT_DEV_REMOVE(bit 30) in PORTSC
true means Device is non-removable.
Reported-by: Juro Bystricky jurobystri...@hotmail.com
Signed-off-by: Lu Baolu baolu...@linux.intel.com
---
drivers/usb/host/xhci.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
2014-11-03 4:07 GMT+01:00 Chris Rorvick:
fusbh200: Make Xen notificaiton consistent with EHCI
fotg210: Make Xen notificaiton consistent with EHCI
you may want to fix the spelling: s/notificaiton/notification/
--
Daniele Forsi
--
To unsubscribe from this list: send the line unsubscribe
On Mon, Nov 03, 2014 at 10:59:59AM -0800, Benson Leung wrote:
On Mon, Nov 3, 2014 at 8:43 AM, Anton Staaf robot...@chromium.org wrote:
Add support for Google devices that export simple serial
interfaces using the vendor specific SubClass/Protocol pair
0x50/0x01.
Signed-off-by: Anton
This serie of patch reworks commit ff8cbf250b448aac35589f6075082c3fcad8a8fe.
This has been discussed at http://www.spinics.net/lists/linux-usb/msg114986.html
It also includes a patch to fix a comment in drivers/usb/host/xhci.h.
Changes in v2:
* Should not be a quirk.
* Should be applied to all
xhci: clear root port wake on bits if controller isn't wake-up capable
When system is being suspended, if host device is not wakeup capable,
xhci_suspend() needs to clear all root port wake on bits. Otherwise,
some platforms may generate spurious wakeup, even if PCI PME# is dis-
abled.
[added linux-usb@vger.kernel.org Cc]
Stephanie Wallick stephanie.s.wall...@intel.com writes:
Media Agnostic (MA) USB enables the USB protocol to be used over a wide
range of physical media. MA USB is a relatively new protocol and is
currently unsupported in the Linux kernel. This patch set
On Tue, Nov 04, 2014 at 09:19:26AM +0100, Stam, Michel [FINT] wrote:
Interesting, as the commit itself is a revert from a kernel back to 2.6
somewhere. The problem I had is related to the PHY being reset on
interface-up, can you confirm that you require this?
I can't confirm what exactly is
Some SoC's FPGA platform will need this quirk, but it will complain if
running at true SoC platform. This is a normal case, so remove this
warning.
Signed-off-by: Huang Rui ray.hu...@amd.com
---
Hi,
This patch is based on balbi/testing/next branch.
Thanks,
Rui
---
drivers/usb/dwc3/core.c | 3
On 10/31/2014 10:40 PM, Sergei Shtylyov wrote:
@@ -264,7 +265,14 @@ static void cppi41_dma_callback(void *private_data)
*/
controller = cppi41_channel-controller;
-if (musb-g.speed == USB_SPEED_HIGH) {
+if (is_host_active(musb)) {
+if
From: Todd Poynor toddpoy...@google.com
usb: phy: Hold wakeupsource when USB is enumerated in peripheral mode
Some systems require a mechanism to prevent system to enter into suspend
state when USB is connected and enumerated in peripheral mode.
This patch provides an interface to hold a
Hello Riku,
Fixing a bug (ethtool support) must not cause breakage elsewhere (in
this case on arndale). This is now a regression of functionality from
3.17.
I think it would better to revert the change now and with less hurry
introduce a ethtool fix that doesn't break arndale.
I don't fully
-Original Message-
From: Andrzej Pietrasiewicz [mailto:andrze...@samsung.com]
Sent: 2014年10月28日 21:10
To: Neil Zhang; linux-usb@vger.kernel.org; linux-ker...@vger.kernel.org
Cc: ba...@ti.com; gre...@linuxfoundation.org
Subject: Re: [PATCH] usb: gadget: don't create new
W dniu 04.11.2014 o 12:05, Neil Zhang pisze:
-Original Message-
From: Andrzej Pietrasiewicz [mailto:andrze...@samsung.com]
Sent: 2014年10月28日 21:10
To: Neil Zhang; linux-usb@vger.kernel.org; linux-ker...@vger.kernel.org
Cc: ba...@ti.com; gre...@linuxfoundation.org
Subject: Re: [PATCH]
Matthias Klein matthias.kl...@linux.com writes:
Am 02.11.2014 um 04:35 schrieb Lars Melin:
On 2014-11-01 23:01, Matthias Klein wrote:
Add ID of the Peiker LTE NAD for legacy serial interface
Signed-off-by: Matthias Klein matthias.kl...@linux.com
---
drivers/usb/serial/option.c | 1 +
1
Hi Greg,
On Mon, 3 Nov 2014 15:23:36 -0800
Greg KH gre...@linuxfoundation.org wrote:
On Sat, Oct 04, 2014 at 12:19:59PM +0100, Mark Knibbs wrote:
...
I see a bunch of patches from you in my queue, but I'm confused as to
which ones I should apply, and which I should ignore.
Can you
Hi,
Back in 2010 the default usb-storage delay_use time was reduced from 5 to 1
second (commit a4a47bc03fe520e95e0c4212bf97c86545fb14f9), but
kernel-parameters.txt wasn't updated to reflect that.
Signed-off-by: Mark Knibbs ma...@clara.co.uk
---
diff -upN
Hi,
Some mass storage devices return a bogus value in response to a Get Max LUN
request. The Iomega Jaz USB Adapter responds with 0x10, hence my recent
patch to use the US_FL_SINGLE_LUN quirk for it.
The USB MSC Bulk Only Transport document says The device shall return one
byte of data that
Hi,
The timeout argument to usb_stor_control_msg() is specified in jiffies, not
milliseconds.
Signed-off-by: Mark Knibbs ma...@clara.co.uk
---
v2: Add spaces, e.g. 5*HZ -- 5 * HZ
After the recent linux-usb mailing list thread usb_stor_control_msg()
timeout argument, the usb_control_msg()
usb_stor_euscsi_init() enables multi-target mode for SCM eUSB SCSI bridge
devices. The control message it sends has wLength = 1 and the byte sent is
0x01. While that works, the SCM Windows driver does it with wLength = 0. We
may as well match what the SCM driver does.
Signed-off-by: Mark Knibbs
Hi,
Entrega is misspelled as Entregra or Entrgra, so fix that.
Signed-off-by: Mark Knibbs ma...@clara.co.uk
---
v2 change: Fix spelling in usb-serial.txt too.
diff -uprN linux-3.17-rc7 linux-3.17-rc7.new
diff -uprN linux-3.17-rc7/Documentation/usb/usb-serial.txt
This patch does two things for SCM eUSCSI USB-SCSI converters:
1. SCM eUSCSI bridge devices are hard-wired to use SCSI ID 7. On connecting
the converter, access to that ID is attempted during the bus scan. Asking
the converter to issue INQUIRY commands to itself isn't very polite and
wastes
On Tue, Nov 04, 2014 at 05:29:51PM +0800, Huang Rui wrote:
Some SoC's FPGA platform will need this quirk, but it will complain if
running at true SoC platform. This is a normal case, so remove this
warning.
nope, why do you need disable_scramble on actual SoC ? Without an
erratum number I will
Hi,
I wanted to understand what is going on the kernel-side when
connecting to the Internet via a Huawei E173 USB web-stick (3rd
Generation: UMTS / HSPA).
Especially the correlation between the diverse USB/NET kernel-drivers
and how the networking is setup.
I have tested a Ubuntu trusty kernel
On Tue, 4 Nov 2014, James Bottomley wrote:
On Mon, 2014-11-03 at 16:06 -0500, Dale R. Worley wrote:
Was there any resolution as to how large disk drives would be handled
if their interface did not support the capacity request that would
tell how large they were?
Realistically no ...
Hi all,
was switched to other tasks last week and couldn't contribute.
Seems MUSB is also broken on OMAP3 boards, booting in OTG mode I'm not
able to make it work when a pendrive is connected to the port. Forcing
HOST mode I get following messages:
[ 13.244567] usb 2-1: new high-speed USB
The xhci platform driver needs to work on systems that either only
support 64-bit DMA or only support 32-bit DMA. Attempt to set a
coherent dma mask for 64-bit DMA, and attempt again with 32-bit
DMA if that fails.
Signed-off-by: Mark Langsdorf mlang...@redhat.com
Tested-by: Mark Salter
Provide the methods to let ACPI identify the need to use
xhci-platform. Change the Kconfig files so the
xhci-plat.o file is selectable during kernel config.
Signed-off-by: Mark Langsdorf mlang...@redhat.com
---
Changes from v1
Renamed from add support for APM X-Gene to xhci-platform
On Tue, 2014-11-04 at 16:11 +0100, Sedat Dilek wrote:
Hi,
I wanted to understand what is going on the kernel-side when
connecting to the Internet via a Huawei E173 USB web-stick (3rd
Generation: UMTS / HSPA).
Especially the correlation between the diverse USB/NET kernel-drivers
and how
On Tue, 4 Nov 2014, Lu Baolu wrote:
xhci: clear root port wake on bits if controller isn't wake-up capable
When system is being suspended, if host device is not wakeup capable,
xhci_suspend() needs to clear all root port wake on bits. Otherwise,
some platforms may generate spurious wakeup,
On Tue, Nov 04, 2014 at 10:50:33AM -0600, Mark Langsdorf wrote:
Provide the methods to let ACPI identify the need to use
xhci-platform. Change the Kconfig files so the
xhci-plat.o file is selectable during kernel config.
Signed-off-by: Mark Langsdorf mlang...@redhat.com
---
Changes from v1
On 11/03/2014 10:14 AM, Arnd Bergmann wrote:
On Monday 03 November 2014 09:15:51 Mark Salter wrote:
On Thu, 2014-10-30 at 22:05 +0100, Arnd Bergmann wrote:
You should definitely make sure that this also works with DT, as
I don't think it's possible to support X-Gene with ACPI. I know
that Al
On Tue, 4 Nov 2014 09:14:49 +0100
Johan Hovold jo...@kernel.org wrote:
2. The chip responds with single correct character followed by a few
hundred or so replies containing only the overrun status (no
data) which are then converted to a bunch of binary zeroes by the
ldisc because of the
On 04/11/14 00:24, Greg KH wrote:
On Tue, Oct 07, 2014 at 11:12:07AM +0200, Sylwester Nawrocki wrote:
The PLAT_S5P Kconfig symbol was removed in commit d78c16ccde96
(ARM: SAMSUNG: Remove remaining legacy code). There are still
some references left, fix that by replacing them with
I have two musb instances running in OTG. One instance is in device mode,
the other in host mode. I enable remote wakeup for both ports
(echo 1 /sys/…/power/wakeup). On leaving suspend I see that the root-hub
is resumed twice. I added a printk to hub_activate to see the device
name and
Use dma_addr_t to support 64-bit plaforms, which access beyond the default
32 bit address range.
Signed-off-by: Bao Truong btru...@apm.com
Signed-off-by: Feng Kan f...@apm.com
---
Changes:
V2: fixed GKH's comment regarding not mark up the comment after
code change.
On Tue, 4 Nov 2014, Sebastian Andrzej Siewior wrote:
I have two musb instances running in OTG. One instance is in device mode,
the other in host mode. I enable remote wakeup for both ports
(echo 1 /sys/…/power/wakeup). On leaving suspend I see that the root-hub
is resumed twice. I added a
On Tue, 2014-11-04 at 19:33 +0100, Sylwester Nawrocki wrote:
On 04/11/14 00:24, Greg KH wrote:
This isn't a stable issue...
Sorry for disturbing then, let me go and read the documentation again.
If I remember correctly, I asked Sylwester to mark this for stable. So
it's me that should be
On Tue, Nov 04, 2014 at 08:21:04PM +0100, Paul Bolle wrote:
On Tue, 2014-11-04 at 19:33 +0100, Sylwester Nawrocki wrote:
On 04/11/14 00:24, Greg KH wrote:
This isn't a stable issue...
Sorry for disturbing then, let me go and read the documentation again.
If I remember correctly, I
On Tue, 2014-11-04 at 11:42 -0800, Greg KH wrote:
As it's something that no one seemed to ever need before (i.e. it's not
a regression fix), but it would be a new feature, I don't think it's
really a stable fix.
But feel free to convince me otherwise :)
Sylwester, was I right in thinking
On Tue, Nov 04, 2014 at 11:23:06AM +0100, Stam, Michel [FINT] wrote:
Hello Riku,
Fixing a bug (ethtool support) must not cause breakage elsewhere (in
this case on arndale). This is now a regression of functionality from
3.17.
I think it would better to revert the change now and with less
On Fri, Oct 31, 2014 at 9:41 AM, Andrew Bresticker
abres...@chromium.org wrote:
On Fri, Oct 31, 2014 at 4:32 AM, Thierry Reding
thierry.red...@gmail.com wrote:
On Thu, Oct 30, 2014 at 10:26:47AM -0700, Andrew Bresticker wrote:
On Thu, Oct 30, 2014 at 10:24 AM, Thierry Reding
Philipp Zabel philipp.za...@gmail.com writes:
Hi Robert,
On Sun, Nov 2, 2014 at 7:11 PM, Robert Jarzmik robert.jarz...@free.fr wrote:
Maybe duplicate the comment from the driver here how his is about
B peripheral only devices
Yeah sure, for v2.
+Required properties:
+- compatible :
Hello linux-usb! I am the administrator of SANE (Scanner Access Now
Easy), which provides scanner drivers for over 1000 models of scanner
on multiple platforms, including Linux. Many of those scanners are
USB, and we have had an increase in bug reports in some of those as of
late. So, I have done
Hello Pratyush,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit a40178b2fa6ad87670fb1e5fa4024db00c149629
Author: Pratyush Anand pratyush.an...@st.com
Date: Fri Jul 18 12:37:10 2014 +0530
There is a typo (prove instead of probe) in the error message printed when
the platform initialization fails. Replace that word with more fitting init.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
---
The patch is against the 'usb-linus' branch of Greg KH's 'usb.git' repo.
On Wed, Nov 05, 2014 at 01:48:48AM +0300, Sergei Shtylyov wrote:
There is a typo (prove instead of probe) in the error message printed when
the platform initialization fails. Replace that word with more fitting init.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
this
Hello.
On 11/05/2014 01:53 AM, Felipe Balbi wrote:
There is a typo (prove instead of probe) in the error message printed when
the platform initialization fails. Replace that word with more fitting init.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
this actually goes
Hi,
On Wed, Nov 05, 2014 at 01:55:17AM +0300, Sergei Shtylyov wrote:
Hello.
On 11/05/2014 01:53 AM, Felipe Balbi wrote:
There is a typo (prove instead of probe) in the error message printed
when
the platform initialization fails. Replace that word with more fitting
init.
Now that ehci-dbgp has its own header, use it rather than duplicating
the declarations, etc.
Signed-off-by: Chris Rorvick ch...@rorvick.com
---
drivers/usb/host/fotg210.h | 40 ++--
1 file changed, 2 insertions(+), 38 deletions(-)
diff --git
Specifying these attributes in both the prototype and the function
definition is unnecessary and could cause confusion or bugs if they are
inconsistent. As such, __init should only be specified at the function
definition.
Keith Owens suggested this as a janitorial task on LKML several years
ago:
If CONFIG_XEN_DOM0 is enabled, the ehci-dbgp driver notifies Xen of
controller reset events via xen_dbgp_reset_prep() and
xen_dbgp_external_startup() (via calls to xen_dbgp_op().) Otherwise
linux/usb/ehci_def.h defines them as no-ops to disable this logic.
The fotg210 driver copies much of the
The FUSBH200 debug port has a EHCI-compatible register layout so there
is no need to define a custom struct.
Signed-off-by: Chris Rorvick ch...@rorvick.com
---
drivers/usb/host/fusbh200.h | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git
The FUSBH200 debug port has a EHCI-compatible register layout so there
is no need to define a custom struct.
Signed-off-by: Chris Rorvick ch...@rorvick.com
---
drivers/usb/host/fotg210.h | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/usb/host/fotg210.h
The fotg210_dbg_port struct is a copy of the ehci_dbg_port definition
in the linux/usb/ehci_def.h header. Embedded in this definition are
a number of macros which came along for the ride. These macros are not
used in the fotg210 driver and will conflict those in the new
linux/usb/ehci-dbgp.h
The FUSBH200 and FOTG210 are not EHCI-compatible and require standalone
drivers. See discussion at:
http://comments.gmane.org/gmane.linux.usb.general/84169
But these controllers do implement an EHCI-compatible debug port and
therefore leverage the ehci-dbgp driver. Rather than pulling in the
The fusbh200_dbg_port struct is a copy of the ehci_dbg_port definition
in the linux/usb/ehci_def.h header. Embedded in this definition are
a number of macros which came along for the ride. These macros are not
used in the fusbh200 driver and will conflict those in the new
linux/usb/ehci-dbgp.h
If CONFIG_XEN_DOM0 is enabled, the ehci-dbgp driver notifies Xen of
controller reset events via xen_dbgp_reset_prep() and
xen_dbgp_external_startup() (via calls to xen_dbgp_op().) Otherwise
linux/usb/ehci_def.h defines them as no-ops to disable this logic.
The fusbh200 driver copies much of the
The FUSBH200 and FOTG210 controllers implement sufficiently EHCI-
compatible debug ports to leverage ehci-dbgp from their respective
drivers. Rather than including linux/usb/ehci_def.h header, though,
they replicate the necessary declarations in their own headers. Move
the ehci-dbgp stuff into
Now that ehci-dbgp has its own header, use it rather than duplicating
the declarations, etc.
Signed-off-by: Chris Rorvick ch...@rorvick.com
---
drivers/usb/host/fusbh200.h | 40 ++--
1 file changed, 2 insertions(+), 38 deletions(-)
diff --git
[with a valid Message-ID]
On Tue, Nov 04, 2014 at 10:00:32AM +0100, Bjørn Mork wrote:
[added linux-usb@vger.kernel.org Cc]
Stephanie Wallick stephanie.s.wall...@intel.com writes:
Media Agnostic (MA) USB enables the USB protocol to be used over a wide
range of physical media. MA USB is a
On Mon, Nov 3, 2014 at 5:09 PM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
It deletes lines of code overall, which looks good to me. Feel free to
resend without the RFC and I will queue it up.
thanks,
greg k-h
Done.
I went through the patches by hand to double check spelling
Let the tasklet only be enabled after open(), and be disabled for
the other situation. The tasklet is only necessary after open() for
tx/rx, so it could be disabled by default.
Signed-off-by: Hayes Wang hayesw...@realtek.com
---
drivers/net/usb/r8152.c | 8 ++--
1 file changed, 6
On 11/5/2014 12:58 AM, Alan Stern wrote:
On Tue, 4 Nov 2014, Lu Baolu wrote:
xhci: clear root port wake on bits if controller isn't wake-up capable
When system is being suspended, if host device is not wakeup capable,
xhci_suspend() needs to clear all root port wake on bits. Otherwise,
some
On Tue, Nov 04, 2014 at 08:47:26AM -0600, Felipe Balbi wrote:
On Tue, Nov 04, 2014 at 05:29:51PM +0800, Huang Rui wrote:
Some SoC's FPGA platform will need this quirk, but it will complain if
running at true SoC platform. This is a normal case, so remove this
warning.
nope, why do you
This serie of patch reworks commit ff8cbf250b448aac35589f6075082c3fcad8a8fe.
This has been discussed at http://www.spinics.net/lists/linux-usb/msg114986.html
It also includes a patch to fix a comment in drivers/usb/host/xhci.h.
Changes in v3:
* Need to consider run-time suspend as well.
* Change
This reverts commit ff8cbf250b448aac35589f6075082c3fcad8a8fe.
Commit ff8cbf250b448aac35589f6075082c3fcad8a8fe triggers the bug logged at
https://bugzilla.kernel.org/show_bug.cgi?id=85701
Signed-off-by: Lu Baolu baolu...@linux.intel.com
Reported-by: Dmitry Nezhevenko d...@inhex.net
---
According to xHCI specification, PORT_DEV_REMOVE(bit 30) in PORTSC
true means Device is non-removable.
Signed-off-by: Lu Baolu baolu...@linux.intel.com
Reported-by: Juro Bystricky jurobystri...@hotmail.com
---
drivers/usb/host/xhci.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
xhci: clear root port wake on bits if controller isn't allowed to do wakeup
When system is being suspended, if host device is not allowed to do wakeup,
xhci_suspend() needs to clear all root port wake on bits. Otherwise, some
platforms may generate spurious wakeup, even if PCI PME# is disabled.
Hello Joe,
On Wed, Nov 05, 2014 at 06:20:06AM +0800, Joseph Salisbury wrote:
Hello Pratyush,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit a40178b2fa6ad87670fb1e5fa4024db00c149629
Split packet transactions are hidden. I could see them by clicking on
the (Show/Hide Split transactions) button. For INT IN, I could see
only Start Split packet.
I attached([2014-10-28 session 144012] Trace0003.rar) complete log for
this scenario.
How come the log doesn't contain
76 matches
Mail list logo
