Hello Peter and Greg,
On 01/06/2014 03:10 AM, Peter Chen wrote:
> According to Freescale imx28 Errata, "ENGR119653 USB: ARM to USB
> register error issue", All USB register write operations must
> use the ARM SWP instruction. So, we implement a special ehci_write
> for imx28.
>
> Discussion for i
Replace some tabs and modify the return value of rtl_ops_init().
v2: add the terminating newline for the message of patch #3.
Hayes Wang (3):
r8152: replace some tabs with spaces
r8152: move the actions of saving the information of the device
r8152: replace the return value of rtl_ops_init
Replace the tabs of the variables declaration with the spaces.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index 13fabbb..095f15b 100644
--- a/drivers/
Replace the boolean value with the error code for the return value
of the rtl_ops_init().
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index 861568
Some information of the device may be used in other functions. Move
the relative code to make sure it would be initialzed correctly
before using it.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/net/usb/r8
The netif_err() and netif_info() should have the terminating newline
at the end of the message.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index 5107372..3d8a565 1
hayeswang writes:
> Bjørn Mork [mailto:bj...@mork.no]
> [...]
>> Sorry, but then this makes even less sense. The active USB
>> configuration is user selectable and you should make any of
>> them work if
>> possible. Why can't the drivers figure out this at runtime?
>
> Excuse me. I have no id
> From: David Cohen
> On Fri, Dec 20, 2013 at 09:26:35AM -, David Laight wrote:
> > > From: David Cohen
> > The effect of this change is really to remove the first allocation and
> > add 8 bytes (or maybe a pointer) to the start of the second one.
> > So it is extremely unlikely to fail when th
Usted necesita para proteger la seguridad de su cuenta de correo electrónico,
con el fin de evitar la interrupción de sus servicios. Haga clic en siguiente
enlace para activar. http://utru.st/32
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to ma
Hi,
On Friday 20 December 2013 06:54 PM, Kamil Debski wrote:
Add a new driver for the Exynos USB 2.0 PHY. The new driver uses the generic
PHY framework. The driver includes support for the Exynos 4x10 and 4x12
SoC families.
Signed-off-by: Kamil Debski
Signed-off-by: Kyungmin Park
---
.../de
Hi,
On Friday 20 December 2013 06:54 PM, Kamil Debski wrote:
This the alternative version of the support for Exynos 421x USB 2.0 PHY
in the Generic PHY framework. In this version the support for Exynos
4210 and 4212 was joined into one file.
Signed-off-by: Kamil Debski
---
Hi,
Me and Kishon w
> From: walt
...
> /* Accept arbitrarily long scatter-gather lists */
> - hcd->self.sg_tablesize = ~0;
> + hcd->self.sg_tablesize = 31;
Even if that reduces the number of fragments passed to the xhci driver
it may not be enough to limit the actual number of fragments that
need
Hi Sarah,
On 01/03/2014 02:03 AM, Sarah Sharp wrote:
> Denis, do all of Compulab's Haswell systems reboot on shutdown? Are
> they all running a Phoenix BIOS? Can you send me the output of `sudo
> lspci -vvv -s` for the xHCI host?
oem@oem-Intense-PC2 ~ $ sudo lspci -vvv -s 00:14.0
00:14.0 USB co
On Mon, 6 Jan 2014, Ben Hutchings wrote:
> On Sat, 2014-01-04 at 05:44 +0800, jida...@jidanni.org wrote:
> > > "BH" == Ben Hutchings writes:
> > BH> And what were those error messages?
> > BH> Which USB devices are you using (this is probably disk or network
> > BH> related)?
> >
> > I had d
On Sun, Jan 05, 2014 at 11:04:39PM +, Hans de Goede wrote:
> Add support for ohci-platform instantiation from devicetree, including
> optionally getting clks and a phy from devicetree, and enabling / disabling
> those on power_on / off.
>
> This should allow using ohci-platform from devicetree
On Sun, Jan 05, 2014 at 11:04:40PM +, Hans de Goede wrote:
> Currently ehci-platform is only used in combination with devicetree when used
> with some via socs. By extending it to (optionally) get clks and a phy from
> devicetree, and enabling / disabling those on power_on / off, it can be used
> From: Alan Stern
> Subject: Re: Bug#733826: crazy loop "xhci_hcd Too many fragments"
>
> On Mon, 6 Jan 2014, Ben Hutchings wrote:
>
> > On Sat, 2014-01-04 at 05:44 +0800, jida...@jidanni.org wrote:
...
> > > # cat /var/log/syslog
> > >
> > > Jan 1 06:57:38 jidanni5 ntpd[2822]: Listen normally
On Mon, 6 Jan 2014, Hans de Goede wrote:
> Add support for ohci-platform instantiation from devicetree, including
> optionally getting clks and a phy from devicetree, and enabling / disabling
> those on power_on / off.
>
> This should allow using ohci-platform from devicetree in various cases.
>
On Monday 06 January 2014, Hans de Goede wrote:
> On 01/06/2014 08:16 AM, Arnd Bergmann wrote:
> > On Monday 06 January 2014, Hans de Goede wrote:
> >> +Required properties:
> >> + - compatible: Should be "platform-ohci"
> >> + - reg: Address range of the ohci registers.
> >> + - interrupts: Should
The existing serial state notification handling expected older Option
devices, having a hardcoded assumption that the Modem port was always
USB interface #2. That isn't true for devices from the past few years.
hso_serial_state_notification is a local cache of a USB Communications
Interface Class
Genuine FTDI chips support only CS7/8. A previous fix enforced this
limitation and reported it back to userspace.
However, certain types of smartcard readers depend on specific
driver behaviour that requests 0 data bits (not 5) to change into a
different operating mode if CS5 has been set.
This p
Hello everyone,
I received a bug report, that at least one type of smartcard reader fails to
work with the bugfix to the ftdi_sio driver of commit
caf2e52920cddef72922cbe7c2140e5d3a690bc6 .
It's likely that the device doesn't use a genuine FTDI chip, but implements the
protocol instead and abu
Hi,
Apologies for the late reply, I wasn't able to access my mail much over
the Christmas break.
On Mon, Dec 23, 2013 at 08:25:49PM +, Andreas Larsson wrote:
> This adds an UDC driver for GRUSBDC USB Device Controller cores available in
> the
> GRLIB VHDL IP core library. The driver only sup
On Mon, Jan 06, 2014 at 03:52:24PM +, David Laight wrote:
> > From: Alan Stern
> > Subject: Re: Bug#733826: crazy loop "xhci_hcd Too many fragments"
> >
> > On Mon, 6 Jan 2014, Ben Hutchings wrote:
> >
> > > On Sat, 2014-01-04 at 05:44 +0800, jida...@jidanni.org wrote:
> ...
> > > > # cat /va
On Fri, Jan 03, 2014 at 04:49:16PM -0800, Greg KH wrote:
> On Fri, Jan 03, 2014 at 04:22:45PM -0800, Sarah Sharp wrote:
> > Occasionally when a USB 3.0 device is disconnected, the roothub port
> > goes into the SS.Inactive state, rather than reporting a disconnect.
>
> Is that a hardware bug? Or
Boris,
On Mon, Dec 9, 2013 at 12:51 AM, Boris BREZILLON
wrote:
> Replace the request_mem_region + ioremap calls by the
> devm_ioremap_resource call which does the same things but with device
> managed resources.
>
> Signed-off-by: Boris BREZILLON
> Acked-by: Nicolas Ferre
> Signed-off-by: Alan
On Mon, 2014-01-06 at 17:19 +0800, Hayes Wang wrote:
> The netif_err() and netif_info() should have the terminating newline
> at the end of the message.
dev_ uses also need terminating newlines.
Perhaps it's a bit more comprehensive to convert the
pr__ratelimited uses to use net_ratelimit and
net
On Sat, Jan 04, 2014 at 12:09:27PM -0500, Alan Stern wrote:
> On Fri, 3 Jan 2014, Sarah Sharp wrote:
>
> > Occasionally when a USB 3.0 device is disconnected, the roothub port
> > goes into the SS.Inactive state, rather than reporting a disconnect. A
> > warm reset is the only way to get out of t
Holger Hans Peter Freyther writes:
Happy New Year,
> xhci_hcd does not work with the Canon Lide scanners and has issues
> with the suspend/resume handling. My Acer Aspire S5 notebook only
> exposes USB3.0 ports and the distribution kernels generally have
> xhci_hcd enabled and I don't have any
On Mon, Jan 06, 2014 at 06:58:01PM +, Holger Freyther wrote:
> Holger Hans Peter Freyther writes:
>
> Happy New Year,
>
>
> > xhci_hcd does not work with the Canon Lide scanners and has issues
> > with the suspend/resume handling. My Acer Aspire S5 notebook only
> > exposes USB3.0 ports and
On Mon, Jan 06, 2014 at 05:35:57PM +0100, Colin Leitner wrote:
> Genuine FTDI chips support only CS7/8. A previous fix enforced this
> limitation and reported it back to userspace.
Please include the commit id of the offending commit when fixing
regressions. In this case, you'd refer to commit 870
Genuine FTDI chips support only CS7/8. A previous fix in commit 8704211f65a2
enforced this limitation and reported it back to userspace.
However, certain types of smartcard readers depend on specific
driver behaviour that requests 0 data bits (not 5) to change into a
different operating mode if CS
On Mon, Jan 06, 2014 at 10:06:33AM -0500, Alan Stern wrote:
> On Mon, 6 Jan 2014, Ben Hutchings wrote:
>
> > On Sat, 2014-01-04 at 05:44 +0800, jida...@jidanni.org wrote:
> > > > "BH" == Ben Hutchings writes:
> > > BH> And what were those error messages?
> > > BH> Which USB devices are you us
Hello Olof,
On 06/01/2014 19:08, Olof Johansson wrote:
Boris,
On Mon, Dec 9, 2013 at 12:51 AM, Boris BREZILLON
wrote:
Replace the request_mem_region + ioremap calls by the
devm_ioremap_resource call which does the same things but with device
managed resources.
Signed-off-by: Boris BREZILLON
On Mon, Jan 06, 2014 at 08:35:08PM +0100, Colin Leitner wrote:
> Genuine FTDI chips support only CS7/8. A previous fix in commit 8704211f65a2
> enforced this limitation and reported it back to userspace.
You should keep the one-line description in parentheses after the sha-id
as in my example.
Th
Hi Johan
> I'll just fix this up this time and submit it to Greg.
thanks! I promise to up my game in git usage for the next patch ;).
-Colin
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http:
On Mon, Jan 06, 2014 at 09:29:57PM +0100, Colin Leitner wrote:
> Hi Johan
>
> > I'll just fix this up this time and submit it to Greg.
>
> thanks! I promise to up my game in git usage for the next patch ;).
Sounds good. :)
Thanks for fixing this.
Johan
--
To unsubscribe from this list: send th
From: Colin Leitner
Genuine FTDI chips support only CS7/8. A previous fix in commit
8704211f65a2 ("USB: ftdi_sio: fixed handling of unsupported CSIZE
setting") enforced this limitation and reported it back to userspace.
However, certain types of smartcard readers depend on specific
driver behavi
From: Hayes Wang
Date: Mon, 6 Jan 2014 17:08:40 +0800
> Replace some tabs and modify the return value of rtl_ops_init().
>
> v2: add the terminating newline for the message of patch #3.
Series applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a mess
From: Dan Williams
Date: Mon, 06 Jan 2014 10:07:29 -0600
> The existing serial state notification handling expected older Option
> devices, having a hardcoded assumption that the Modem port was always
> USB interface #2. That isn't true for devices from the past few years.
>
> hso_serial_state_
On Mon, 2014-01-06 at 16:30 -0500, David Miller wrote:
> From: Dan Williams
> Date: Mon, 06 Jan 2014 10:07:29 -0600
>
> > The existing serial state notification handling expected older Option
> > devices, having a hardcoded assumption that the Modem port was always
> > USB interface #2. That isn
From: Dan Williams
Date: Mon, 06 Jan 2014 15:39:40 -0600
> If the driver ever gets to that callback for any !Modem port, something
> is horribly wrong, which the BUG_ON() was attempting to make explicit.
> The driver only enables that callback for the Modem port, so yeah, it's
> somewhat defensiv
Dan, can you test this patch, on top of the other patch that Ben sent?
There's directions for building a custom kernel here, if you need it:
http://kernelnewbies.org/KernelBuild
I suggest either getting the Debian kernel source and patching that, or
patching 3.12.6 or later.
Sarah Sharp
8<-
On Mon, 6 Jan 2014, Felipe Balbi wrote:
> On Mon, Jan 06, 2014 at 06:58:01PM +, Holger Freyther wrote:
> > Holger Hans Peter Freyther writes:
> >
> > Happy New Year,
> >
> >
> > > xhci_hcd does not work with the Canon Lide scanners and has issues
> > > with the suspend/resume handling. My
Don't worry, I'll trust you! Plus I'm 53.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Jan 03, 2014 at 03:29:29PM -0800, Sarah Sharp wrote:
> On Fri, Jan 03, 2014 at 01:21:18PM -0800, walt wrote:
> > I'm so sorry Sarah, that was another mistake. The mistake is so stupid I'm
> > not
> > going to publish it here :(
> >
> > Once I finally ran the kernel with debugging actuall
We have met a bug that the high bandwidth ISO-TX transfer has failed
at the last packet if it is less than 1024, the TD status shows it
is "Transaction Error".
The root cause of this problem is: the mult value at qh is not correct
for current TD's transfer length. We use TD list to queue un-transf
We have met a bug that the high bandwidth ISO-TX transfer has failed
at the last packet if it is less than 1024, the TD status shows it
is "Transaction Error".
The root cause of this problem is: the mult value at qh is not correct
for current TD's transfer length. We use TD list to queue un-transf
When CONFIG_PCI and CONFIG_PM are not selected, xhci.c gets this
warning:
drivers/usb/host/xhci.c:409:13: warning: ‘xhci_msix_sync_irqs’ defined
but not used [-Wunused-function]
Instead of creating nested #ifdefs, this patch fixes it by defining the
xHCI PCI stubs as inline.
Signed-off-by: David
> Hello Peter and Greg,
>
> On 01/06/2014 03:10 AM, Peter Chen wrote:
> > According to Freescale imx28 Errata, "ENGR119653 USB: ARM to USB
> > register error issue", All USB register write operations must
> > use the ARM SWP instruction. So, we implement a special ehci_write
> > for imx28.
> >
>
set hub->change_bits when we plug in a device which causes
over-current condition, so that hub_events() will check it.
Signed-off-by: Shen Guang
---
drivers/usb/core/hub.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
ind
On Tue, Jan 07, 2014 at 10:33:14AM +0800, 沈光 wrote:
> set hub->change_bits when we plug in a device which causes
> over-current condition, so that hub_events() will check it.
Why?
What does this solve? Is this a bug with existing devices that needs to
be backported to older kernels?
thanks,
gr
On Tue, 2014-01-07 at 07:01 +0800, jida...@jidanni.org wrote:
> Don't worry, I'll trust you! Plus I'm 53.
I don't think anyone else has reproduced this problem, so you are the
person in the best place to check that these changes really fix it.
You can test patches against the Debian kernel packag
When CONFIG_PCI and CONFIG_PM are not selected, xhci.c gets this
warning:
drivers/usb/host/xhci.c:409:13: warning: ‘xhci_msix_sync_irqs’ defined
but not used [-Wunused-function]
It happens due to lack of __maybe_unused flag on xhci_msix_sync_irqs()
function in case of !CONFIG_PCI.
Signed-off-by:
- Replace pr_warn_ratelimited() with net_ratelimit() and netdev_warn().
- Adjust the algnment of some messages.
- Remove the peroid.
- Fix some messages don't have terminating newline.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 23 +--
1 file changed, 13 inse
On Tue, Jan 7, 2014 at 10:40 AM, Greg KH wrote:
> On Tue, Jan 07, 2014 at 10:33:14AM +0800, 沈光 wrote:
>> set hub->change_bits when we plug in a device which causes
>> over-current condition, so that hub_events() will check it.
>
> Why?
>
> What does this solve? Is this a bug with existing devices
On Tue, Jan 07, 2014 at 11:35:50AM +0800, 沈光 wrote:
> On Tue, Jan 7, 2014 at 10:40 AM, Greg KH wrote:
> > On Tue, Jan 07, 2014 at 10:33:14AM +0800, 沈光 wrote:
> >> set hub->change_bits when we plug in a device which causes
> >> over-current condition, so that hub_events() will check it.
> >
> > Why
On Mon, Jan 06, 2014 at 09:26:20AM +, David Laight wrote:
> > From: David Cohen
> > On Fri, Dec 20, 2013 at 09:26:35AM -, David Laight wrote:
> > > > From: David Cohen
> > > The effect of this change is really to remove the first allocation and
> > > add 8 bytes (or maybe a pointer) to the
From: Hayes Wang
Date: Tue, 7 Jan 2014 11:18:22 +0800
> - Replace pr_warn_ratelimited() with net_ratelimit() and netdev_warn().
> - Adjust the algnment of some messages.
> - Remove the peroid.
> - Fix some messages don't have terminating newline.
>
> Signed-off-by: Hayes Wang
I only want m
On Tue, Jan 7, 2014 at 11:53 AM, Greg KH wrote:
> On Tue, Jan 07, 2014 at 11:35:50AM +0800, 沈光 wrote:
>> On Tue, Jan 7, 2014 at 10:40 AM, Greg KH wrote:
>> > On Tue, Jan 07, 2014 at 10:33:14AM +0800, 沈光 wrote:
>> >> set hub->change_bits when we plug in a device which causes
>> >> over-current con
On Mon, Jan 06, 2014 at 04:44:51PM -0500, Alan Stern wrote:
> Finally, blacklisting xhci-hcd won't solve the problem at hand, because
> the ports get switched from EHCI to xHCI during early PCI processing,
> before xhci-hcd is loaded. The only check is for whether
> CONFIG_USB_XHCI_HCD is enabled
61 matches
Mail list logo
