On Fri, 2014-08-15 at 08:23 +0800, Peter Chen wrote:
> On Thu, Aug 14, 2014 at 11:54:02AM -0500, Felipe Balbi wrote:
> > Hi,
> >
> > On Thu, Aug 14, 2014 at 09:53:10AM -0700, Tim Bird wrote:
> > > Ping. Anybody know the status of this patch? Is it queued in someone's
> > > tree?
> > > Without i
Bin Liu writes:
> Dirk,
>
> On Thu, Aug 14, 2014 at 1:52 AM, Dirk Gouders wrote:
>> Bin Liu writes:
>>
>>> All,
>>>
>>> On Mon, Nov 18, 2013 at 12:08 PM, Yann E. MORIN
>>> wrote:
Dirk, All,
On 2013-11-07 15:05 +0100, Dirk Gouders spake thusly:
> If choices consist of choice
On 08/15/2014 09:37 AM, Dirk Gouders wrote:
> Here, I still see the problem (I was wondering if the issue has been
> solved/gone by a kconfig-file modification).
>
> Perhaps, Sebastian could check if the problem, he reported still exists...
I will re-test tonight and report. I don't see the patch
> On Thu, Aug 14, 2014 at 11:46:33AM +0200, Hans de Goede wrote:
>> Hi,
...
>>
>> Can you collect "lsusb -v" output for the drive in question when connected
>> through an usb-3 port (the uas module does not need to be loaded).
Here lsusb output, full text as attachment
Bus 003 Device 003: ID 152d
From: "Ivan T. Ivanov"
PHY drivers keep track of the current state of the hardware,
so don't change PHY settings under it.
Signed-off-by: Ivan T. Ivanov
---
drivers/usb/chipidea/ci_hdrc_msm.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/drivers/usb/chipidea/ci_h
On 08/15/2014 12:21 AM, Lion Bino wrote:
> I have a problem a midi controller, a Samson Carbon 61. When I connect
> via usb, dmesg tells me the following.
>
>
> [ 1480.097123] usb 2-1.1: new full-speed USB device number 9
> using ehci_hcd
> [ 1480.118082] usb 2-1.1: no configurati
> > Have you used a bus analyzer on the wire connected to the parent hub's
> > upstream port? If you do, you should be able to see the events leading
> > up to a reset. My guess is that they will all look normal until at some
> > point the HID device stops responding to packets. Probably the hub
>
> > This thread seems to have wandered pretty far off-topic. I just wanted
> > to make the point that if you create another API function for this
> > issue, please be aware that not all controllers/phys will need it or
> > be able to support it. In fact, I think this issue is specific to the
>
hi all:
Is there any test program we can use to capture input data send from
usb keyboard/mouse?
I don't need to parsing the binary sent by keyboard/mouse. Just raw
data is fine.
I checked the Kernel sample, hid-example.c, but it seems only get
report and print it out.
appreciate your help in adv
From: loody
> Is there any test program we can use to capture input data send from
> usb keyboard/mouse?
google usbmon
David
Hi!
I'm working on a student project and have come across a serial
converter that works with the ftdi_sio module after feeding it the
PID:
[ 6606.959890] usb 6-2: new full-speed USB device number 3 using uhci_hcd
[ 6607.143722] usb 6-2: New USB device found, idVendor=0403, idProduct=cb08
The series has been re-worked from v2 onwards to split out the ehci and ohci
parts
into their own drivers / devices like most other ARM platforms based on
feedback from Arnd Bergmann (see here
http://www.spinics.net/lists/linux-usb/msg24.html.
The ehci-platform & ohci-platform have been use
This patch documents the device tree bindings required for the
ehci on-chip controller found in ST consumer electronics SoC's.
Signed-off-by: Peter Griffin
---
Documentation/devicetree/bindings/usb/ehci-st.txt | 39 +++
1 file changed, 39 insertions(+)
create mode 100644 Doc
This patch adds the glue code required to ensure the on-chip OHCI
controller works on STi consumer electronics SoC's from STMicroelectronics.
It mainly manages the setting and enabling of the relevant clocks and manages
the reset / power signals to the IP block.
Signed-off-by: Peter Griffin
---
Signed-off-by: Peter Griffin
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c2066f4..89aef87 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1356,6 +1356,8 @@ F:drivers/pinctrl/pinctrl-st.c
F: drivers/media/rc/st_rc.c
F: driv
This patch documents the device tree bindings required for
the ohci on-chip controller found in ST consumer electronics SoC's.
Signed-off-by: Peter Griffin
---
Documentation/devicetree/bindings/usb/ohci-st.txt | 37 +++
1 file changed, 37 insertions(+)
create mode 100644 Doc
This patch adds the glue code required to ensure the on-chip EHCI
controller works on STi consumer electronics SoC's from STMicroelectronics.
It mainly manages the setting and enabling of the relevant clocks and manages
the reset / power signals to the IP block.
Signed-off-by: Peter Griffin
---
On Fri, 15 Aug 2014, Du, ChangbinX wrote:
> Hi, All,
> As described in runtime_pm.txt for pm_wq:
> The power management work queue pm_wq in which bus types and device
> drivers can put their PM-related work items. It is strongly recommended that
> pm_wq be used for queuing all work items related t
Added support for ekey Converter USB which uses an FT232BM chip.
Also cleaned up some code style warnings, mostly whitespace and some
braces.
* ftdi_sio.c: checkpatch.pl 11E and 27W down to 11E and 21W
* ftdi_sio_ids.h: checkpatch.pl 60W down to 58W, only long lines left
Signed-off-by: Jaša Barte
hi David:
2014-08-15 20:54 GMT+08:00 David Laight :
> From: loody
>> Is there any test program we can use to capture input data send from
>> usb keyboard/mouse?
>
> google usbmon
Sorry for making you confused.
What I need is not monitor usb bus data.
What I need is some user mode program, and when
Hi,
On 08/15/2014 04:00 PM, Lionel wrote:
> Hi Daniel. This is trace when i connect the midi controller.
Thanks. This one here is the setup packet followed by the answer, which
is the device descriptor:
> 8801cbae2a80 1534946150 S Ci:2:000:0 s 80 06 0100 0040 64 <
> 8801cbae2a80 15
On Fri, 15 Aug 2014, David Laight wrote:
> With all the usb dynamic-debug enabled the first errors I see are 'detected
> XactErr'
> len 0/1522 and len 2048/18944 (all 32 retries).
> Then some '3strikes' messages (75 in total split between the endpoints).
>
> I've not yet looked at what those err
Please ignore this patch.
Somewhere in the pipeline all tabs got converted to spaces.
I'll repost soon.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello.
On 08/15/2014 06:03 PM, Peter Griffin wrote:
This patch documents the device tree bindings required for the
ehci on-chip controller found in ST consumer electronics SoC's.
Signed-off-by: Peter Griffin
---
Documentation/devicetree/bindings/usb/ehci-st.txt | 39 ++
On Thu, 14 Aug 2014, Vivek Gautam wrote:
> Now that we have completely moved from older USB-PHY drivers
> to newer GENERIC-PHY drivers for PHYs available with USB controllers
> on Exynos series of SoCs, we can remove the support for the same
> in our host drivers too.
> This should fix the issue o
On Thu, 14 Aug 2014, Vivek Gautam wrote:
> Now that we have completely moved from older USB-PHY drivers
> to newer GENERIC-PHY drivers for PHYs available with USB controllers
> on Exynos series of SoCs, we can remove the support for the same
> in our host drivers too.
> This should fix the issue o
If I understood correctly, you just want to dump the hid output.
You can just cat /sys/kernel/debug/hid/*/events if debugfs is mounted.
Or you may want to have a look at these 2 projects:
hid-recorder -> http://bentiss.github.io/hid-replay-docs/
usbhid-dump-> https://github.com/DIGImend/usbhid-du
This adds a new device id to the pl2303 driver for the ZTEK device.
Reported-by: Mike Chu
Cc: stable
Signed-off-by: Greg Kroah-Hartman
diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
index b3d5a35c0d4b..e9bad928039f 100644
--- a/drivers/usb/serial/pl2303.c
+++ b/drivers
On 08/15/2014 05:25 PM, Lionel wrote:
> Thanks Daniel!
You're welcome!
> I decided to ask the vendor to fix the bug in the firmware. Do I have
> any expectation of success?
Probably not. Most audio hardware vendors don't care about Linux.
> What should be the best way to request
> support for l
On Fri, Aug 15, 2014 at 04:20:14PM +0200, Jaša Bartelj wrote:
> Added support for ekey Converter USB which uses an FT232BM chip.
> Also cleaned up some code style warnings, mostly whitespace and some
> braces.
> * ftdi_sio.c: checkpatch.pl 11E and 27W down to 11E and 21W
> * ftdi_sio_ids.h: checkp
The uSCSI from Newer Technology is a SCSI-USB converter with USB ID 06ca:2003.
Like several other SCSI-USB products, it's a Shuttle Technology OEM device.
Copying the unusual-devs.h entry for device 04e6:0002 allows it to work with
Linux
There are currently six entries for Shuttle-developed SCS
31 matches
Mail list logo
