Hi,
Am 14.04.2013 16:01, schrieb Greg KH:
On Sun, Apr 14, 2013 at 11:42:06AM +0200, Karsten Malcher wrote:
please have a look at my last email in the bug report.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704242
Do you have an idea what's maybe the difference that this adapter is working
Hi,
>> Here are another problem. In usbmon trace, the time difference
>> between first SCSI_INQUIRY command and the second TEST_UNIT_READY
>> command is large. So i check the driver log file. When SCSI_INQUIRY is
>> received, start_transfer() is called, then UDC ep_queue function is
>> called, the
On Wed, 20 Mar 2013 14:41:59 +0530, Kishon Vijay Abraham I
wrote:
> Added a generic PHY framework that provides a set of APIs for the PHY drivers
> to create/destroy a PHY and APIs for the PHY users to obtain a reference to
> the PHY with or without using phandle. To obtain a reference to the PHY
This adds a dwc_platform.ko module that can be loaded by using
compatible = "snps,dwc2" in a device tree.
Signed-off-by: Matthijs Kooijman
---
v2: remove useless debug prints
change module author and copyright
use "usb" in devicetree example instead of "otg"
v3: make building as a module
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-gadget.git
> >
> > The patc
Hi,
On Monday 15 April 2013 03:50 PM, Grant Likely wrote:
On Wed, 20 Mar 2013 14:41:59 +0530, Kishon Vijay Abraham I
wrote:
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or
On 04/15/2013 12:36 PM, Kishon Vijay Abraham I wrote:
> On Monday 15 April 2013 03:50 PM, Grant Likely wrote:
>> On Wed, 20 Mar 2013 14:41:59 +0530, Kishon Vijay Abraham I
>> wrote:
>>> Added a generic PHY framework that provides a set of APIs for the PHY
>>> drivers
>>> to create/destroy a PHY a
On Wed, 20 Mar 2013 14:42:00 +0530, Kishon Vijay Abraham I
wrote:
> The PHY framework provides a set of APIs for the PHY drivers to
> create/destroy a PHY and APIs for the PHY users to obtain a reference to the
> PHY with or without using phandle. To obtain a reference to the PHY without
> using
Hello.
On 13-04-2013 3:40, 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 b
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-by: Roger Quadros
---
drivers/usb/host/ehci-omap.c |6 +
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 warnings when USB_EHCI_HCD_OMAP
is enabled.
warning: (USB_EHCI_
Matthijs Kooijman writes:
>
> > > It seems like you managed to resolve the issue. If so, then could you
please
> > > explain how you managed to do it.
> > It's probably not directly helpful to you since the driver is really
> > different, but I patched up the dwc_otg driver to detect this "locku
On Mon, 15 Apr 2013 16:06:37 +0530, Kishon Vijay Abraham I
wrote:
> Hi,
>
> On Monday 15 April 2013 03:50 PM, Grant Likely wrote:
> > On Wed, 20 Mar 2013 14:41:59 +0530, Kishon Vijay Abraham I
> > wrote:
> >> Added a generic PHY framework that provides a set of APIs for the PHY
> >> drivers
>
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 APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using ph
Hi,
On Monday 15 April 2013 05:56 PM, Grant Likely wrote:
On Mon, 15 Apr 2013 16:06:37 +0530, Kishon Vijay Abraham I
wrote:
Hi,
On Monday 15 April 2013 03:50 PM, Grant Likely wrote:
On Wed, 20 Mar 2013 14:41:59 +0530, Kishon Vijay Abraham I
wrote:
Added a generic PHY framework that provi
Hi Laurent,
On Mon, Feb 11, 2013 at 08:43:44PM +0100, Laurent Pinchart wrote:
> Hi Michael,
>
> Thanks for the patch.
>
> On Saturday 09 February 2013 00:54:54 Michael Grzeschik wrote:
> > Those optional operations are used to release and reacquire the queue
> > lock when videobuf2 needs to perf
Hi Michael,
On Monday 15 April 2013 14:36:27 Michael Grzeschik wrote:
> On Mon, Feb 11, 2013 at 08:43:44PM +0100, Laurent Pinchart wrote:
> > On Saturday 09 February 2013 00:54:54 Michael Grzeschik wrote:
> > > Those optional operations are used to release and reacquire the queue
> > > lock when v
Hi folks,
my next series of cleanups is related to interrupt handling. The dwc2
driver distinguishes between host mode interrupts and common interrupts
(where the latter occur in both host and device mode). However, this
distinction was a bit messy at some points, which this series tries to
fix.
For host mode, this interrupt is already handled by the hcd interrupt
handler. The common interrupt handler additionally did a noop handling
(it only cleared the flag and nothing else) when in device mode.
Since the driver currently supports only host mode, this shouldn't
result in any behaviour c
This piece of code manually disabled interrupts, while there are
perfectly good functions to do this.
Technically, the old code really disabled _all_ interrupts, while the
new code only disables a specific list of interrupts, but that list of
interrupts includes all interrupts that are ever enable
Before, enabling common interrupts would implicitly disable all other
interrupts and enabling host interrupts would disable all interrupts and
then enable both common and host interrupts.
Now, these two are properly separated: each enable function only enables
its own interrupts and leaves all oth
This interrupt is currently not enabled anywhere, but there is some
(dummy) handling for it in the host interrupt handler. This marks it as
a host mode interrupt, so it makes sense to disable it when disabling
the other host mode interrupts.
Signed-off-by: Matthijs Kooijman
---
drivers/staging/d
Before, dwc2_hcd_intr() would always return IRQ_HANDLED when the
controller was in host mode, even if no interrupt triggered that was
actually handled by by this commit message (for example for interrupts
handled by the common handler).
The check added works just like the check that is already in
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.
This moves the enabling of these interrupts around to match the spot
whe
This function disables all "common interrupts", i.e., those that are
handled by the common interrupt handler.
Signed-off-by: Matthijs Kooijman
---
drivers/staging/dwc2/core.c | 14 ++
drivers/staging/dwc2/core.h | 6 ++
drivers/staging/dwc2/core_intr.c | 5 -
3 fi
This simply defines a list of interrupts handled by the the host
interrupt handler.
Signed-off-by: Matthijs Kooijman
---
drivers/staging/dwc2/core.c | 4 +---
drivers/staging/dwc2/core.h | 4
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/dwc2/core.c b/driver
From: Stephen Warren
The top-level hcd interrupt handlers already used irq_return_t, but the
functions to which it delegates the actual work and the common irq
handler returned plain ints. In addition, they used the IRQ_RETVAL in
the wrong way (but because of the values of the various constants,
This flag is a deprecated NOOP, interrupt handlers are always run
with interupts disabled.
See commit 6932bf37 (genirq: Remove IRQF_DISABLED from core code), and
include/linux/interrupt.h:
* IRQF_DISABLED - keep irqs disabled when calling the action handler.
* DE
Hi,
On Mon, Apr 15, 2013 at 04:13:47PM +0200, Matthijs Kooijman wrote:
> Before, dwc2_hcd_intr() would always return IRQ_HANDLED when the
> controller was in host mode, even if no interrupt triggered that was
> actually handled by by this commit message (for example for interrupts
"by by this com
On Wed, 2013-04-10 at 15:30 -0500, Dan Williams wrote:
> Some drivers (sierra_net) need the status interrupt URB
> active even when the device is closed, because they receive
> custom indications from firmware. Add functions to refcount
> the status interrupt URB submit/kill operation so that
> su
On Mon, Apr 15, 2013 at 10:23:08AM +0200, Karsten Malcher wrote:
> Hi,
>
> Am 14.04.2013 16:01, schrieb Greg KH:
> >On Sun, Apr 14, 2013 at 11:42:06AM +0200, Karsten Malcher wrote:
> >>please have a look at my last email in the bug report.
> >>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=70424
On Mon, 15 Apr 2013, victor yeo wrote:
> >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 hap
On Sun, 14 Apr 2013, Gonglei (Arei) wrote:
> > > Hi Alan,
> > > We pass-throughed USB 2.0 disk to guest using usb-host (qemu option:
> > -device usb-ehci,id=ehci -device usb-host,bus=ehci.0,hostbus=2,hostport=1)
> > on
> > KVM(on linux-3.8.3 or linux-3.0.13) and qemu 1.4.0 ,
> >
> > Are you sure
Cc-ing the public Linux PCI and USB mailing lists.
On Fri, Apr 12, 2013 at 02:59:29PM -0400, Bulkow, David wrote:
> Susan,
I'm Sarah. :)
> While testing Linux 3.9 we ran into an issue which I believe is a
> conflict between a couple of PCI changes. Stratus has hardware that
> can hot add/remove
> From: Matthijs Kooijman [mailto:matth...@stdin.nl]
> Sent: Monday, April 15, 2013 7:14 AM
>
> This flag is a deprecated NOOP, interrupt handlers are always run
> with interupts disabled.
>
> See commit 6932bf37 (genirq: Remove IRQF_DISABLED from core code), and
> include/linux/interrupt.h:
>
>
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 APIs for the PHY drivers to
> >> create/destroy a
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 support was working
fine. Now I get "fsl-ehci: USB PHY clo
On Mon, Apr 15, 2013 at 11:26 AM, Sarah Sharp
wrote:
> Cc-ing the public Linux PCI and USB mailing lists.
>
> On Fri, Apr 12, 2013 at 02:59:29PM -0400, Bulkow, David wrote:
>> Susan,
>
> I'm Sarah. :)
>
>> While testing Linux 3.9 we ran into an issue which I believe is a
>> conflict between a coup
Hi Matthijs,
> -Original Message-
> From: Matthijs Kooijman [mailto:matth...@stdin.nl]
>
> 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
> an
> -Original Message-
> From: Matthijs Kooijman [mailto:matth...@stdin.nl]
>
> This simply defines a list of interrupts handled by the the host
> interrupt handler.
>
> Signed-off-by: Matthijs Kooijman
> ---
> drivers/staging/dwc2/core.c | 4 +---
> drivers/staging/dwc2/core.h | 4
>
> -Original Message-
> From: Matthijs Kooijman [mailto:matth...@stdin.nl]
> Sent: Monday, April 15, 2013 7:14 AM
>
> From: Stephen Warren
>
> The top-level hcd interrupt handlers already used irq_return_t, but the
> functions to which it delegates the actual work and the common irq
> han
> From: Matthijs Kooijman [mailto:matth...@stdin.nl]
> Sent: Monday, April 15, 2013 7:14 AM
>
> This function disables all "common interrupts", i.e., those that are
> handled by the common interrupt handler.
>
> Signed-off-by: Matthijs Kooijman
> ---
> drivers/staging/dwc2/core.c | 14
> From: Matthijs Kooijman [mailto:matth...@stdin.nl]
> Sent: Monday, April 15, 2013 7:14 AM
>
> This piece of code manually disabled interrupts, while there are
> perfectly good functions to do this.
>
> Technically, the old code really disabled _all_ interrupts, while the
> new code only disable
> From: Matthijs Kooijman [mailto:matth...@stdin.nl]
> Sent: Monday, April 15, 2013 7:14 AM
>
> Before, enabling common interrupts would implicitly disable all other
> interrupts and enabling host interrupts would disable all interrupts and
> then enable both common and host interrupts.
>
> Now,
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 common interrupt handler additionally did a noop handling
> (it only cleared the flag and n
On Mon, Apr 08, 2013 at 05:18:25PM -0700, Julius Werner wrote:
> diff --git a/drivers/usb/host/xhci-dbg.c b/drivers/usb/host/xhci-dbg.c
> index 5f3a7c7..16a8272 100644
> --- a/drivers/usb/host/xhci-dbg.c
> +++ b/drivers/usb/host/xhci-dbg.c
> @@ -503,11 +503,14 @@ static void xhci_dbg_ep_ctx(struct
> From: Matthijs Kooijman [mailto:matth...@stdin.nl]
> Sent: Monday, April 15, 2013 7:14 AM
>
> This interrupt is currently not enabled anywhere, but there is some
> (dummy) handling for it in the host interrupt handler. This marks it as
> a host mode interrupt, so it makes sense to disable it whe
When CONFIG_XHCI_HCD_DEBUGGING is activated, the XHCI driver can dump
device and input contexts to the console. The endpoint contexts in that
dump are labeled "Endpoint N Context", where N is the XHCI endpoint
index (DCI - 1). This can be very confusing, especially for people who
are not that famil
Hi,
Libusbx v1.0.15 has now been released. A source tarball is available at:
http://sourceforge.net/projects/libusbx/files/releases/1.0.15/source/
This version brings the following fixes and improvements:
* Improve transfer cancellation and avoid short read failures on broken
descriptors
* Fil
Looks fine, except for the "ini" in the subject, which I've corrected to
"init".
This is now applied to my for-usb-linus-queue branch, thanks! You can
see your patch here:
http://git.kernel.org/cgit/linux/kernel/git/sarah/xhci.git/commit/?h=for-usb-linus-queue&id=b3a559901d23b9c391699c23f0d37f20
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 be looking for that conclusion before
> moving forward with
> -Original Message-
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Tuesday, April 16, 2013 1:44 AM
> To: Gonglei (Arei)
> Cc: linux-usb@vger.kernel.org; Yanqiangjun; Hanweidong; Luonengjun;
> kra...@redhat.com; hdego...@redhat.com; qemu-de...@nongnu.org
> Subject: RE: USB2.
On Mon, Apr 15, 2013 at 04:58:01PM -0700, Sarah Sharp wrote:
> Looks fine, except for the "ini" in the subject, which I've corrected to
> "init".
>
> This is now applied to my for-usb-linus-queue branch, thanks! You can
> see your patch here:
>
> http://git.kernel.org/cgit/linux/kernel/git/sarah
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 the light on the device turns completely off and
54 matches
Mail list logo
