It looks like this typo was introduced by a mistake in a copy-and-paste in
commit ddbe32491951.
Signed-off-by: Adam Cozzette
---
drivers/hid/usbhid/usbkbd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hid/usbhid/usbkbd.c b/drivers/hid/usbhid/usbkbd.c
index 7960869
Dear Peter Chen,
> > Probe the usbmisc driver earlier, otherwise the ci_hdrc_imx.c will
> > get -EPROBE_DEFER from usbmisc when both are compiled into the kernel
> > and thus USB gadget mode won't work.
>
> Hi Marek, you know the root cause of it, you suggested using
> a better way to fix it.
>
this series introduces support for the common clock framework (CCF,
COMMON_CLK Kconfig option) in the PowerPC based MPC512x platform, which
brings device tree based clock lookup as well
at subsystem maintainers:
this series was streamlined for conflict free application through the
subsystems' ind
after device tree based clock lookup became available, the peripheral
driver need no longer construct clock names which include the component
index -- remove the "usb%d_clk" template, always use "ipg" instead
Cc: Greg Kroah-Hartman
Cc: linux-usb@vger.kernel.org
Signed-off-by: Gerhard Sittig
---
Is there a way to tell if a USB device is in use or not before requesting the
kernel detach drivers?
I'd define "in use" as either an interface claimed on usbfs or tty/etc
provided by a kernel driver being opened. And "not in use" including "kernel
driver attached, but not interfacing device to
Hi Paul/Felipe,
Any comment?
Regards
Pratyush
On Fri, Nov 15, 2013 at 09:34:44AM +0530, Pratyush Anand wrote:
> Hi,
>
> Patch "usb: dwc3: gadget: drop dwc3 manual phy control" says
>
> "Recent versions of the core, can suspend and resume the PHYs
> automatically, so we don't need to fiddle wit
On Mon, Nov 18, 2013 at 01:44:19AM +, Luke-Jr wrote:
> Is there a way to tell if a USB device is in use or not before requesting the
> kernel detach drivers?
Not really, sorry.
> I'd define "in use" as either an interface claimed on usbfs or tty/etc
> provided by a kernel driver being opene
On Monday, November 18, 2013 4:40:55 AM Greg KH wrote:
> On Mon, Nov 18, 2013 at 01:44:19AM +, Luke-Jr wrote:
> > Is there a way to tell if a USB device is in use or not before requesting
> > the kernel detach drivers?
>
> Not really, sorry.
>
> > I'd define "in use" as either an interface cl
On Mon, Nov 18, 2013 at 05:35:53AM +, Luke-Jr wrote:
> On Monday, November 18, 2013 4:40:55 AM Greg KH wrote:
> > On Mon, Nov 18, 2013 at 01:44:19AM +, Luke-Jr wrote:
> > > Is there a way to tell if a USB device is in use or not before requesting
> > > the kernel detach drivers?
> >
> > No
While I hunt an other problem with my UPLI I see this problem.
Linux-next 20131105 source.
commit bd6a053d0497bc71e182e8a1063a8ae7d803fc7d
Author: Chris Ruehl
Date: Mon Nov 18 14:21:58 2013 +0800
Fix wrong pointer when remap UTMI pad
diff --git a/drivers/usb/phy/phy-tegra-usb.c b/driver
> -Original Message-
> From: Chris Ruehl [mailto:chris.ru...@gtsys.com.hk]
> Sent: Monday, November 18, 2013 11:56 AM
> To: linux-usb@vger.kernel.org; Venu Byravarasu; Greg Kroah-Hartman
> Subject: phy-tegra-usb.c: wrong pointer check for remap UTMI
>
>
> While I hunt an other problem wit
On Fr, 2013-11-15 at 16:06 +0100, Hans de Goede wrote:
> task management commands expect a response_iu rather then a sense_iu,
> and
> these have different sizes. Make the urb we submit to get the reply
> the right
> size.
I think that doesn't work for uas in usb2 (no streams) mode. status
urbs a
On Monday, November 18, 2013 6:07:37 AM Greg KH wrote:
> > I want my software to ignore devices that are already in use by other
> > software. The "other software" might be accessing it via the kernel
> > drivers, or perhaps libusb. My software (in this case) would be using
> > libusb, and need to
13 matches
Mail list logo
