On 07/28/2014 05:21 PM, Michal Nazarewicz wrote:
> OK, I see, I misunderstood your change before. So what you're saying is
> that now we have:
> 1. numbers user space provides in bEndpoindAddress,
> 2. physical addresses assigned when endpoint is configured, and
> 3. numbers for file names which g
I don't think this works. As I understand it, ep_ring->cycle_state
contains the current cycle state at the enqueue pointer, not the
dequeue pointer (it gets updated in inc_enq() but not in inc_deq() for
transfer rings). That's the only reason we need to pull it out of the
Endpoint Context at all...
single-ulpi-bypass is a flag used for older OMAP3 silicon.
The flag when set, can excite code that improperly uses the
OMAP_UHH_HOSTCONFIG_UPLI_BYPASS define to clear the corresponding bit.
Instead it clears all of the other bits disabling all of the ports in
the process.
Signed-off-by: Michael W
ти спечели деветстотин хиляди долара от Microsoft, изпратете име, държава и тел
Hi,
On 07/28/2014 10:31 PM, Laszlo T. wrote:
> I have some problems with Jmicron JMS567 (Sata 6 Gb/s -> USB3.0)
mobile rack.
>
> I tried on different kernels:
> 3.15.5
> 3.16.rc6
>
> I got the following errors when I ran a mkfs.ext4 command and then
the
>
On Mon, 28 Jul 2014, Laszlo T. wrote:
> > Laszlo, you can try specifying the "quirks=152d:0567:u" module
> > parameter for usb-storage. I don't know if that will help, but it
> > might.
> >
> >> What can the problem be?
> >
> > There's no way to tell from just this information.
> >
>
> Unfortuna
> Laszlo, you can try specifying the "quirks=152d:0567:u" module
> parameter for usb-storage. I don't know if that will help, but it
> might.
>
>> What can the problem be?
>
> There's no way to tell from just this information.
>
Unfortunately it did not help.
Is there any other information you ne
I have some problems with Jmicron JMS567 (Sata 6 Gb/s -> USB3.0)
>>> mobile rack.
I tried on different kernels:
3.15.5
3.16.rc6
I got the following errors when I ran a mkfs.ext4 command and then
>>> the
device disappeared.
Jul 26 19:54:37 debian ker
On Mon, Jul 28, 2014 at 12:57:39PM -0500, Michael Welling wrote:
> On Mon, Jul 28, 2014 at 10:57:18AM -0500, Felipe Balbi wrote:
> > Hi,
> >
> > On Mon, Jul 28, 2014 at 10:29:49AM -0500, Michael Welling wrote:
> > > On Mon, Jul 28, 2014 at 11:02:47AM -0400, Alan Stern wrote:
> > > > On Fri, 25 Jul
On Mon, Jul 28, 2014 at 10:57:18AM -0500, Felipe Balbi wrote:
> Hi,
>
> On Mon, Jul 28, 2014 at 10:29:49AM -0500, Michael Welling wrote:
> > On Mon, Jul 28, 2014 at 11:02:47AM -0400, Alan Stern wrote:
> > > On Fri, 25 Jul 2014, Michael Welling wrote:
> > >
> > > > The plot thickens
> > > >
>
On Mon, Jul 28, 2014 at 12:37:14PM -0400, Waiman Long wrote:
> I am planning to take out the check in check_deadlock and only have the test
> in lock_acquire which change a 3 to 2 when in interrupt context. Now my
> question is whether to do it as a new patch on top of the existing one in
> tip or
On 07/25/2014 12:10 PM, Peter Zijlstra wrote:
On Thu, Jul 24, 2014 at 04:38:28PM -0400, Waiman Long wrote:
Yes, I think I may have a solution for that.
Borislav, can you apply the following patch on top of the lockdep patch to
see if it can fix the problem?
diff --git a/kernel/locking/lockdep.
Hi,
On Mon, Jul 28, 2014 at 10:29:49AM -0500, Michael Welling wrote:
> On Mon, Jul 28, 2014 at 11:02:47AM -0400, Alan Stern wrote:
> > On Fri, 25 Jul 2014, Michael Welling wrote:
> >
> > > The plot thickens
> > >
> > > So if I run the above command before anything is plugged into the ports
>
On Mon, Jul 28, 2014 at 11:02:47AM -0400, Alan Stern wrote:
> On Fri, 25 Jul 2014, Michael Welling wrote:
>
> > The plot thickens
> >
> > So if I run the above command before anything is plugged into the ports
> > the HUB disconnects.
> >
> > root@som3517:~# echo on > /sys/bus/usb/devices/1-
Hi,
On 07/28/2014 04:50 PM, Oliver Neukum wrote:
> On Mon, 2014-07-28 at 10:48 -0400, Alan Stern wrote:
>> On Mon, 28 Jul 2014, Laszlo T. wrote:
>>
>>> Hello,
>>>
>>> I have some problems with Jmicron JMS567 (Sata 6 Gb/s -> USB3.0)
>> mobile rack.
>>>
>>> I tried on different kernels:
>>> 3.15.5
>
OK, I see, I misunderstood your change before. So what you're saying is
that now we have:
1. numbers user space provides in bEndpoindAddress,
2. physical addresses assigned when endpoint is configured, and
3. numbers for file names which go sequentially;
and what you want is to change the code so
On Fri, 25 Jul 2014, Michael Welling wrote:
> The plot thickens
>
> So if I run the above command before anything is plugged into the ports
> the HUB disconnects.
>
> root@som3517:~# echo on > /sys/bus/usb/devices/1-1/power/control
> [ 63.068839] usb 1-1: USB disconnect, device number 2
>
On Fri, Jul 25, 2014 at 10:01:52PM -0700, Greg KH wrote:
> On Fri, Jul 25, 2014 at 11:19:05AM -0500, Felipe Balbi wrote:
> > When we're debugging hard-to-reproduce and time-sensitive
> > use cases, printk() poses too much overhead. That's when
> > the kernel's tracing infrastructure comes into play
This commit adds PLL7 which is required for USBPHY1. It also adds
the USB PHY and USB Controller clocks and the gates to enable them.
Acked-by: Jingchang Lu
Signed-off-by: Stefan Agner
---
arch/arm/mach-imx/clk-vf610.c | 12 ++--
include/dt-bindings/clock/vf610-clock.h | 5 ++
This adds support for the USB PHY in Vybrid VF610. We assume that
the disconnection without VBUS is also needed for Vybrid.
Tests showed, without MXS_PHY_NEED_IP_FIX, enumeration of devices
behind a USB Hub fails with errors:
[ 215.163507] usb usb1-port1: cannot reset (err = -32)
[ 215.170498]
Add device tree node for usbmisc which controls the non-core USB
registers. This is required to use the property to disable the over-
current detection.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/vf610.dtsi | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git
This adds Vybrid VF610 SoC support. The IP is very similar to i.MX6,
however, the non-core registers are spread in two different register
areas. Hence we support multiple instances of the USB misc driver
and add the driver instance to the imx_usbmisc_data structure.
Signed-off-by: Stefan Agner
--
Add USB support for Colibri VF61 modules. The Colibri standard pinout
defines a pin for USB over-current. However, due to lack of pinmux
options, the USB hosts over-current protection signal of the Colibri
standard could not be connected to the PHY's over-current protection.
Hence we need to disabl
This adds USB PHY and USB controller nodes. Vybrid SoCs have two
independent USB cores which each supports DR (dual role). However,
real OTG is not supported since the OTG ID pin is not available.
The PHYs are located within the anadig register range, hence we need
to change the length of the anad
Add USB support for Freescale Vybrid tower. The USB hosts over-current
protection signal is not connected is not connected to the PHY's over-
current protection, hence we need to disable it.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/vf610-twr.dts | 10 ++
1 file changed, 10 inser
This patchset adds USB support for Vybrid VF610 SoC. It extends the
clock framework to support the USB PHY cocks, extends the device
tree files and adds support for the non-core registers in the
usbmisc_imx driver.
This patchset needs the eSDHC registers length fix available in
Shawn's for-next br
On Mon, 2014-07-28 at 10:48 -0400, Alan Stern wrote:
> On Mon, 28 Jul 2014, Laszlo T. wrote:
>
> > Hello,
> >
> > I have some problems with Jmicron JMS567 (Sata 6 Gb/s -> USB3.0)
> mobile rack.
> >
> > I tried on different kernels:
> > 3.15.5
> > 3.16.rc6
> >
> > I got the following errors when
On Mon, 28 Jul 2014, Laszlo T. wrote:
> Hello,
>
> I have some problems with Jmicron JMS567 (Sata 6 Gb/s -> USB3.0) mobile rack.
>
> I tried on different kernels:
> 3.15.5
> 3.16.rc6
>
> I got the following errors when I ran a mkfs.ext4 command and then the
> device disappeared.
>
> Jul 26 19:
On 07/27/2014 11:28 PM, Evan Langlois wrote:
> This is likely the same problem as the one I just posted about, but
> with 3.16 I get call traces and my USB bus came down and I couldn't
> even shut down the system. I've since gone back to my usual
> 3.13/Ubuntu kernel. Here's what happened. A sni
On Mon, 28 Jul 2014, Adam Borowski wrote:
> On Wed, Jul 23, 2014 at 11:19:06AM -0400, Alan Stern wrote:
> > > > Your system wakes up okay from suspend, but not from hibernation. Was
> > > > there ever any kernel version where USB wakeup from hibernation did
> > > > work?
> > >
> > > Any version
On 07/27/2014 11:21 PM, Evan Langlois wrote:
> Sorry if this is answered somewhere, but I couldn't find anything
> specific on Google as far as how to determine if this quirk is needed
> or if its configurable at boot/run-time. Its an HP laptop, and it
> looks like other HP models have the proble
When we manually need to move the TR dequeue pointer we need to set the
correct cycle bit as well. Previously we used the trb pointer from the
last event received as a base, but this was changed in Commit 1f81b6d22
to use the dequeue pointer from the endpoint context instead.
It turns out some Asm
Hello,
I have some problems with Jmicron JMS567 (Sata 6 Gb/s -> USB3.0) mobile rack.
I tried on different kernels:
3.15.5
3.16.rc6
I got the following errors when I ran a mkfs.ext4 command and then the
device disappeared.
Jul 26 19:54:37 debian kernel: [ 118.060026] usb 8-3: new high-speed
USB
Hi Roy,
On Mon, 2014-07-28 at 15:05 +0800, Roy wrote:
> Hi Dinh:
>
> Do you think it might be a problem of a un-aligned DMA buffer
> address? We know that the usbnet driver submits lots of URBs with a
> 2-byte aligned buffer address. But in Buffer DMA mode, the starting DMA
> address must be
Hi Dan,
Thank you very much for answer and support. I will try to merge your patchset
to Debian kernel source. When I will be successful then I will report the result
on my hardware. I hope that it will fix my problem. Have a nice day.
Regards,
Marek
-- Původní zpráva --
O
>> + do {
>> + if (cycle_found) {
>> + if (new_seg->trbs > cur_td->last_trb ||
>> + &new_seg->trbs[TRBS_PER_SEGMENT - 1] <
>> cur_td->last_trb)
>> + new_deq = &new_seg->trbs[TRBS_PER_SEGMENT -
>> 1];
On 07/28/2014 12:22 PM, Michal Nazarewicz wrote:
> On Mon, Jul 28 2014, Robert Baldyga wrote:
>> On 07/25/2014 04:18 PM, Michal Nazarewicz wrote:
>>> On Fri, Jul 25 2014, Robert Baldyga wrote:
This patch adds virtual endpoint address mapping to functionfs.
So far endpoint addresses
Remove redundant return statements at the end of void functions. This
addresses the checkpatch.pl warnings:
WARNING: void function return statements are not generally useful
#533: FILE: stub_rx.c:533:
+ return;
+}
#1125: FILE: vhci_hcd.c:1125:
+ return;
+}
#116: FILE: vhci_rx.c:116:
+
>> On Fri, Jul 25 2014, Robert Baldyga wrote:
>>> This patch introduces ioctl named FUNCTIONFS_ENDPOINT_DESC, which
>>> returns endpoint descriptor to userspace. It works only if function
>>> is active.
> On 07/25/2014 04:15 PM, Michal Nazarewicz wrote:
>> I would argue that user space should neve
On Mon, Jul 28 2014, Robert Baldyga wrote:
> On 07/25/2014 04:18 PM, Michal Nazarewicz wrote:
>> On Fri, Jul 25 2014, Robert Baldyga wrote:
>>> This patch adds virtual endpoint address mapping to functionfs.
>>>
>>> So far endpoint addresses given by user through endpoint descriptors
>>> were igno
On Thu, Jul 24, 2014 at 7:03 PM, Wang YanQing wrote:
> PL2303HX has two GPIOs, this patch add interface for it.
>
> Signed-off-by: Wang YanQing
> ---
> Changes v3-v4:
> 1: fix missing static for gpio_dir_mask and gpio_value_mask
> 2: reduce unneeded compile macro defined suggested by
> gno..
On Wed, Jul 23, 2014 at 11:19:06AM -0400, Alan Stern wrote:
> > > Your system wakes up okay from suspend, but not from hibernation. Was
> > > there ever any kernel version where USB wakeup from hibernation did work?
> >
> > Any version before c1db30a2a79eb59997b13b8cabf2a50bea9f04e1. That very
>
Hi Dinh:
Do you think it might be a problem of a un-aligned DMA buffer
address? We know that the usbnet driver submits lots of URBs with a
2-byte aligned buffer address. But in Buffer DMA mode, the starting DMA
address must be DWORD-aligned, only if turn on Descriptor DMA mode this
this 4-byte
Hi Dinh:
Do you think it might be a problem of a un-aligned DMA buffer
address? We know that the usbnet driver submits lots of URBs with a
2-byte aligned buffer address. But in Buffer DMA mode, the starting DMA
address must be DWORD-aligned, only if turn on Descriptor DMA mode this
4-byte alig
44 matches
Mail list logo
