On Mon, Oct 21, 2013 at 11:57:32AM -0400, Alan Stern wrote:
> On Mon, 21 Oct 2013, Huang Rui wrote:
>
> > + /*
> > +* get generic device-level capability descriptors [9.6.2]
> > +* in USB 3.0 spec
> > +*/
> > + retval = usb_get_descriptor(ude
Fix commit b27c08c953e994f792a03d9b7cbc5cf3f9844135 where dev_set_name()
is used without a string literal as format.
Reported-by: Fengguang Wu
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/f_mass_storage.c |2 +-
1 files changed, 1 insertions(+),
On Fri, Oct 25 2013, Andrzej Pietrasiewicz wrote:
> Fix commit b27c08c953e994f792a03d9b7cbc5cf3f9844135 where dev_set_name()
> is used without a string literal as format.
>
> Reported-by: Fengguang Wu
> Signed-off-by: Andrzej Pietrasiewicz
> Signed-off-by: Kyungmin Park
Acked-by: Michal Nazare
On Fri, Oct 25, 2013 at 02:02:23PM +0800, Peter Chen wrote:
> Due to imx28 usb has special write request, it is not compatible
> with other imx27 sytle usb controllers.
>
> Signed-off-by: Peter Chen
> ---
> arch/arm/boot/dts/imx28.dtsi |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions
Hi,
I used the USB-serial driver option.c to communicate with the GSM modem
device through usb, the used host controller is EHCI. The problem is that
nothing appear on the screen when type characters after using "microcom -s
115200 /dev/ttyUSB3" command to access the ttyUSB3 device node. In nor
On Fri, Oct 25, 2013 at 04:23:32PM +0800, Shawn Guo wrote:
> On Fri, Oct 25, 2013 at 02:02:23PM +0800, Peter Chen wrote:
> > Due to imx28 usb has special write request, it is not compatible
> > with other imx27 sytle usb controllers.
> >
> > Signed-off-by: Peter Chen
> > ---
> > arch/arm/boot/dt
On Fri, Oct 25, 2013 at 04:14:30PM +0800, Peter Chen wrote:
> > > @@ -1041,7 +1041,7 @@
> > > ranges;
> > >
> > > usb0: usb@8008 {
> > > - compatible = "fsl,imx28-usb", "fsl,imx27-usb";
> > > + compatible = "fsl,imx28-usb";
> >
> > You shou
On Thu, Oct 24, 2013 at 02:24:14PM -0700, Praveen Murali wrote:
> Hi,
> I have a USB3.0 hard drive enclosure which works perfectly on my
> desktop (w/ a TI TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller)
> running Debian 3.10-3-amd64 kernel. But when I plug it on my other
> setup (with a VIA VL
From: Wei Yongjun
In case of error, the function platform_device_register_simple() returns
ERR_PTR() and never returns NULL. The NULL test in the return value check
should be replaced with IS_ERR().
Signed-off-by: Wei Yongjun
---
drivers/usb/phy/phy-generic.c | 3 ++-
1 file changed, 2 inserti
On Thu, Oct 24, 2013 at 03:20:02PM +0200, Frank Schäfer wrote:
> Ok, this seems to be a HXD (HX rev. D) chip.
> Could you please validate by checking what Prolifics CheckChipVersion
> tool toll sais ?
It says: "This is a PL-2303 HXD chip".
> It would also be very nice if you could provide a USB-l
On Fri, Oct 25, 2013 at 09:09:27AM +0200, Andrzej Pietrasiewicz wrote:
> Fix commit b27c08c953e994f792a03d9b7cbc5cf3f9844135 where dev_set_name()
> is used without a string literal as format.
>
> Reported-by: Fengguang Wu
> Signed-off-by: Andrzej Pietrasiewicz
> Signed-off-by: Kyungmin Park
Ni
Hello.
On 25-10-2013 11:09, Andrzej Pietrasiewicz wrote:
Fix commit b27c08c953e994f792a03d9b7cbc5cf3f9844135 where dev_set_name()
Please also specify that commit's summary line in parens.
is used without a string literal as format.
Reported-by: Fengguang Wu
Signed-off-by: Andrzej Pie
On Fri, Oct 25, 2013 at 07:16:24AM -0500, Felipe Balbi wrote:
> On Fri, Oct 25, 2013 at 09:09:27AM +0200, Andrzej Pietrasiewicz wrote:
> > Fix commit b27c08c953e994f792a03d9b7cbc5cf3f9844135 where dev_set_name()
> > is used without a string literal as format.
> >
> > Reported-by: Fengguang Wu
> >
Xhci got a lot noisier since I recently updated my phone to the newer version
of iOS.
Possibly it's related to the new feature where it pops up a dialog on the phone
asking if I trust the machine I've plugged into?
This is from an 3.12-rc6 kernel:
xhci_hcd :00:14.0: Port Status Change Event
Am 25.10.2013 12:27, schrieb Mika Westerberg:
> On Thu, Oct 24, 2013 at 03:20:02PM +0200, Frank Schäfer wrote:
>> Ok, this seems to be a HXD (HX rev. D) chip.
>> Could you please validate by checking what Prolifics CheckChipVersion
>> tool toll sais ?
> It says: "This is a PL-2303 HXD chip".
Good,
On Fri, Oct 25, 2013 at 03:01:37PM +0200, Frank Schäfer wrote:
> > Tried few other baudrates > 115200 and they don't work either.
> Urgh... has this device ever been working at baud rates > 115200 ?
I have only used it as a serial console for a device and never tried baud
rates higher than 115200
hi,
On Fri, Oct 25, 2013 at 01:53:46PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Oct 25, 2013 at 07:16:24AM -0500, Felipe Balbi wrote:
> > On Fri, Oct 25, 2013 at 09:09:27AM +0200, Andrzej Pietrasiewicz wrote:
> > > Fix commit b27c08c953e994f792a03d9b7cbc5cf3f9844135 where dev_set_name()
> > > is
On Wed, Oct 23, 2013 at 09:29:22PM +, Paul Zimmerman wrote:
> > From: Matt Porter [mailto:matt.por...@linaro.org]
> > Sent: Wednesday, October 23, 2013 7:43 AM
> >
> > On Tue, Oct 22, 2013 at 04:38:52PM -0500, Rob Herring wrote:
> > > On 10/22/2013 06:25 AM, Matt Porter wrote:
> > > > On Tue,
On Thu, Oct 24, 2013 at 10:51:43AM +0530, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Wednesday 23 October 2013 08:12 PM, Matt Porter wrote:
> > On Tue, Oct 22, 2013 at 04:38:52PM -0500, Rob Herring wrote:
> >> On 10/22/2013 06:25 AM, Matt Porter wrote:
> >>> On Tue, Oct 22, 2013 at 12:48:29PM +020
Am 25.10.2013 15:17, schrieb Mika Westerberg:
> On Fri, Oct 25, 2013 at 03:01:37PM +0200, Frank Schäfer wrote:
>>> Tried few other baudrates > 115200 and they don't work either.
>> Urgh... has this device ever been working at baud rates > 115200 ?
> I have only used it as a serial console for a dev
Hi,
This is the second version of the patch adding support for USB PHY module
of the Exynos series of SoCs by Samsung. The driver is utilising the newly
added Generic PHY Framework by Kishon Vijay Abraham I [1].
In addition to the PHY driver this patchset contains:
- work in progress support for
Add a new driver for the Exynos USB PHY. The new driver uses the generic
PHY framework. The driver includes support for the Exynos 4x10 and 4x12
SoC families.
Signed-off-by: Kamil Debski
Signed-off-by: Kyungmin Park
---
.../devicetree/bindings/phy/samsung-usbphy.txt | 51 +++
drivers/phy/
Change the used phy driver to the new Exynos USB phy driver that uses the
generic phy framework.
Signed-off-by: Kamil Debski
Signed-off-by: Kyungmin Park
---
drivers/usb/gadget/s3c-hsotg.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/gadget/s3c
Change the phy provider used from the old usb phy specific to a new one
using the generic phy framework.
Signed-off-by: Kamil Debski
Signed-off-by: Kyungmin Park
---
drivers/usb/host/ehci-s5p.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/drivers
Add support for Exynos 5250. This is work-in-progress commit. Not
for merging.
Signed-off-by: Kamil Debski
Signed-off-by: Kyungmin Park
---
drivers/phy/Kconfig |7 +
drivers/phy/Makefile |1 +
drivers/phy/phy-exynos-usb.c | 10 +
drivers/phy/phy-exynos-usb
From: Mateusz Krawczuk
Add support for the Samsung's S5PV210 SoC to the Exynos USB PHY driver.
Signed-off-by: Mateusz Krawczuk
[k.deb...@samsung.com: whitespace cleanup and commit description]
Signed-off-by: Kamil Debski
---
drivers/phy/Kconfig |7 ++
drivers/phy/phy-exynos-usb.
On Thu, 24 Oct 2013, Jánosi Zoli wrote:
> Thank you for your help. I just want to ask a lazy question at last. From now
> on i always have to compile the kernel by myself to make it work, or there
> will be some kind of fix for this?
That's up to Felipe. See:
http://marc.info/?l=linu
On Fri, 25 Oct 2013, Hans de Goede wrote:
> Hi,
>
> On 10/24/2013 06:32 PM, Alan Stern wrote:
> > On Thu, 24 Oct 2013, Hans de Goede wrote:
> >
> >> uas devices have 2 alternative settings on their usb-storage interface,
> >> one for usb-storage and one for uas. Using the uas driver is preferred,
Resending in plain-text.
On Thu, Oct 24, 2013 at 11:06 PM, Prasad Koya wrote:
> Hi
>
> I tried with even unmounting the USB before forcing panic and I see same
> time out while getting device descriptor.
>
> From debugs, I see that the portstatus is 0x501 to start with ie,
> (high-speed attached,
On Fri, 25 Oct 2013, Huang Rui wrote:
> On Mon, Oct 21, 2013 at 11:57:32AM -0400, Alan Stern wrote:
> > On Mon, 21 Oct 2013, Huang Rui wrote:
> >
> > > + /*
> > > + * get generic device-level capability descriptors [9.6.2]
> > > + * in USB 3.0 spec
> > > + */
>
On Fri, 25 Oct 2013, Dave Jones wrote:
> Xhci got a lot noisier since I recently updated my phone to the newer version
> of iOS.
> Possibly it's related to the new feature where it pops up a dialog on the
> phone
> asking if I trust the machine I've plugged into?
>
> This is from an 3.12-rc6 ke
On Fri, Oct 25, 2013 at 10:27:56AM -0400, Alan Stern wrote:
> On Fri, 25 Oct 2013, Dave Jones wrote:
>
> > Xhci got a lot noisier since I recently updated my phone to the newer
> > version of iOS.
> > Possibly it's related to the new feature where it pops up a dialog on the
> > phone
> >
On Fri, 25 Oct 2013, Prasad Koya wrote:
> Resending in plain-text.
>
> On Thu, Oct 24, 2013 at 11:06 PM, Prasad Koya wrote:
> > Hi
> >
> > I tried with even unmounting the USB before forcing panic and I see same
> > time out while getting device descriptor.
A better test would be to unbind usb-
Hi,
I'm using a Telit modem with an i.mx28 processor. I'm currently running
a 2.6.35 kernel on that (I know, it's pretty old, and on an other
thread, I'm working on the v3 also). The modem is using the cdc-acm driver.
I can reproduce the problem easiest, if I'm running the following loop:
/
On Thu, 24 Oct 2013, Dan Williams wrote:
> >> Details:
> >> 1/ Port power policy needs 'connector' awareness.
> >>
> >>It is a recipe for unintended device disconnects to turn off a
> >>port while leaving its peer active.
> >
> > "It is a recipe" -- what is "it"? Do you mean that under th
Hi,
On 10/25/2013 03:19 PM, Alan Stern wrote:
On Fri, 25 Oct 2013, Hans de Goede wrote:
Hi,
On 10/24/2013 06:32 PM, Alan Stern wrote:
On Thu, 24 Oct 2013, Hans de Goede wrote:
uas devices have 2 alternative settings on their usb-storage interface,
one for usb-storage and one for uas. Using
Hi,
On Friday 25 October 2013 07:45 PM, Kamil Debski wrote:
> Add a new driver for the Exynos USB PHY. The new driver uses the generic
> PHY framework. The driver includes support for the Exynos 4x10 and 4x12
> SoC families.
>
> Signed-off-by: Kamil Debski
> Signed-off-by: Kyungmin Park
> ---
>
Hi,
On Friday 25 October 2013 07:45 PM, Kamil Debski wrote:
> Add support for Exynos 5250. This is work-in-progress commit. Not
> for merging.
>
> Signed-off-by: Kamil Debski
> Signed-off-by: Kyungmin Park
> ---
> drivers/phy/Kconfig |7 +
> drivers/phy/Makefile |
Hi,
On Friday 25 October 2013 07:45 PM, Kamil Debski wrote:
> From: Mateusz Krawczuk
>
> Add support for the Samsung's S5PV210 SoC to the Exynos USB PHY driver.
>
> Signed-off-by: Mateusz Krawczuk
> [k.deb...@samsung.com: whitespace cleanup and commit description]
> Signed-off-by: Kamil Debski
Hi,
On Friday 25 October 2013 07:45 PM, Kamil Debski wrote:
> Change the phy provider used from the old usb phy specific to a new one
> using the generic phy framework.
looks good :-)
Thanks
Kishon
>
> Signed-off-by: Kamil Debski
> Signed-off-by: Kyungmin Park
> ---
> drivers/usb/host/ehci-
On Friday 25 October 2013 07:45 PM, Kamil Debski wrote:
> Change the used phy driver to the new Exynos USB phy driver that uses the
> generic phy framework.
>
> Signed-off-by: Kamil Debski
> Signed-off-by: Kyungmin Park
> ---
> drivers/usb/gadget/s3c-hsotg.c | 13 -
> 1 file chang
On 10/25/2013 01:48 AM, Sarah Sharp wrote:
On Thu, Oct 24, 2013 at 02:24:14PM -0700, Praveen Murali wrote:
Hi,
I have a USB3.0 hard drive enclosure which works perfectly on my
desktop (w/ a TI TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller)
running Debian 3.10-3-amd64 kernel. But when I pl
On 2013-10-25 17:14, Robert Hodaszi wrote:
Hi,
I'm using a Telit modem with an i.mx28 processor. I'm currently running
a 2.6.35 kernel on that (I know, it's pretty old, and on an other
thread, I'm working on the v3 also). The modem is using the cdc-acm driver.
I can reproduce the problem easie
Add missing USB UGCTRL2 register offset.
Signed-off-by: Valentine Barshak
---
drivers/usb/phy/phy-rcar-gen2-usb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/phy/phy-rcar-gen2-usb.c
b/drivers/usb/phy/phy-rcar-gen2-usb.c
index a99a695..db3ab34 100644
--- a
On Fri, Oct 25, 2013 at 8:23 AM, Alan Stern wrote:
> On Thu, 24 Oct 2013, Dan Williams wrote:
>
>> >> Details:
>> >> 1/ Port power policy needs 'connector' awareness.
>> >>
>> >>It is a recipe for unintended device disconnects to turn off a
>> >>port while leaving its peer active.
>> >
>>
Once we start supporting uas hardware, and as more and more uas devices
become available, we will likely start seeing broken devices. This patch
prepares for the inevitable need for blacklisting those devices.
Signed-off-by: Hans de Goede
---
drivers/usb/storage/uas-detect.h | 11
dri
Note this is done through a usbcore module parameter as the option is needed
by both the uas and usb-storage drivers.
Signed-off-by: Hans de Goede
---
drivers/usb/core/usb.c | 12
drivers/usb/storage/uas-detect.h | 3 +++
include/linux/usb.h | 1 +
3 files c
Hi All,
Here are 2 more patches on top of my patch set of 7 from yesterday. These
add an (empty for now) blacklist, as well as a kernel cmdline option, to
force using usb-storage with devices which advertise uas support so that
we can work around buggy uas devices.
Working on this has also led to
All right, I'm starting to get the overall picture.
This patch set makes a large number of significant changes to important
and subtle aspects of the USB stack. It would be a lot easier to
discuss in pieces; I can't possibly review the whole series in a
reasonable time.
And I wish the basic a
On Oct 25, 2013, at 9:15 AM, Kamil Debski wrote:
> Add a new driver for the Exynos USB PHY. The new driver uses the generic
> PHY framework. The driver includes support for the Exynos 4x10 and 4x12
> SoC families.
>
> Signed-off-by: Kamil Debski
> Signed-off-by: Kyungmin Park
> ---
> .../devic
On Fri, Oct 25, 2013 at 2:11 PM, Alan Stern wrote:
> All right, I'm starting to get the overall picture.
>
Thanks for the patience I really appreciate it.
> This patch set makes a large number of significant changes to important
> and subtle aspects of the USB stack. It would be a lot easier to
From: fre...@asix.com.tw
Date: Thu, 24 Oct 2013 14:58:25 +0800
> From: Freddy Xin
>
> Remove AX_MEDIUM_ALWAYS_ONE in AX_MEDIUM_STATUS_MODE register.
> Setting this bit may cause TX throttling in Half-Duplex mode.
>
> Signed-off-by: Freddy Xin
Applied.
--
To unsubscribe from this list: send th
On Friday, October 25, 2013 11:15 PM, Kamil Debski wrote:
>
> Change the phy provider used from the old usb phy specific to a new one
> using the generic phy framework.
>
> Signed-off-by: Kamil Debski
> Signed-off-by: Kyungmin Park
> ---
> drivers/usb/host/ehci-s5p.c | 21 +++
On Saturday, October 26, 2013 12:50 AM, Kishon Vijay Abraham I wrote:
> On Friday 25 October 2013 07:45 PM, Kamil Debski wrote:
> > From: Mateusz Krawczuk
> >
> > Add support for the Samsung's S5PV210 SoC to the Exynos USB PHY driver.
> >
> > Signed-off-by: Mateusz Krawczuk
> > [k.deb...@samsung.
--
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
55 matches
Mail list logo
