On Tue, Aug 14, 2012 at 10:21:16PM +0200, Sebastian Andrzej Siewior wrote:
> The remaining non-composite users are:
> - dbgp
> very simple, not doing much ep0
> - file_storage
> will be removed in v3.8
> - gadgetfs
> Here are my problems at a central spot.
>
> So gadgetfs. Its ep0 handling c
On 2012年08月15日 08:28, Greg Kroah-Hartman wrote:
> On Tue, Jul 17, 2012 at 03:28:43PM -0700, Sarah Sharp wrote:
>> --- a/drivers/usb/core/usb.h
>> +++ b/drivers/usb/core/usb.h
>> @@ -1,5 +1,9 @@
>> #include
>>
>> +#ifdef CONFIG_ACPI
>> +#include
>> +#endif
>
> Why is this #ifdef in here?
>
If
On 2012年08月15日 08:27, Greg Kroah-Hartman wrote:
> On Tue, Jul 17, 2012 at 03:28:42PM -0700, Sarah Sharp wrote:
>> From: Lan Tianyu
>>
>> This patch turns each USB port on a hub into a new struct device. This
>> new device has the USB hub interface device as its parent. The port
>> devices are st
On Tue, Jul 17, 2012 at 03:28:43PM -0700, Sarah Sharp wrote:
> --- a/drivers/usb/core/usb.h
> +++ b/drivers/usb/core/usb.h
> @@ -1,5 +1,9 @@
> #include
>
> +#ifdef CONFIG_ACPI
> +#include
> +#endif
Why is this #ifdef in here?
greg k-h
--
To unsubscribe from this list: send the line "unsubscr
On Tue, Jul 17, 2012 at 03:28:42PM -0700, Sarah Sharp wrote:
> From: Lan Tianyu
>
> This patch turns each USB port on a hub into a new struct device. This
> new device has the USB hub interface device as its parent. The port
> devices are stored in a new structure (usb_port), and an array of
>
From: Bjørn Mork
Date: Sun, 12 Aug 2012 21:53:38 +0200
> Signed-off-by: Bjørn Mork
Applied to 'net'
--
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
From: Bjørn Mork
Date: Sun, 12 Aug 2012 21:16:29 +0200
> The home cooked whitelisting code can be removed now that
> the USB core supports interface number matching.
>
> The second patch adds a few new devices.
>
> The third patch improves device list readability by using
> existing macros whe
On Tue, Aug 14, 2012 at 10:57:58PM +0200, Peter Stuge wrote:
> Matthew Garrett wrote:
> > +++ b/drivers/usb/host/pci-quirks.c
> ..
> > @@ -830,9 +830,17 @@ static void __devinit quirk_usb_handoff_xhci(struct
> > pci_dev *pdev)
> > */
> > ext_cap_offset = xhci_find_next_cap_offset(base,
>
Matthew Garrett wrote:
> +++ b/drivers/usb/host/pci-quirks.c
..
> @@ -830,9 +830,17 @@ static void __devinit quirk_usb_handoff_xhci(struct
> pci_dev *pdev)
>*/
> ext_cap_offset = xhci_find_next_cap_offset(base,
> XHCI_HCC_PARAMS_OFFSET);
> do {
> + if ((ext_cap_off
My test platform (Intel DX79SI) boots reliably under BIOS, but frequently
crashes when booting via UEFI. I finally tracked this down to the xhci
handoff code. It seems that reads from the device occasionally just return
0xff, resulting in xhci_find_next_cap_offset generating a value that's
larger t
The remaining non-composite users are:
- dbgp
very simple, not doing much ep0
- file_storage
will be removed in v3.8
- gadgetfs
Here are my problems at a central spot.
So gadgetfs. Its ep0 handling can be done in kernel and some requests
can be offloded to userland. Lets assume the host send
Hi Russell,
> On Tue, Aug 14, 2012 at 12:54:00PM +0200, Jiri Kosina wrote:
> > Actually, Henrik (added to CC) has been doing some latency improvements
> > both for input core in general, and for HID devices as well lately. I
> > still have his patchset in my to-review queue, as I have just came
Hi Sarah,
I was wondering if you have any news regarding this patch, or if there's
something else I need to change on code. I also noticed that I forgot to write
'[PATCH]' at the beginning of the patch's subject, Should I resend it?
Thanks and Best Regards,
Alexis Cortes.
On 8/3/2012 2:00
Hi,
going through uas it looks to me like there is a race by which
uas_do_work() can walk uas_work_list and do IO to a device
after it has been removed. This makes me wonder why you used
a single global list. Could you comment on that and tell me whether
I missed something subtle?
Regards
于 2012/8/13 23:52, Alan Stern 写道:
On Mon, 13 Aug 2012, Lan, Tianyu wrote:
Hi all:
I am trying to implement patch of setting DeviceRemovable
according ACPI information.
The DeviceRemovable is set in hcd driver *_hub_descriptor(e.g
ehci_hub_descriptor()). But these
functions jus
On Tue, Aug 14, 2012 at 08:15:39AM +0200, Ruben Jenster wrote:
> Hi Greg,
>
> thanks for your answer.
>
> On Aug 13, 2012, at 4:42 PM, Greg KH wrote:
>
> >
> > After reading the code for the USB host driver for this hardware, and
> > reading the hardware data sheet, I'm amazed that any USB devi
Hello Kelvin,
On Wednesday 18 January 2012 14:41:16 Kelvin Cheung wrote:
> Use ehci_setup() in ehci_ls1x_reset().
>
> The Loongson1x SoCs have a built-in EHCI controller.
> This patch adds the necessary glue code to make the generic EHCI
> driver usable for them.
>
> Signed-off-by: Kelvin Cheung
On 8/14/12, Chen Peter-B29397 wrote:
> HW_USBPHY_CTRL.ENHOSTDISCONDETECT should be set after bus reset is
> finished.
I agree. How do we guarantee that ENHOSTDISCONDETECT is set after bus reset?
Thanks,
Fabio Estevam
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
th
On Tuesday 14 August 2012 12:54:00 Jiri Kosina wrote:
> Offloading the processing to workqueue might actually work and make sense,
> but I will have to think a little bit more about all the consequences it'd
> have throughout the rest of the code.
How would alt-sysrq be handled?
Reagrds
On Tue, Aug 14, 2012 at 12:54:00PM +0200, Jiri Kosina wrote:
> Actually, Henrik (added to CC) has been doing some latency improvements
> both for input core in general, and for HID devices as well lately. I
> still have his patchset in my to-review queue, as I have just came back
> from offline
On Tue, 14 Aug 2012, Russell King wrote:
> I've been trying to track down where all the CPU time goes while
> processing USB interrupts for HID devices. At the moment, out of
> everything on the cubox, moving the mouse or even pressing a key
> on the keyboard just once is far more expensive than
I've been trying to track down where all the CPU time goes while
processing USB interrupts for HID devices. At the moment, out of
everything on the cubox, moving the mouse or even pressing a key
on the keyboard just once is far more expensive than processing an
interrupt for the network interface
Le Sun, 12 Aug 2012 17:23:30 -0400 (EDT),
Alan Stern a écrit :
> On Sun, 12 Aug 2012, Laurent Bigonville wrote:
>
> > > I don't know how well this will work, but you can tell the
> > > computer not to ask for all those reports by using an appropriate
> > > module parameter for the usbhid driver:
On Tue, Aug 14, 2012 at 07:46:59AM +1000, NeilBrown wrote:
> On Mon, 13 Aug 2012 17:32:34 +0300 Felipe Balbi wrote:
>
> > Hi,
> >
> > On Mon, Aug 13, 2012 at 12:34:53PM +1000, NeilBrown wrote:
> > > On Thu, 9 Aug 2012 14:15:51 +0300 Felipe Balbi wrote:
> > >
> > >
> > > > hehe, that's nasty.
24 matches
Mail list logo
