Mathew Binkley wrote:
> Hi all. Could someone tell me how to associate a USB Bus:Device
> info with a /dev/entry?
This is subsystem-specific. Feel free to take inspiration from my
script for usb-serial at http://stuge.se/find430.sh
You'll have to change the code inside:
for usbiface in "${port
Hi,
I recently upgraded from 3.3 to 3.5 kernel (gentoo). A USB device
(Midisport2x2) depends on firmware loading using fxload from a udev
rules script. Without usbfs, can someone give me a recommendation for
replacing the udev script to load the firmware?
At the moment, I compiled the 3.5 kernel
On Sun, Sep 16, 2012 at 10:03:49AM -0400, Unknown wrote:
> Hi,
>
> I recently upgraded from 3.3 to 3.5 kernel (gentoo). A USB device
> (Midisport2x2) depends on firmware loading using fxload from a udev
> rules script. Without usbfs, can someone give me a recommendation for
> replacing the udev sc
Peter Stuge wrote:
> > Hi all. Could someone tell me how to associate a USB Bus:Device
> > info with a /dev/entry?
>
> This is subsystem-specific. Feel free to take inspiration from my
> script for usb-serial at http://stuge.se/find430.sh
>
> You'll have to change the code inside:
> for usbifa
On Sun, 2012-09-16 at 07:30 -0700, Greg KH wrote:
> On Sun, Sep 16, 2012 at 10:03:49AM -0400, Unknown wrote:
> > Hi,
> >
> > I recently upgraded from 3.3 to 3.5 kernel (gentoo). A USB device
> > (Midisport2x2) depends on firmware loading using fxload from a udev
> > rules script. Without usbfs, ca
On Fri, Sep 14, 2012 at 12:01:36 -0700, Sarah Sharp wrote:
some logs with the 0x4000 quirk enabled.. I tried to write to a file
on VFAT fs—the Transcend SDHC again—I got only IO error and
when mounted on USB2 port, filesystem had 0-byte file.
sarah-quirk-dmesg.txt
(action starts at 180 seconds)
last patch introduces a copy of each descriptor for each function. Most
gadgets were doing this but not all of them.
The remaining patches are fixes which I noticed while inspecting each
function. One thing that is still not done properly:
We have no function to return/free endpoints and interface
In case something goes wrong here, don't leak memory / endpoints.
Cc: Yadwinder Singh
Cc: Jaswinder Singh
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/f_uac2.c | 25 ++---
1 file changed, 22 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/gadget
This function works only on FS or HS. If the gadget is HS capable only
HS descriptors are assigned. If we plug it to an 1.1 host it won't work
because we have only 2.0 descriptors. This patch changes the behavior to
provide both sets.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadg
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/f_phonet.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/f_phonet.c b/drivers/usb/gadget/f_phonet.c
index 8ee9268..a6c19a4 100644
--- a/drivers/usb/gadget/f_phonet.c
+++ b/drivers/u
The HS descriptors are only created if HS is supported by the UDC but we
never free them.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/f_midi.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/gadget/f_midi.c b/drivers/usb/gadget/f_midi.c
index b2522ba..b978c
I think this wrong since 72c973dd ("usb: gadget: add
usb_endpoint_descriptor to struct usb_ep"). If we fail to allocate an ep
or bail out early we shouldn't check for the descriptor which is
assigned at ep_enable() time.
Cc: Tatyana Brokhman
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/
Whether highspeed configuration is valid or not is something that
composite decides and not the gadget. That gadget can only provide the
required descriptors for it.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/f_midi.c |1 -
drivers/usb/gadget/f_uac1.c |1 -
2 files c
HS and SS descriptors are staticaly created. They are updated during the
bind process with the endpoint address, string id or interface numbers.
After that, the descriptor chain is linked to struct usb_function which
is used by composite in order to serve the GET_DESCRIPTOR requests,
number of avai
The "video->minor = -1" assigment is done in V4L2 by
video_register_device() so it is removed here.
Now. uvc_function_bind() calls in error case uvc_function_unbind() for
cleanup. The problem is that uvc_function_unbind() frees the uvc struct
and uvc_bind_config() does as well in error case of usb_
On Sun, Sep 16, 2012 at 01:38:56PM -0400, Unknown wrote:
> On Sun, 2012-09-16 at 07:30 -0700, Greg KH wrote:
> > On Sun, Sep 16, 2012 at 10:03:49AM -0400, Unknown wrote:
> > > Hi,
> > >
> > > I recently upgraded from 3.3 to 3.5 kernel (gentoo). A USB device
> > > (Midisport2x2) depends on firmware
>
> The PHY framework provides a set of API's for the PHY drivers to
> create/remove a PHY and the PHY users to obtain a reference to the PHY
> using or without using phandle. If the PHY users has to obtain a
> reference to
> the PHY without using phandle, the platform specfic intialization code
On Sun, 16 Sep 2012, Sami Farin wrote:
> On Fri, Sep 14, 2012 at 12:01:36 -0700, Sarah Sharp wrote:
>
> some logs with the 0x4000 quirk enabled.. I tried to write to a file
> on VFAT fs—the Transcend SDHC again—I got only IO error and
> when mounted on USB2 port, filesystem had 0-byte file.
>
>
Hi Felipe,
Below are two patches to split some phy related things from
otg.
Peter Chen (2):
usb: phy: rename enum usb_otg_state to usb_state
usb: phy: rename otg.c to phy.c
drivers/usb/otg/Makefile |3 -
drivers/usb/otg/isp1301_omap.c |4 +-
drivers/usb/otg/otg.c | 2
These states are not all otg specific, and they stands for
general usb state.
Signed-off-by: Peter Chen
---
drivers/usb/otg/isp1301_omap.c |4 ++--
drivers/usb/otg/otg.c | 12 +++-
drivers/usb/otg/otg_fsm.c |6 +++---
include/linux/usb/msm_hsusb.h |2 +-
incl
The operations in current otg.c are actually for USB PHY's
Move it from drivers/usb/otg/ to drivers/usb/phy/
Signed-off-by: Peter Chen
---
drivers/usb/otg/Makefile |3 -
drivers/usb/otg/otg.c| 239 --
drivers/usb/phy/Makefile |3 +
drivers
On Mon, Sep 17, 2012 at 12:18 AM, Peter Chen wrote:
> The operations in current otg.c are actually for USB PHY's
> Move it from drivers/usb/otg/ to drivers/usb/phy/
>
> Signed-off-by: Peter Chen
> ---
> drivers/usb/otg/Makefile |3 -
> drivers/usb/otg/otg.c| 239
> -
The series enables multi-platform support for imx. Since the required
frameworks (clk, pwm) and spare_irq have already been adopted on imx,
the series is all about cleaning up mach/* headers. Along with the
changes, arch/arm/plat-mxc gets merged into arch/arm/mach-imx.
It's based on a bunch of b
The inclusion of mach/hardware.h is not used by the driver at all.
Remove it.
Signed-off-by: Shawn Guo
Cc: Greg Kroah-Hartman
Cc: linux-usb@vger.kernel.org
---
drivers/usb/host/ehci-mxc.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/usb/host/ehci-mxc.c b/drivers/usb/host/ehci-m
Hi,
On Mon, Sep 17, 2012 at 6:50 AM, Chen Peter-B29397 wrote:
>
>>
>> The PHY framework provides a set of API's for the PHY drivers to
>> create/remove a PHY and the PHY users to obtain a reference to the PHY
>> using or without using phandle. If the PHY users has to obtain a
>> reference to
>> t
On Mon, Sep 17, 2012 at 1:28 AM, Sebastian Andrzej Siewior
wrote:
> In case something goes wrong here, don't leak memory / endpoints.
>
> Cc: Yadwinder Singh
> Cc: Jaswinder Singh
> Signed-off-by: Sebastian Andrzej Siewior
> ---
> drivers/usb/gadget/f_uac2.c | 25 ++---
>
>
> On Mon, Sep 17, 2012 at 12:18 AM, Peter Chen
> wrote:
> > The operations in current otg.c are actually for USB PHY's
> > Move it from drivers/usb/otg/ to drivers/usb/phy/
> >
> > Signed-off-by: Peter Chen
> > ---
> > drivers/usb/otg/Makefile |3 -
> > drivers/usb/otg/otg.c| 239 -
27 matches
Mail list logo
