Hi,
On 05/25/2015 03:30 AM, fx IWATA NOBUO wrote:
Hello,
I see your point and what you have done in patches.
I'm only showing you that you may achieve almost the same effect
without any changes in kernel.
I tested wstunnel.
The performance comparison in my environment is as following.
Round
Alan Stern writes:
> > I feel that this person ins't at time maintaining this source code.
>
> You seem to be right, since his email address doesn't work any more.
>
> > I'm suposing that this mailing list is readed by very competent
people
> > that can implement this "simple" change. I hope
On 05/23/2015 10:00 PM, Donald Harter wrote:
May 23 08:52:05 pc_u kernel: [53875.075976] xhci_hcd :00:14.0:
Port Status Change Event for port 3
May 23 08:52:05 pc_u kernel: [53875.075979] xhci_hcd :00:14.0:
port resume event for port 3
May 23 08:52:05 pc_u kernel: [53875.075981] xhci_h
Hi,
> Why do we even need that? If you take patch that makes ulpi_init a
> subsys_initcall you won't have this problem, and no additional weird
> hacks and errors will be needed
Using subsys_initcall will work around the problem for now, but I
would not make the assumption that there will never b
On Thu, 21 May 2015, Herton R. Krzesinski wrote:
> I received a report from an user of following mouse which needs this quirk:
>
> usb 1-1.6: USB disconnect, device number 58
> usb 1-1.6: new low speed USB device number 59 using ehci_hcd
> usb 1-1.6: New USB device found, idVendor=04f2, idProduct
On Fri, May 22, 2015 at 09:08:45AM -0700, David Cohen wrote:
> Hi,
>
> On Fri, May 22, 2015 at 07:29:15PM +0800, Lu Baolu wrote:
> > Phy drivers and the ulpi interface providers depend on the
> > registeration of the ulpi bus. Ulpi registers the bus in
> > module_init(). This could result in a lo
Hi Felipe
On Mon, May 18, 2015 at 05:28:58PM +0200, Michael Trimarchi wrote:
> Not checking config_ep_by_speed could lead to a kernel
> NULL pointer dereference error in usb_ep_enable
>
> Cc: Felipe Balbi
> Signed-off-by: Michael Trimarchi
>
> ---
>
> v2:
> - fix mail subject
> - add descript
On Mon, 25 May 2015, Rong Wang wrote:
> On Fri, May 22, 2015 at 10:06 PM, Alan Stern
> wrote:
> > On Fri, 22 May 2015, Rong Wang wrote:
> >
> >> Hi,
> >>
> >> We have one USB 2.0 Controller on an ARM SoC, with internal PHY
> >> confirming to UTMI.
> >> The PHY would detect unexpected disconnect
On Mon, 25 May 2015, Golmer Palmer wrote:
> Alan Stern writes:
>
> > > I feel that this person ins't at time maintaining this source code.
> >
> > You seem to be right, since his email address doesn't work any more.
> >
> > > I'm suposing that this mailing list is readed by very competent
> p
When looking up a phy through its DT node, ensure that the corresponding
device has been registered.
Signed-off-by: Tomeu Vizoso
---
drivers/usb/phy/phy.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/phy/phy.c b/drivers/usb/phy/phy.c
index d1cd6b5..7084f21 100644
--- a/driv
I've been testing add/remove HCD extensively and didn't observe any issues
after applying
these 5 patches. Well there is one issue that comes up but it has nothing
to do with xhci
not being allocated. It has more to do with command being queued after the
HCD ha
Hello,
I have a problem with the panel on my Tegra Chromebook taking longer than
expected to be ready during boot (Stéphane Marchesin reported what is
basically the same issue in [0]), and have looked into ordered probing as a
better way of solving this than moving nodes around in the DT or playin
On Mon, May 25, 2015 at 02:40:10PM +0300, Heikki Krogerus wrote:
> Hi,
>
> > Why do we even need that? If you take patch that makes ulpi_init a
> > subsys_initcall you won't have this problem, and no additional weird
> > hacks and errors will be needed
>
> Using subsys_initcall will work around t
On Mon, May 25, 2015 at 05:51:06AM +, Badola Nikhil wrote:
> > -Original Message-
> > From: Greg KH [mailto:g...@kroah.com]
> > Sent: Monday, September 29, 2014 11:56 AM
You are responding to a very old email, why?
> > On Mon, Sep 29, 2014 at 03:46:02AM +, nikhil.bad...@freescale.
Greg KH writes:
> If there are other bus drivers that do this, I'll go fix them up,
> pointers to those files would be appreciated.
git grep -E 'if .*\.p\W' found a couple of interesting candidates you
might want to check out:
drivers/i2c/i2c-core.c: if (unlikely(WARN_ON(!i2c_bus_type.p))) {
[1.] One line summary of the problem:
USB drive errors with newer kernel versions
[2.] Full description of the problem/report:
I am seeing various USB drive errors while trying to use the drives with later
versions of the kernel.
I have tested with 4.1-rc5 and still see the issues.
For insta
Yes, this fixed the problem. Thanks for your help.
Here is the kernel version that I compiled:
Linux 4.1.0-rc2+ #2 SMP Mon May 25 10:58:36 CDT 2015 x86_64 x86_64
x86_64 GNU/Linux
On the non-working generic ubuntu kernel,the USB 3.0 ports that time out
became non-working. I could plug my oth
On 15-05-14 05:52 PM, Felipe Balbi wrote:
Hi,
On Wed, Apr 22, 2015 at 04:04:10PM -0700, Arun Ramamurthy wrote:
Most of the phy providers use "select" to enable GENERIC_PHY. Since select
is only recommended when the config is not visible, GENERIC_PHY is changed
an invisible option. To maintain
Fix USB 3.0 devices lost in NOTATTACHED state after a hub port reset.
Dissolve the function hub_port_finish_reset() completely and divide the
actions to be taken into those which need to be done after each reset
attempt and those which need to be done after the full procedure is
complete, and plac
On 05/26/2015 03:06 AM, Donald Harter wrote:
Yes, this fixed the problem. Thanks for your help.
That doesn't mean exactly that this change fixes your problem.
I would suggest you to try the latest kernel without any changes
to check whether the fix is already there. Then you can go ahead
wi
Hi,
> Maybe with other daemon or if you write your own one you will get
> better performance. It is obvious that it will never be as fast as
> dedicated implementation but the difference may be small enough.
Yes.
If there's any other trick other than TCP/IP loopback, please, let me
know.
Than
Hi Felipe,
> Sent: Monday, May 18, 2015 8:56 PM
>
> On Mon, May 18, 2015 at 1:04 PM, Yoshihiro Shimoda
> wrote:
> > This patch adds a compatible string to support for R-Car E2.
> >
> > Signed-off-by: Yoshihiro Shimoda
> > Acked-by: Geert Uytterhoeven " in patch 2
> > ---
> > Remarks: Geert's A
Hi Alan,
On Mon, May 25, 2015 at 10:16 PM, Alan Stern wrote:
> On Mon, 25 May 2015, Rong Wang wrote:
>
>> On Fri, May 22, 2015 at 10:06 PM, Alan Stern
>> wrote:
>> > On Fri, 22 May 2015, Rong Wang wrote:
>> >
>> >> Hi,
>> >>
>> >> We have one USB 2.0 Controller on an ARM SoC, with internal PHY
Hi,
On Saturday 23 May 2015 01:24 AM, Rob Herring wrote:
On Thu, May 21, 2015 at 7:51 AM, Kishon Vijay Abraham I wrote:
On Thursday 21 May 2015 06:15 PM, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 14 May 2015 04:18 AM, Rob Herring wrote:
Add PHY driver for the Marvell HSIC 28nm PHY. Th
24 matches
Mail list logo
