>> ...although, the spec says that it does not wait for the port resets
>> to complete. As far as I can see re-issuing a warm reset and waiting
>> is the only way to guarantee the core times the recovery. Presumably
>> the portstatus debounce in hub_activate() mitigates this, but that
>> 100ms is
Hi,
On Thursday 12 December 2013 03:27 AM, Graham Williams wrote:
> Hi Kishon,
>
> I see you have added this new generic phy framework. The usb phy framework
> contains a struct notifier_block to send usb specific events like
> USB_EVENT_ID. Will this new generic phy support notifications lik
Hi Robert,
[Repost with Bhupesh's hopefully correct e-mail address]
On Tuesday 10 December 2013 12:40:33 Robert Baldyga wrote:
> Hello,
>
> This patchset fixes UVC gadget test application, created by Laurent Pinchart
> (git tree available here: git://git.ideasonboard.org/uvc-gadget.git), with
>
Hi Robert,
On Tuesday 10 December 2013 12:40:33 Robert Baldyga wrote:
> Hello,
>
> This patchset fixes UVC gadget test application, created by Laurent Pinchart
> (git tree available here: git://git.ideasonboard.org/uvc-gadget.git), with
> applied patches created by Bhupesh Sharma (which can be fo
On Thu, Dec 12, 2013 at 02:20:59AM +0200, Grazvydas Ignotas wrote:
> This is a hard to reproduce problem which leads to non-functional
> USB-OTG port in 0.1%-1% of all boots. Tracked it down to commit
> e25bec160158abe86c "omap2+: save and restore OTG_INTERFSEL",
> which introduces save/restore of
This is a hard to reproduce problem which leads to non-functional
USB-OTG port in 0.1%-1% of all boots. Tracked it down to commit
e25bec160158abe86c "omap2+: save and restore OTG_INTERFSEL",
which introduces save/restore of OTG_INTERFSEL over suspend.
Since the resume function is also called early
On Wed, Dec 11, 2013 at 2:51 PM, Dan Williams wrote:
> On Wed, Dec 11, 2013 at 11:36 AM, Sarah Sharp
> wrote:
>> On Wed, Dec 11, 2013 at 11:00:13AM -0800, Julius Werner wrote:
>>> > I don't know what you mean by "fails". The system goes to sleep and
>>> > then later on wakes up, doesn't it?
>>>
On Wed, Dec 11, 2013 at 11:03:09AM -0500, Alan Stern wrote:
> On Tue, 10 Dec 2013, Sarah Sharp wrote:
> > On 3.13-rc1, the btrfs partion from the disconnected USB device
> > continues to be listed as mounted. Yanking the cable produces some
> > additional oops messages. It also produced a couple
On Wednesday, December 11, 2013 5:13 PM, Nicolas Ferre wrote:
> On 11/12/2013 08:31, Jingoo Han :
> > Use devm_*() functions to make cleanup paths simpler.
> >
> > Signed-off-by: Jingoo Han
>
> Jingoo,
>
> Well, these modifications are already addressed by a series written by
> Boris.
> "[PATCH
On Wed, Dec 11, 2013 at 11:36 AM, Sarah Sharp
wrote:
> On Wed, Dec 11, 2013 at 11:00:13AM -0800, Julius Werner wrote:
>> > I don't know what you mean by "fails". The system goes to sleep and
>> > then later on wakes up, doesn't it?
>> >
>> > Do you mean that the Jetflash device gets disconnected
Hi Kishon,
I see you have added this new generic phy framework. The usb phy framework
contains a struct notifier_block to send usb specific events like USB_EVENT_ID.
Will this new generic phy support notifications like the usb phy? Also will
set_power() and set_vbus() ops get added? Or shou
On Wed, Dec 11, 2013 at 11:00:13AM -0800, Julius Werner wrote:
> > I don't know what you mean by "fails". The system goes to sleep and
> > then later on wakes up, doesn't it?
> >
> > Do you mean that the Jetflash device gets disconnected when the system
> > wakes up? That's _supposed_ to happen u
> Sorry for not getting back to this sooner. Ironically, it looks like
> this change isn't needed any more, thanks to Thomas Pugliese's patch:
>
> http://marc.info/?l=linux-usb&m=13866180520&w=2
Yes... thanks for pointing it out, that would make this patch
obsolete. I'll wait a few da
> I don't know what you mean by "fails". The system goes to sleep and
> then later on wakes up, doesn't it?
>
> Do you mean that the Jetflash device gets disconnected when the system
> wakes up? That's _supposed_ to happen under those circumstances.
> When hub_activate() sees HUB_RESET_RESUME, al
On Wed, Dec 11, 2013 at 04:16:33PM +0900, Jingoo Han wrote:
> Use devm_*() functions to make cleanup paths simpler.
>
> Signed-off-by: Jingoo Han
> ---
> drivers/usb/host/ehci-orion.c | 43
> -
> 1 file changed, 12 insertions(+), 31 deletions(-)
Acked-
On Tue, 10 Dec 2013, Vikas Sajjan wrote:
> > Finally, I don't see why you put this in hub_activate(). Isn't it more
> > closely connected with the reset-resume procedure for the child device?
>
>
> I was trying to add a FIX in usb_port_resume(), but in our case we
> have CONFIG_USB_DEFAULT_PERS
From: Freddy Xin
Date: Wed, 11 Dec 2013 14:17:59 +0800
> I think there is no way of undoing the reservation in the driver.
Then you should add a flag that, indeed, tells usbnet not to do the
reservation in the first place.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" i
On Thu, 5 Dec 2013, Julius Werner wrote:
> usb_deauthorize_device() tries to unset the configuration of a USB
> device and then unconditionally blows away the configuration descriptors
> with usb_destroy_configuration(). This is bad if the
> usb_set_configuration() call failed before the configura
On Wed, Dec 11, 2013 at 11:03:09AM -0500, Alan Stern wrote:
> On Tue, 10 Dec 2013, Sarah Sharp wrote:
>
> > In order to stress test the uas driver (next-gen USB storage driver), I
> > decided to run some tests with a USB 3.0 storage device with four 10GB
> > partitions: BTRFS, ext3, ext4, and fat3
On Wed, 11 Dec 2013, Eugene Shatokhin wrote:
> Hi,
>
> On ROSA Linux with kernel 3.10.21 with DMA debug options enabled, the
> kernel sometimes issues a warning about DMA pool corruption (see the log
> below).
>
> That happens sometimes, when the system boots or resumes from
> hibernation wit
On Wed, 11 Dec 2013, Robert Baldyga wrote:
> This patch adds "maxpacket_limit" to struct usb_ep. This field contains
> maximum value of maxpacket supported by driver, and is set in driver probe.
> This value should be used by autoconfig() function, because value of field
> "maxpacket" is set to va
On Tue, 10 Dec 2013, Sarah Sharp wrote:
> In order to stress test the uas driver (next-gen USB storage driver), I
> decided to run some tests with a USB 3.0 storage device with four 10GB
> partitions: BTRFS, ext3, ext4, and fat32.
>
> It seems that BTRFS doesn't handle unexpected USB disconnect v
On Thu, Dec 05, 2013 at 01:29:35PM +0100, Kamil Debski wrote:
> Change the used phy driver to the new Exynos USB phy driver that uses the
> generic phy framework.
>
> Signed-off-by: Kamil Debski
> Signed-off-by: Kyungmin Park
> ---
> .../devicetree/bindings/usb/samsung-hsotg.txt |4 +++
Hi,
On ROSA Linux with kernel 3.10.21 with DMA debug options enabled, the
kernel sometimes issues a warning about DMA pool corruption (see the log
below).
That happens sometimes, when the system boots or resumes from
hibernation with Samson C01U USB microphone attached.
The affected DMA po
This patch adds "maxpacket_limit" to struct usb_ep. This field contains
maximum value of maxpacket supported by driver, and is set in driver probe.
This value should be used by autoconfig() function, because value of field
"maxpacket" is set to value from endpoint descriptor when endpoint becomes
e
> From: Freddy Xin
> On 2013年12月10日 09:01, David Miller wrote:
> > From: fre...@asix.com.tw
> > Date: Fri, 6 Dec 2013 17:58:18 +0800
> >
> >> From: Freddy Xin
> >>
> >> The AX88179_178A has a hardware feature that it can insert a 2-bytes pseudo
> >> header in front of each received frame by setti
Hi,
On Wed, 2013-12-04 at 21:38 +0800, Peter Chen wrote:
> On Wed, Dec 04, 2013 at 11:35:54AM +0200, Ivan T. Ivanov wrote:
> >
> > Hi Peter,
> >
> > On Wed, 2013-12-04 at 13:37 +0800, Peter Chen wrote:
> > > On Mon, Nov 11, 2013 at 04:36:09PM +0200, Ivan T. Ivanov wrote:
> > > >
> > > > Hi
On Tue, 2013-11-12 at 16:51 +0200, Ivan T. Ivanov wrote:
> From: "Ivan T. Ivanov"
>
> This patch fix compilation error when driver is compiled
> in multi-platform builds.
>
> drivers/built-in.o: In function `msm_otg_link_clk_reset':
> ./drivers/usb/phy/phy-msm-usb.c:314: undefined reference to
Hi,
On Thu, 2013-12-05 at 10:41 +, Mark Rutland wrote:
> On Mon, Nov 18, 2013 at 12:54:37PM +, Ivan T. Ivanov wrote:
> > Hi Mark,
> >
> > On Fri, 2013-11-15 at 16:38 +, Mark Rutland wrote:
> > > On Tue, Nov 12, 2013 at 02:51:45PM +, Ivan T. Ivanov wrote:
> > > > From: "Ivan T.
On Wednesday 11 December 2013 02:23 PM, Heikki Krogerus wrote:
> Hi,
>
> On Mon, Dec 09, 2013 at 11:26:04AM +0200, Heikki Krogerus wrote:
>> Can you guys explain why is something like this needed? Like with
>> clocks and gpios, the device drivers shouldn't need to care any more
>> if t
Hi again,
On Wed, Dec 11, 2013 at 02:02:43PM +0530, Vivek Gautam wrote:
> On Wed, Dec 11, 2013 at 1:39 PM, Heikki Krogerus
> wrote:
> > On Wed, Dec 11, 2013 at 12:08:04PM +0530, Vivek Gautam wrote:
> >> On Tue, Dec 10, 2013 at 7:31 PM, Heikki Krogerus
> >> > I think "setup" instead of "tune" is m
Hi,
On Mon, Dec 09, 2013 at 11:26:04AM +0200, Heikki Krogerus wrote:
> > >>>Can you guys explain why is something like this needed? Like with
> > >>>clocks and gpios, the device drivers shouldn't need to care any more
> > >>>if the platform has the phys or not. -ENODEV tells you your platform
> >
Hi Kishon,
On Wed, Dec 11, 2013 at 1:47 PM, Kishon Vijay Abraham I wrote:
> On Wednesday 11 December 2013 12:08 PM, Vivek Gautam wrote:
>> Hi,
>>
>>
>> On Tue, Dec 10, 2013 at 7:31 PM, Heikki Krogerus
>> wrote:
>>> Hi,
>>
>> Thanks for reviewing this.
>>
>>>
>>> On Tue, Dec 10, 2013 at 04:25:23
Hi,
On Wed, Dec 11, 2013 at 1:39 PM, Heikki Krogerus
wrote:
> Hi,
>
> On Wed, Dec 11, 2013 at 12:08:04PM +0530, Vivek Gautam wrote:
>> On Tue, Dec 10, 2013 at 7:31 PM, Heikki Krogerus
>> > I think "setup" instead of "tune" is much more clear and reusable.
>>
>> I think "setup" will look more lik
Hi,
On Thu, 2013-12-05 at 10:42 +, Mark Rutland wrote:
> On Mon, Nov 18, 2013 at 12:57:42PM +, Ivan T. Ivanov wrote:
> >
> > Hi Mark,
> >
> > On Fri, 2013-11-15 at 16:42 +, Mark Rutland wrote:
> > > On Tue, Nov 12, 2013 at 02:51:47PM +, Ivan T. Ivanov wrote:
> > > > From: "Iva
On Wednesday 11 December 2013 12:08 PM, Vivek Gautam wrote:
> Hi,
>
>
> On Tue, Dec 10, 2013 at 7:31 PM, Heikki Krogerus
> wrote:
>> Hi,
>
> Thanks for reviewing this.
>
>>
>> On Tue, Dec 10, 2013 at 04:25:23PM +0530, Vivek Gautam wrote:
>>> Some PHY controllers may need to tune PHY post-initi
On 11/12/2013 08:31, Jingoo Han :
Use devm_*() functions to make cleanup paths simpler.
Signed-off-by: Jingoo Han
Jingoo,
Well, these modifications are already addressed by a series written by
Boris.
"[PATCH v5 0/3] usb: ohci-at91: various improvements"
Thanks for your patch anyway.
Bes
Hi,
On Wed, Dec 11, 2013 at 12:08:04PM +0530, Vivek Gautam wrote:
> On Tue, Dec 10, 2013 at 7:31 PM, Heikki Krogerus
> > I think "setup" instead of "tune" is much more clear and reusable.
>
> I think "setup" will look more like first time setting up the phy,
> which is rather served by "init" cal
38 matches
Mail list logo
