vekin writes:
>
> I have a Seagate backup plus 3TB usb3 drive that seems to be recognized.
> I get no /dev/sdx device associated with it unless I unplug it and plug it in
> after the kernel is loaded.
>
I only now just realized that the problem only occurs when I use "reboot"
not "shutdown -h n
I am a new fish of linux usb host driver developper.
Recently, when developping the host's PM function, I found that usb's
remote wakeup relys on CONFIG_USB_SUSPEND. I do not know why we need
such a restriction.
Is it means if a usb host driver without the implementation of runtime
suspend also ca
When usbfs receives a ctrl-request from userspace it calls check_ctrlrecip,
which for a request with USB_RECIP_ENDPOINT tries to map this to an interface
to see if this interface is claimed, except for ctrl-requests with a type of
USB_TYPE_VENDOR.
When trying to use this device: http://www.akaipro
The intention was to test against the constant, not the size of
the constant.
Signed-off-by: Bjørn Mork
---
This should go to stable-3.8 (and stable-3.9 if too late for v3.9).
Thanks.
Bjørn
drivers/net/usb/cdc_mbim.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/driver
Hi,
On Tuesday 16 April 2013 01:20 AM, Grant Likely wrote:
On Mon, 15 Apr 2013 17:56:10 +0530, Kishon Vijay Abraham I
wrote:
Hi,
On Monday 15 April 2013 05:04 PM, Grant Likely wrote:
On Wed, 20 Mar 2013 14:42:00 +0530, Kishon Vijay Abraham I
wrote:
The PHY framework provides a set of API
From: Manjunath Goudar
This patch prepares ohci-hcd for being split up into a core
library and separate platform driver modules. A generic
ohci_hc_driver structure is created, containing all the "standard"
values, and a new mechanism is added whereby a driver module can
specify a set of override
From: Manjunath Goudar
This patch splits the PCI portion of ohci-hcd out into its
own separate driver module, called ohci-pci. Consistently with the
current practice, the decision whether to build this module is not
user-configurable. If OHCI_PCI are enabled then the module will
be built, alway
On Tue, 16 Apr 2013, linux fddl wrote:
> I am a new fish of linux usb host driver developper.
> Recently, when developping the host's PM function, I found that usb's
> remote wakeup relys on CONFIG_USB_SUSPEND. I do not know why we need
> such a restriction.
> Is it means if a usb host driver wit
On Tue, 16 Apr 2013, Hans de Goede wrote:
> When usbfs receives a ctrl-request from userspace it calls check_ctrlrecip,
> which for a request with USB_RECIP_ENDPOINT tries to map this to an interface
> to see if this interface is claimed, except for ctrl-requests with a type of
> USB_TYPE_VENDOR.
Hello.
On 16-04-2013 13:08, Hans de Goede wrote:
When usbfs
USBFS support has been removed some months ago. Maybe you meant 'usbdevfs'?..
receives a ctrl-request from userspace it calls check_ctrlrecip,
which for a request with USB_RECIP_ENDPOINT tries to map this to an interface
to see
On Tuesday 16 April 2013 09:15:45 Ming Lei wrote:
> On Mon, Apr 15, 2013 at 11:59 PM, Dan Williams wrote:
> >
> > So, what was the general consensus on this one? I know Oliver signed
> > off on it, but the discussion about memflags seemed to die out without a
> > specific conclusion. davem might
On 16-04-2013 18:12, Sergei Shtylyov wrote:
When usbfs
USBFS support has been removed some months ago. Maybe you meant
'usbdevfs'?..
Or was it vice versa, or is there two entities dubbed 'usbfs'? Anyway,
here's the commit removing CONFIG_USB_DEVICEFS (under /proc/bus/usb/):
https
Am 15.04.2013 18:16, schrieb Greg KH:
If you can't do the bisection, can you point me at the exact device you
are using here so I can buy one and try to track this down?
It seems that exact the same adapter is out of stock.
But this seems to be nearly exact the same one:
http://cgi.ebay.com/ws
On Tue, 16 Apr 2013, Sergei Shtylyov wrote:
> On 16-04-2013 18:12, Sergei Shtylyov wrote:
>
> >> When usbfs
>
> > USBFS support has been removed some months ago. Maybe you meant
> > 'usbdevfs'?..
>
> Or was it vice versa, or is there two entities dubbed 'usbfs'? Anyway,
> here's the c
Hi,
>> >In fact, this problem starts even _before_ the INQUIRY command is
>> >received. The log shows that the UDC driver calls the
>> >bulk_out_complete routine over and over, even though no packet was
>> >received and ka2000_ack_irq didn't run. The same thing happens after
>> >the INQUIRY is r
On Tue, 16 Apr 2013, vekin wrote:
> I have a Seagate backup plus 3TB usb3 drive that seems to be recognized.
> I get no /dev/sdx device associated with it unless I unplug it and plug it in
> after the kernel is loaded.
>
> I can see this.
> Bus 004 Device 002: ID 0bc2:a0a1 Seagate RSS LLC
> But
On Tue, 16 Apr 2013, Gonglei (Arei) wrote:
> > > Yes, this disk was using EHCI, since guest QEMU and Linux kernel both
> > > prints matching EHCI logs, such as transfer types and transfer sizes.
> > > There are many buck-out URBs whose sizes are 31 or 4064 that are not
> > > multiples of 512. Sinc
On Tue, 16 Apr 2013, victor yeo wrote:
> From the usbmon trace and driver log, i can only see that TEST UNIT
> READY command is sent out but UDC driver does not receive it. May i
> ask, under what circumstances, is gadget driver calling
> start_transfer() to schedule reading from bulk-out endpoint
On Mon, 15 Apr 2013, Roger Quadros wrote:
> Don't select NOP_USB_XCEIV. Instead, board config
> must select USB_PHY and the appropriate PHY driver.
>
> Also add a hint in Kconfig so that users enabling
> this driver manually enable the right PHY drivers as well.
>
> Gets rid of the below warning
On Mon, 15 Apr 2013, Roger Quadros wrote:
> As the USB PHY layer never returns NULL we don't need
> to check for that condition.
>
> If we fail to get the PHY device it could be due
> to missing USB PHY drivers. Give this hint to the user
> in the error message.
>
> CC: Alan Stern
> Signed-off-
On Mon, 15 Apr 2013, Michael Braun wrote:
> Hi,
>
> I'm running OpenWRT Kernel 3.8.3 (which already has
> f66dea709cd9309b2ee9f715697818001fb518de and
> 5ed338778f917a035f0f0a52327fc4f72e36f7a1 applied) on a P1020WLAN (QorlQ,
> PPC) device.
> Before updating the kernel from 3.3.0, USB host sup
Hi,
> Fixing this will require qemu to copy the beginning and ending parts of
> these non-aligned qTDs into separate bounce buffers so that the URB
> length can be divisible by 512.
Worth trying: http://www.kraxel.org/cgit/qemu/log/?h=usb.80
It puts the qemu usb passthrough code upside down.
>From musb point of view, the Address Assignment sequence during
device enumeration is next:
- first ep0 interrupt:
* read the address from USB_REQ_SET_ADDRESS request
* set up CSR0L.DataEnd bit (that is ACK
signalization for the host)
- second ep0 interrupt:
* i
Allocate port-private data in port-probe rather than in attach.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/symbolserial.c | 30 +++---
1 file changed, 19 insertions(+), 11 deletions(-)
diff --git a/drivers/usb/serial/symbolserial.c
b/drivers/usb/serial/symbolser
Remove redundant data-offset define, which was really just the header
length.
Add payload-size define and use the bulk-out size define for the actual
bulk-out size.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/omninet.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
Refactor read-urb processing, and add sanity checks on header and data
lengths.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/omninet.c | 25 ++---
1 file changed, 18 insertions(+), 7 deletions(-)
diff --git a/drivers/usb/serial/omninet.c b/drivers/usb/serial/omninet.c
Make sure the port private data, which contains the write sequence
number, is cleared at allocation.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/omninet.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/serial/omninet.c b/drivers/usb/serial/omninet.c
index
These patches against usb-next replace the omninet custom read
implementation with the generic one, fix some port-data abuse in
mct_u232, and make kobil_sct and symbolserial use the port interrupt
urbs rather than private ones, while cleaning up all four drivers
somwehat.
All patches have been com
Replace broken and commented-out debug code with usb_serial_debug_data.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/kobil_sct.c | 20 ++--
1 file changed, 2 insertions(+), 18 deletions(-)
diff --git a/drivers/usb/serial/kobil_sct.c b/drivers/usb/serial/kobil_sct.c
index 9
Use the port interrupt-out urb rather than abusing the port write_urb
pointer and allocating a new urb at every open (but the first...).
Note that the write_urb abuse would have led to a double free should
there ever be interfaces with a bulk-out endpoint.
Signed-off-by: Johan Hovold
---
driver
Use the port interrupt-in urb rather managing a private one.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/symbolserial.c | 102 +-
1 file changed, 12 insertions(+), 90 deletions(-)
diff --git a/drivers/usb/serial/symbolserial.c
b/drivers/usb/serial/sym
Switch to the more efficient generic read implementation.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/omninet.c | 43 +++
1 file changed, 3 insertions(+), 40 deletions(-)
diff --git a/drivers/usb/serial/omninet.c b/drivers/usb/serial/omninet.c
inde
The device uses the second interrupt-in endpoint of the interface for
reading. Stop abusing the port read urb and store a pointer to the
second interrupt-in urb as port-private data instead.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/mct_u232.c | 37 +++--
Use port device for debug messages in interrupt-urb callback and remove
unused private data.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/symbolserial.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/usb/serial/symbolserial.c
b/drivers/usb/serial/symbolse
Remove unused interrupt-in endpoint address from private data.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/kobil_sct.c | 8
1 file changed, 8 deletions(-)
diff --git a/drivers/usb/serial/kobil_sct.c b/drivers/usb/serial/kobil_sct.c
index da1a372..5bcfd57 100644
--- a/drivers/usb
Clean up and fix typos in protocol comment.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/omninet.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/drivers/usb/serial/omninet.c b/drivers/usb/serial/omninet.c
index ea1105c..ec16b92 100644
--- a/drivers/usb/s
Hi Felipe,
> "by by this commit message" ??
Hmm, not sure what my brain was doing there. Will be fixed in the next version.
> > --- a/drivers/staging/dwc2/hcd_intr.c
> > +++ b/drivers/staging/dwc2/hcd_intr.c
> > @@ -2083,7 +2083,8 @@ irqreturn_t dwc2_hcd_intr(struct dwc2_hsotg *hsotg)
> >
Hi Paul,
> > Before, the DISCONNINT interrupt was enabled in
> > dwc2_enable_host_interrupts, but handled in dwc2_handle_common_intr,
> > while the RXFLVL interrupt was enabled in dwc2_enable_commont_interrupts
> > and handled in dwc_handle_hcd_intr.
>
> I guess you meant dwc2_hcd_intr, not dwc_h
Hi Paul,
> > --- a/drivers/staging/dwc2/core.c
> > +++ b/drivers/staging/dwc2/core.c
...
> > + /* Enable common interrupts without disturbing host mode interrupts */
> > + intmsk = readl(hsotg->regs + GINTMSK);
> > + intmsk |= GINTSTS_DISCONNINT | GINTSTS_MODEMIS | GINTSTS_OTGINT |
> > +
Hi Paul,
On Mon, Apr 15, 2013 at 10:22:12PM +, Paul Zimmerman wrote:
> Resending as plain text.
>
> > From: Matthijs Kooijman [mailto:matth...@stdin.nl]
> > Sent: Monday, April 15, 2013 7:14 AM
> >
> > For host mode, this interrupt is already handled by the hcd interrupt
> > handler. The com
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Bilovol, Ruslan
> Sent: Tuesday, April 16, 2013 9:12 PM
> To: Balbi, Felipe; gre...@linuxfoundation.org; linux-usb@vger.kernel.org;
> linux-ker...@vger.kernel.org
> Subject:
On 10.04.2013 21:55, Daniel Mack wrote:
> Hi all,
>
> here are some patches to separate the HCD and gadget part of the musb
> driver so they can be deselected in Kconfig. They also make the driver
> keep track of the configured port mode that is set from DT, so the
> actual runtime configuration c
> From: Matthijs Kooijman [mailto:matth...@stdin.nl]
> Sent: Tuesday, April 16, 2013 9:47 AM
>
> > > --- a/drivers/staging/dwc2/core.c
> > > +++ b/drivers/staging/dwc2/core.c
> ...
> > > + /* Enable common interrupts without disturbing host mode interrupts */
> > > + intmsk = readl(hsotg->regs + G
> From: Matthijs Kooijman [mailto:matth...@stdin.nl]
> Sent: Tuesday, April 16, 2013 9:53 AM
>
> On Mon, Apr 15, 2013 at 10:22:12PM +, Paul Zimmerman wrote:
> >
> > > From: Matthijs Kooijman [mailto:matth...@stdin.nl]
> > > Sent: Monday, April 15, 2013 7:14 AM
> > >
> > > For host mode, this i
Hi Paul,
> No, the interrupt is strictly a host interrupt. But due to the
> design of the hardware, there's a race condition: Say the user
> unplugs the A connector from the host. The disconnect interrupt gets
> triggered, and the driver starts to process it. But unplugging the
> A connector also
> From: Matthijs Kooijman [mailto:matth...@stdin.nl]
> Sent: Tuesday, April 16, 2013 12:03 PM
>
> > No, the interrupt is strictly a host interrupt. But due to the
> > design of the hardware, there's a race condition: Say the user
> > unplugs the A connector from the host. The disconnect interrupt
Excellent. The quirk is no longer triggering resource issues.
This leaves an issue with dev->enable_cnt in pci_disable_device. We
still get the message 'disabling already-disabled device'. I was hoping
by not having the resource errors, enable_cnt would be more accurate.
This occurs after:
- c
From: Bjørn Mork
Date: Tue, 16 Apr 2013 12:17:07 +0200
> The intention was to test against the constant, not the size of
> the constant.
>
> Signed-off-by: Bjørn Mork
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@
Hello.
Here's the set of 4 patches against the Simon Horman's 'renesas.git' repo,
'renesas-next-20130416' tag and the R8A7779/Marzen patchset I've posted.
It was created to add support of R8A7778/BOCK-W USB to the platform code and
the USB common PHY driv
The driver currently only supports R8A7779 SoC. Compared to it, R8A7778 USB-PHY
has extra register range containing two high-speed signal quality characteristic
control registers which should be set up during USB-PHY startup depending on
whether a ferrite bead is in use or not. So, we now handle
Add USB clock and EHCI, OHCI, and USB PHY platform devices for R8A7778 SoC; add
a function to register PHY device with board-specific platform data and register
EHCI and OHCI platfrom devices from the init_late() board method.
Also, don't forget to enable CONFIG_ARCH_HAS_[EO]HCI options for R8A7
Register the USB PHY device from bockw_init(), passing the platform data to it.
Set machine's init_late() method to r8a7778_init_late() in order for [EO]HCI to
get registered too...
The patch has been tested on the BOCK-W board.
Signed-off-by: Sergei Shtylyov
---
Changes since version 2:
- ref
Enable USB platform EHCI/OHCI and common PHY drivers in 'bockw_defconfig'.
Enable USB storage driver and SCSI disk driver that it needs as well...
Signed-off-by: Sergei Shtylyov
---
arch/arm/configs/bockw_defconfig | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
Index: rene
Hi
I am using an isp1763 on MPC8360 and linux-3.0.0-2 from debian.
The driver is ported from Sebastian's original isp1760 and I am forward porting
to Arvid's version.
I noticed that a custom timing delay is missing on the new isp1760. This delay
is added in [1]
and an mmiowb() is added in [2]
On 04/17/2013 01:32 AM, I wrote:
The driver currently only supports R8A7779 SoC. Compared to it, R8A7778 USB-PHY
has extra register range containing two high-speed signal quality characteristic
control registers which should be set up during USB-PHY startup depending on
whether a ferrite bead
The driver currently only supports R8A7779 SoC. Compared to it, R8A7778 USB-PHY
has extra register range containing two high-speed signal quality characteristic
control registers which should be set up during USB-PHY startup depending on
whether a ferrite bead is in use or not. So, we now handle
Hi Sergei
> >>> I'm going to post R8A7778/BOCK-W series following this one, and
> >>> all the
> >>> patches in 1st series should additionally be tested on BOCK-W. Well, I
> >>> probably can hold up posting version 3 until I have the second
> >>> series verified.
> >>> BTW, about R8A77
On Wed, Apr 17, 2013 at 9:17 AM, Chao Xie wrote:
>
> On Sun, Apr 7, 2013 at 6:29 PM, Chao Xie wrote:
>>
>> The patches create the mv-usb phy driver
>>
>>
>> directly use devm_usb_get_phy_dev return value for error return.
>>
>> v9->v8
>> Remove u2o_xxx.
>> Add prefix for register definition
On Tue, Apr 16, 2013 at 3:57 PM, Oliver Neukum wrote:
> On Tuesday 16 April 2013 09:15:45 Ming Lei wrote:
>> On Mon, Apr 15, 2013 at 11:59 PM, Dan Williams wrote:
>> >
>> > So, what was the general consensus on this one? I know Oliver signed
>> > off on it, but the discussion about memflags seem
This patch adds the support in UVC webcam gadget to allocate UVC header and
payload as Scatter-Gather elements which can be used on a SG-capable UDC
controller.
A module parameter has been introduced for the same. One can set the
module parameter 'sg_mode' to 1 to turn on this feature (by default
Hi Laurent,
> Hi Bhupesh,
>
> On Wednesday 10 April 2013 18:37:42 Bhupesh SHARMA wrote:
> > Hi Laurent,
> >
> > > This patchset tries to enhance the UVC gadget test application and
> > > is based on Laurent's git tree available here (project: uvc-gadget.git):
> > > git://git.ideasonboard.org/uvc-
Reduce the size of the objects by consolidating
the duplicated USB_STORAGE into a single function.
Add function usb_stor_dbg to emit debugging messages.
Always validate the format and arguments.
Reduce the number of uses of CONFIG_USB_STORAGE_DEBUG.
Reduces size of objects ~7KB when CONFIG_USB_ST
On Wednesday 17 April 2013 09:56:33 Ming Lei wrote:
> On Tue, Apr 16, 2013 at 3:57 PM, Oliver Neukum wrote:
> > Generally, saying that somebody else has a problem is not an argument
> > as long as the fix is very simple. Of course it is a corner case, but why
> > fail to solve it as long as the c
63 matches
Mail list logo
