>
> Which one? The MX28 p-o-s? Skimming through it's sources, I already used
> two
> puking bags, more to be filled tho.
>
mx23,mx28, maybe mx6x is the same.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More
Dear Chen Peter-B29397,
> > Which one? The MX28 p-o-s? Skimming through it's sources, I already used
> > two
> > puking bags, more to be filled tho.
>
> mx23,mx28, maybe mx6x is the same.
I use the MX28, so I made these two patches (follow). I'll roll them into an
official thingie and submit pr
Hi Anton,
On Thu, August 2, 2012 1:09 am, Anton Tikhomirov wrote:
>
>
>> -Original Message-
>> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
>> ow...@vger.kernel.org] On Behalf Of Ido Shayevitz
>> Sent: Wednesday, August 01, 2012 11:44 PM
>> To: Anton Tikhomirov
>> Cc: 'Ido Sha
Hi Paul,
On Wed, August 1, 2012 1:08 pm, Paul Zimmerman wrote:
>> From: Ido Shayevitz [mailto:i...@codeaurora.org]
>> Sent: Wednesday, August 01, 2012 7:25 AM
>>
>> On Mon, July 30, 2012 12:00 pm, Paul Zimmerman wrote:
>> >> From: Ido Shayevitz [mailto:i...@codeaurora.org]
>> >> Sent: Monday, Jul
On Sunday, August 05, 2012, Alan Stern wrote:
> On Sat, 4 Aug 2012, Rafael J. Wysocki wrote:
>
> > On Saturday, August 04, 2012, Alan Stern wrote:
> > > On Sat, 4 Aug 2012, Rafael J. Wysocki wrote:
> > >
> > > > > That wasn't what he meant. What if the code needs to run in the
> > > > > _same_
On Sun, Aug 05, 2012 at 10:59:38AM +0800, Fengguang Wu wrote:
> Hi all,
>
> This line triggers an oops in kvm boot test:
>
> usb_match_id():
> ==> 748 for (; id->idVendor || id->idProduct || id->bDeviceClass
> ||
> 749id->bInterfaceClass || id->driver_info;
On 03.08.2012 17:48, Hiremath, Vaibhav wrote:
> On Fri, Aug 03, 2012 at 17:11:38, Daniel Mack wrote:
>> On 03.08.2012 11:07, Hiremath, Vaibhav wrote:
>>> I have just pushed the code (V7 which Ravi submitted), so can you please
>>> try
>>> with below branch?
>>>
>>> https://github.com/hvaibhav/am
On Sat, Aug 04, 2012 at 11:46:36PM +0200, Marek Vasut wrote:
> Greg, do you please have any solution for this problem? Basically, the probe
> of
> hid fails on the fact that the HID_GLOBAL_ITEM_TAG_REPORT_SIZE is 128, while
> right now it's capped at 96.
>
> Shall I submit a patch that increase
Hi guys!
I think I might have hit a bug:
* Description of the issue *
Continuous (variable time 1-10 mins) small bulk transfers (between 1-6
bytes payload) either with libusb, or generic USB serial driver, leaves the
app in uninterruptible wait state (i.e., hung).
The kernel hung task stack dump
On Sun, 5 Aug 2012, Tomas Sokorai wrote:
> Hi guys!
>
> I think I might have hit a bug:
>
> * Description of the issue *
> Continuous (variable time 1-10 mins) small bulk transfers (between 1-6
> bytes payload) either with libusb, or generic USB serial driver, leaves the
> app in uninterruptible
Hi Praveen,
Am Mittwoch, 1. August 2012, 15:05:47 schrieb Praveen Paneri:
> This driver uses usb_phy interface to interact with s3c-hsotg. Supports
> phy_init and phy_shutdown functions to enable/disable phy. Tested with
> smdk6410 and smdkv310. More SoCs can be brought under later.
Looks cool.
The Freescale i.MX28 BootROM USB recovery mode implements the USB HID
protocol, yet the global item tag report size is 128. Linux checks if
this is 96 as of now, see [1]. This causes Linux to refuse to communicate
with this device, making it impossible to use the recovery mode.
This is not a stand
The USB recovery mode present in i.MX28 ROM emulates USB HID.
It needs this quirk to behave properly.
Signed-off-by: Marek Vasut
Cc: Chen Peter
Cc: Greg KH
Cc: Jiri Kosina
---
drivers/hid/hid-ids.h |3 +++
drivers/hid/usbhid/hid-quirks.c |1 +
2 files changed, 4 insertions(+
[...]
> diff --git a/drivers/hid/usbhid/hid-quirks.c
> b/drivers/hid/usbhid/hid-quirks.c index 903eef3..6a09570 100644
> --- a/drivers/hid/usbhid/hid-quirks.c
> +++ b/drivers/hid/usbhid/hid-quirks.c
> @@ -101,6 +101,7 @@ static const struct hid_blacklist {
> { USB_VENDOR_ID_SIGMA_MICRO, USB_
On Sun, Aug 5, 2012 at 5:36 PM, Alan Stern wrote:
> Build a kernel with CONFIG_USB_DEBUG enabled (and also
> CONFIG_DEBUG_FS). When the hang occurs, go into the subdirectory of
> /sys/kernel/debug/usb/ohci/ corresponding to the bus the device is
> plugged into (:00:04.0 if your setup hasn't c
Hi Alan, Felipe, Greg
These are v3 of ehci/ohci-platform patches
Kuninori Morimoto (4):
usb: host: ehci-platform: BUG_ON() to WARN_ON() on probe
usb: host: ohci-platform: BUG_ON() to WARN_ON() on probe
usb: host: ehci-platform: add platform specific power callback
usb: ho
We should avoid using BUG_ON() in drivers.
This patch switch to use WARN_ON() from BUG_ON(),
and avoid NULL pointer access by new macro.
Signed-off-by: Kuninori Morimoto
---
v2 -> v3
- BUG_ON -> WARN_ON
drivers/usb/host/ehci-platform.c | 18 ++
1 files changed, 10 insertions
We should avoid using BUG_ON() in drivers.
This patch switch to use WARN_ON() from BUG_ON(),
and avoid NULL pointer access by new macro.
Signed-off-by: Kuninori Morimoto
---
v2 -> v3
- BUG_ON -> WARN_ON
drivers/usb/host/ohci-platform.c | 10 ++
1 files changed, 6 insertions(+), 4 de
This patch enables to call platform specific power callback function.
Signed-off-by: Kuninori Morimoto
---
v2 -> v3
- add power multi functions
- call it by macro
drivers/usb/host/ehci-platform.c | 40 ++---
include/linux/usb/ehci_pdriver.h |5
2 fi
This patch enables to call platform specific power callback function.
Signed-off-by: Kuninori Morimoto
---
v2 -> v3
- add power multi functions
- call it by macro
drivers/usb/host/ohci-platform.c | 36 +---
include/linux/usb/ohci_pdriver.h |5 +
2 fi
Fix config warning:
warning: ( ... && DRM_USB) selects USB which has unmet direct dependencies
(USB_SUPPORT && USB_ARCH_HAS_HCD)
by adding the missing dependency on USB_ARCH_HAS_HCD to DRM_UDL and DRM_USB.
This exposes:
drivers/video/Kconfig:36:error: recursive dependency detected!
drivers/video
This driver provides support for several Kvaser CAN/USB devices.
Such kind of devices supports up to three can network interfaces.
It has been tested with a Kvaser USB Leaf Light (one network interface)
connected to a pch_can interface.
The firmware version of the Kvaser device was 2.5.205.
List
Hi Felipe, Greg
These are bug fix patches of renesas_usbhs.
Without these patches, renesas_usbhs suspend/resume will be failed
on Host mode.
Kuninori Morimoto (2):
usb: renesas_usbhs: mod_host: add missing .bus_suspend/resume
usb: renesas_usbhs: fixup resume method for autonomy mode
suspend/resume will failed on renesas_usbhs without this patch.
Signed-off-by: Kuninori Morimoto
---
drivers/usb/renesas_usbhs/mod_host.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/renesas_usbhs/mod_host.c
b/drivers/usb/renesas_usbhs/mod_host.c
i
If renesas_usbhs is probed as autonomy mode,
phy reset should be called after power resumed,
and manual cold-plug should be called with slight delay.
Signed-off-by: Kuninori Morimoto
---
drivers/usb/renesas_usbhs/common.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --gi
On Mon, Aug 06, 2012 at 01:22:53, Daniel Mack wrote:
> On 03.08.2012 17:48, Hiremath, Vaibhav wrote:
> > On Fri, Aug 03, 2012 at 17:11:38, Daniel Mack wrote:
> >> On 03.08.2012 11:07, Hiremath, Vaibhav wrote:
> >>> I have just pushed the code (V7 which Ravi submitted), so can you please
> >>> try
26 matches
Mail list logo
