Hi Laurent,
> -Original Message-
> From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
> Sent: Monday, January 21, 2013 6:16 PM
> To: ba...@ti.com
> Cc: Bhupesh SHARMA; linux-usb@vger.kernel.org
> Subject: Re: [PATCH V3 0/5] UVC webcam gadget related changes
>
> Hi Felipe,
>
On Tuesday 29 January 2013 10:51:28 Bjørn Mork wrote:
> A device sending 0 length frames as fast as it can has been
> observed killing the host system due to the resulting memory
> pressure.
>
> Temporarily disable RX skb allocation and URB submission when
> the current error ratio is high, preven
On Mon, Jan 21, 2013 at 10:30:01AM +0800, Peter Chen wrote:
> During the system suspend/resume procedure, the USB also
> needs to go suspend/resume procedure, this patch adds
> related APIs. It is tested at i.mx6q sabrelite. Meanwhile,
> it fixes the bug that the USB will out of work after
> system
Hello,
2013/1/29 Bjørn Mork :
> Dan Williams writes:
>> On Mon, 2013-01-28 at 16:47 +0100, Daniele Palmas wrote:
>>> From: danielepa
>>>
>>> Add PID and special handling for Telit LE920
>>
>> Any idea what interfaces 1 and 5 are? Is one perhaps a pseudo-ethernet
>> interface that could be used
On Wed, Jan 30, 2013 at 11:36:42AM +0530, kishon wrote:
> Hi,
>
> > boolglobal_phy;
> > struct usb_phy *transceiver;
> > struct usb_hcd *hcd;
> >-struct usb_otg otg;
> >+struct usb_otg otg;
> Yo
Vivek Gautam wrote:
>
> Hi Tomasz,
>
>
> On Wed, Jan 16, 2013 at 8:35 PM, Vivek Gautam
> wrote:
> > Hi Tomasz,
> >
> >
> > On Wed, Jan 16, 2013 at 1:19 PM, Tomasz Figa
> wrote:
> >> Hi Vivek,
> >>
> >> Don't you need also some clkdev lookup entry to make the clock
available
> >> in the driver?
On Tue, Jan 29, 2013 at 11:37:22AM +0200, Alexander Shishkin wrote:
> Peter Chen writes:
>
> > On Fri, Jan 25, 2013 at 02:12:20PM +0200, Alexander Shishkin wrote:
> >> Peter Chen writes:
> >>
> >> > On Thu, Jan 24, 2013 at 04:35:30PM +0200, Alexander Shishkin wrote:
> >> >> Peter Chen writes:
Hi,
On Monday 21 January 2013 07:26 AM, Peter Chen wrote:
The main design flow is the same with msm otg driver, that is the id and
vbus interrupt are handled at core driver, others are handled by
individual drivers.
- At former design, when switch usb role from device->host, it will call
udc_st
Vivek Gautam wrote:
>
> Adding PHY driver support for USB 3.0 controller for Samsung's
> SoCs.
>
> Signed-off-by: Vivek Gautam
> ---
>
> Changes from v3:
> - Making SAMSUNG_USB3PHY dependent on SAMSUNG_USBPHY.
> - Adding USB_DWC3 to dependencies of SAMSUNG_USB2PHY since
>dwc3 controller a
Vivek Gautam wrote:
>
> Moving register and structure definitions to header file,
> and keeping the generic functions to be used across
> multiple PHYs in common file "samsung-usbphy.c".
> Also renaming the usb 2.0 phy driver to "samsung-usb2.c"
Just in my opinion, Samsung-usb2phy is more clear?.
On Wednesday 30 January 2013 02:00 AM, Sascha Hauer wrote:
On Tue, Jan 29, 2013 at 07:14:51PM +0530, kishon wrote:
Hi,
On Tuesday 29 January 2013 04:52 PM, Sascha Hauer wrote:
From: Michael Grzeschik
This adds two little devicetree helper functions for determining the
dr_mode (host, peripher
Vivek Gautam wrote:
>
> Adding usb3.0 phy node for Exynos5250 along with the
> necessary device data to be parsed.
>
> Signed-off-by: Vivek Gautam
> ---
> arch/arm/boot/dts/exynos5250.dtsi | 13 +
> 1 files changed, 13 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/boot/
Vivek Gautam wrote:
>
> Adding usbphy node for Exynos5250 along with the
> necessary device data to be parsed.
>
> Signed-off-by: Vivek Gautam
> ---
> arch/arm/boot/dts/exynos5250.dtsi | 15 +++
> 1 files changed, 15 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/boot/dt
On Tue, Jan 29, 2013 at 01:55:04PM +0200, Alexander Shishkin wrote:
> Sascha Hauer writes:
>
> > From: Michael Grzeschik
> >
> > This adds two little devicetree helper functions for determining the
> > dr_mode (host, peripheral, otg) and phy_type (utmi, ulpi,...) from
> > the devicetree.
> >
> >
On Tue, Jan 29, 2013 at 04:01:34PM +, Russell King - ARM Linux wrote:
> On Tue, Jan 29, 2013 at 10:34:53AM -0500, Alan Stern wrote:
> > On Mon, 28 Jan 2013, Russell King - ARM Linux wrote:
> >
> > > On Mon, Jan 28, 2013 at 10:17:33AM -0500, Alan Stern wrote:
> > > > On Mon, 28 Jan 2013, Roger
On Tue, Jan 29, 2013 at 07:14:51PM +0530, kishon wrote:
> Hi,
>
> On Tuesday 29 January 2013 04:52 PM, Sascha Hauer wrote:
> >From: Michael Grzeschik
> >
> >This adds two little devicetree helper functions for determining the
> >dr_mode (host, peripheral, otg) and phy_type (utmi, ulpi,...) from
>
On Tue, Jan 29, 2013 at 03:56:20PM -0300, Ezequiel Garcia wrote:
> Hi Jason,
>
> On Wed, Jan 23, 2013 at 2:40 PM, Jason Cooper wrote:
> > On Wed, Jan 23, 2013 at 02:06:12PM -0300, Ezequiel Garcia wrote:
> >> Jason,
> >>
> >> On Wed, Jan 23, 2013 at 12:26 PM, Ezequiel Garcia
> >> wrote:
> >> > T
Hi Jason,
On Wed, Jan 23, 2013 at 2:40 PM, Jason Cooper wrote:
> On Wed, Jan 23, 2013 at 02:06:12PM -0300, Ezequiel Garcia wrote:
>> Jason,
>>
>> On Wed, Jan 23, 2013 at 12:26 PM, Ezequiel Garcia
>> wrote:
>> > The Armada 370 and Armada XP SoC has an Orion EHCI USB controller.
>> > This patch a
Dan Williams writes:
> On Mon, 2013-01-28 at 16:47 +0100, Daniele Palmas wrote:
>> From: danielepa
>>
>> Add PID and special handling for Telit LE920
>
> Any idea what interfaces 1 and 5 are? Is one perhaps a pseudo-ethernet
> interface that could be used instead of PPP? What's the lsusb -v ou
On Tue, 2013-01-29 at 11:19 -0600, Dan Williams wrote:
> On Mon, 2013-01-28 at 16:47 +0100, Daniele Palmas wrote:
> > From: danielepa
> >
> > Add PID and special handling for Telit LE920
>
> Any idea what interfaces 1 and 5 are? Is one perhaps a pseudo-ethernet
> interface that could be used in
On Mon, 2013-01-28 at 16:47 +0100, Daniele Palmas wrote:
> From: danielepa
>
> Add PID and special handling for Telit LE920
Any idea what interfaces 1 and 5 are? Is one perhaps a pseudo-ethernet
interface that could be used instead of PPP? What's the lsusb -v output
for the device?
Dan
> Sig
On 01/29/2013 06:11 PM, Stephen Warren wrote:
> On 01/29/2013 04:22 AM, Sascha Hauer wrote:
>> From: Michael Grzeschik
>>
>> This adds two little devicetree helper functions for determining the
>> dr_mode (host, peripheral, otg) and phy_type (utmi, ulpi,...) from
>> the devicetree.
>>
>> Signed-of
On 01/29/2013 04:22 AM, Sascha Hauer wrote:
> From: Michael Grzeschik
>
> This adds two little devicetree helper functions for determining the
> dr_mode (host, peripheral, otg) and phy_type (utmi, ulpi,...) from
> the devicetree.
>
> Signed-off-by: Michael Grzeschik
> Signed-off-by: Marc Kleine
On 01/29/2013 06:44 AM, kishon wrote:
> Hi,
>
> On Tuesday 29 January 2013 04:52 PM, Sascha Hauer wrote:
>> From: Michael Grzeschik
>>
>> This adds two little devicetree helper functions for determining the
>> dr_mode (host, peripheral, otg) and phy_type (utmi, ulpi,...) from
>> the devicetree.
On Tue, Jan 29, 2013 at 10:34:53AM -0500, Alan Stern wrote:
> On Mon, 28 Jan 2013, Russell King - ARM Linux wrote:
>
> > On Mon, Jan 28, 2013 at 10:17:33AM -0500, Alan Stern wrote:
> > > On Mon, 28 Jan 2013, Roger Quadros wrote:
> > >
> > > > Make use of devm_request_and_ioremap() and correct com
On Mon, 28 Jan 2013, Russell King - ARM Linux wrote:
> On Mon, Jan 28, 2013 at 10:17:33AM -0500, Alan Stern wrote:
> > On Mon, 28 Jan 2013, Roger Quadros wrote:
> >
> > > Make use of devm_request_and_ioremap() and correct comment.
> >
> > Didn't a big patch come through recently converting all u
On 01/29/2013 05:30 PM, Alan Stern wrote:
> On Tue, 29 Jan 2013, Roger Quadros wrote:
>
>> For each port that is in PHY mode we obtain a PHY device using the USB PHY
>> library and put it out of suspend.
>>
>> It is up to platform code to associate the PHY to the controller's
>> port and it is upt
On Tue, 29 Jan 2013, Roger Quadros wrote:
> For each port that is in PHY mode we obtain a PHY device using the USB PHY
> library and put it out of suspend.
>
> It is up to platform code to associate the PHY to the controller's
> port and it is upto the PHY driver to manage the PHY's resources.
s
On Tue, 29 Jan 2013, Vivek Gautam wrote:
> This change de-asserts vbus_gpio on suspend and
> re-asserts on resume in order to save power.
> NOTE, this change means no USB charging in suspend
> mode.
Doing this would mean USB devices could not wake up the system. This
would be unacceptable.
How
On Tue, 29 Jan 2013, Anton Tikhomirov wrote:
> Hello,
>
> Sorry for my haste, I missed that. We have situation when CPU
> stalls in usb_hcd_flush_endpoint(), so at first glance it looked
> strange for me. Will analyze more.
If you provide more information, maybe I can help guide your analysis.
On 01/29/2013 03:55 PM, Wolfram Sang wrote:
>
>> I prefer u32 here, because we have the matching enum. Otherwise we end
>> up with:
>>
>> of_property_read_string(...,&type);
>>
>> if (!strcmp(type, "ulpi"))
>> foo();
>> else if (!strcmp(type, "utmi"))
>> bar();
>> else if (!strcmp(type,
> I prefer u32 here, because we have the matching enum. Otherwise we end
> up with:
>
> of_property_read_string(...,&type);
>
> if (!strcmp(type, "ulpi"))
> foo();
> else if (!strcmp(type, "utmi"))
> bar();
> else if (!strcmp(type, "pipe3"))
> baz();
> else
> BUG();
>
>
Hi,
On Tue, Jan 29, 2013 at 07:40:23PM +0530, kishon wrote:
> On Tuesday 29 January 2013 07:23 PM, Wolfram Sang wrote:
> >>>+ err = of_property_read_string(np, "phy_type", &phy_type);
> >>>+ if (err < 0)
> >>>+ return USBPHY_INTERFACE_MODE_NA;
> >>
> >>Why don't we use a u32 property ty
On Tuesday 29 January 2013 07:23 PM, Wolfram Sang wrote:
+ err = of_property_read_string(np, "phy_type", &phy_type);
+ if (err < 0)
+ return USBPHY_INTERFACE_MODE_NA;
Why don't we use a u32 property type for the *phy-type*? IMHO we
should use string property only when
> >+err = of_property_read_string(np, "phy_type", &phy_type);
> >+if (err < 0)
> >+return USBPHY_INTERFACE_MODE_NA;
>
> Why don't we use a u32 property type for the *phy-type*? IMHO we
> should use string property only when the property should be
> absolutely unambiguous (e.g.
Hi,
On Tuesday 29 January 2013 04:52 PM, Sascha Hauer wrote:
From: Michael Grzeschik
This adds two little devicetree helper functions for determining the
dr_mode (host, peripheral, otg) and phy_type (utmi, ulpi,...) from
the devicetree.
Signed-off-by: Michael Grzeschik
Signed-off-by: Marc Kl
On Tue, Jan 29, 2013 at 09:37:08AM +0100, Alessandro Zappala wrote:
>
> [1.] Low speed when
> transferring files over USB flash drives
>
> [2.] Bug
> Description
>
> Low speed when transferring files over USB 2.0
> and USB 3.0. Example USB flash devices with FAT that demonstrates
> this problem:
On 29-01-2013 15:20, Sergei Shtylyov wrote:
This patch makes musb can work on blackfin bf60x series platform.
Bf60x uses MHDRC RTL version 2.0 musb ip core which don't need a lot of
blackfin
specific anomalies anymore.
Signed-off-by: Bob Liu
---
drivers/usb/musb/Kconfig |2 +-
dri
On Tue, Jan 22, 2013 at 9:01 PM, Vivek Gautam wrote:
> Changes from v1:
> - Putting separate device nodes for usb 2.0 phy and usb 3.0 phy
>based on separate driver for samsung usb 3.0 phy and
>samsung usb 2.0 phy:
>[PATCH v3 0/2] Adding USB 3.0 DRD-phy support for exynos5250
>[PAT
Hello.
On 28-01-2013 19:47, Daniele Palmas wrote:
From: danielepa
Name/email should preferrably be the same as the one in your signoff.
Besides, the email address is not valid here.
Add PID and special handling for Telit LE920
Signed-off-by: Daniele Palmas
WBR, Sergei
--
To un
Hi Oliver,
On Tue, Jan 29, 2013 at 5:07 PM, Oliver Neukum wrote:
> On Tuesday 29 January 2013 16:22:45 Vivek Gautam wrote:
>> This change de-asserts vbus_gpio on suspend and
>> re-asserts on resume in order to save power.
>> NOTE, this change means no USB charging in suspend
>> mode.
>
> What ha
Sascha Hauer writes:
> From: Michael Grzeschik
>
> This adds two little devicetree helper functions for determining the
> dr_mode (host, peripheral, otg) and phy_type (utmi, ulpi,...) from
> the devicetree.
>
> Signed-off-by: Michael Grzeschik
> Signed-off-by: Marc Kleine-Budde
> ---
>
> The p
On Tuesday 29 January 2013 16:22:45 Vivek Gautam wrote:
> This change de-asserts vbus_gpio on suspend and
> re-asserts on resume in order to save power.
> NOTE, this change means no USB charging in suspend
> mode.
What happens if a device on the bus is a source of wakeups?
Regards
From: Michael Grzeschik
This adds two little devicetree helper functions for determining the
dr_mode (host, peripheral, otg) and phy_type (utmi, ulpi,...) from
the devicetree.
Signed-off-by: Michael Grzeschik
Signed-off-by: Marc Kleine-Budde
---
The properties and their values have been taken
Hello.
On 29-01-2013 11:41, Bob Liu wrote:
This patch makes musb can work on blackfin bf60x series platform.
Bf60x uses MHDRC RTL version 2.0 musb ip core which don't need a lot of blackfin
specific anomalies anymore.
Signed-off-by: Bob Liu
---
drivers/usb/musb/Kconfig |2 +-
dri
This change de-asserts vbus_gpio on suspend and
re-asserts on resume in order to save power.
NOTE, this change means no USB charging in suspend
mode.
Signed-off-by: Vivek Gautam
CC: Doug Anderson
---
Based on 'usb-next'.
drivers/usb/host/ehci-s5p.c | 29 ++---
1 file
On Tue, Jan 29, 2013 at 12:08:23PM +0200, Roger Quadros wrote:
> On 01/29/2013 11:57 AM, Felipe Balbi wrote:
> > Hi,
> >
> > On Tue, Jan 29, 2013 at 11:50:32AM +0200, Roger Quadros wrote:
> >> For each port that is in PHY mode we obtain a PHY device using the USB PHY
> >> library and put it out of
On 01/29/2013 11:57 AM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Jan 29, 2013 at 11:50:32AM +0200, Roger Quadros wrote:
>> For each port that is in PHY mode we obtain a PHY device using the USB PHY
>> library and put it out of suspend.
>>
>> It is up to platform code to associate the PHY to the contr
Hi,
On Tue, Jan 29, 2013 at 11:50:32AM +0200, Roger Quadros wrote:
> For each port that is in PHY mode we obtain a PHY device using the USB PHY
> library and put it out of suspend.
>
> It is up to platform code to associate the PHY to the controller's
> port and it is upto the PHY driver to manag
A device sending 0 length frames as fast as it can has been
observed killing the host system due to the resulting memory
pressure.
Temporarily disable RX skb allocation and URB submission when
the current error ratio is high, preventing us from trying to
allocate an infinite number of skbs. Reena
For each port that is in PHY mode we obtain a PHY device using the USB PHY
library and put it out of suspend.
It is up to platform code to associate the PHY to the controller's
port and it is upto the PHY driver to manage the PHY's resources.
Also remove wired spacing around declarations we come
Peter Chen writes:
> On Fri, Jan 25, 2013 at 02:12:20PM +0200, Alexander Shishkin wrote:
>> Peter Chen writes:
>>
>> > On Thu, Jan 24, 2013 at 04:35:30PM +0200, Alexander Shishkin wrote:
>> >> Peter Chen writes:
>> >>
>> >> > - Create init/destroy API for probe and remove
>> >> > - start/stop
Daniele Palmas writes:
> 2013/1/28 Bjørn Mork :
>
>> Thanks for adding this device. But the patch doesn't apply to the
>> current "net" tree. Care to rebase it?
>>
>
> Sure. Should I use the following git repository
>
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/net-next.git
>
> ?
No,
This patch change blackfin.c to support musb for blackfin bf60x series soc
platform.
Signed-off-by: Bob Liu
---
drivers/usb/musb/blackfin.c | 72 +++
1 file changed, 46 insertions(+), 26 deletions(-)
diff --git a/drivers/usb/musb/blackfin.c b/drivers/us
This patch makes musb framework can support blackfin bf60x series soc platform.
Bf60x uses MHDRC RTL version 2.0 musb ip core which don't need a lot of
blackfin specific anomalies anymore.
Signed-off-by: Bob Liu
---
drivers/usb/musb/Kconfig |2 +-
drivers/usb/musb/musb_core.c |6
On Tue, Jan 29, 2013 at 04:37:27PM +0800, Bob Liu wrote:
> On Tue, Jan 29, 2013 at 3:50 PM, Felipe Balbi wrote:
> > Hi,
> >
> > On Tue, Jan 29, 2013 at 03:41:39PM +0800, Bob Liu wrote:
> >> This patch makes musb can work on blackfin bf60x series platform.
> >> Bf60x uses MHDRC RTL version 2.0 musb
[1.] Low speed when
transferring files over USB flash drives
[2.] Bug
Description
Low speed when transferring files over USB 2.0
and USB 3.0. Example USB flash devices with FAT that demonstrates
this problem:
ID 13fe:4100 Kingston Technology Company
Inc.
ID 090c:1000 Silicon Motion, Inc. - Tai
On Tue, Jan 29, 2013 at 3:50 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Jan 29, 2013 at 03:41:39PM +0800, Bob Liu wrote:
>> This patch makes musb can work on blackfin bf60x series platform.
>> Bf60x uses MHDRC RTL version 2.0 musb ip core which don't need a lot of
>> blackfin
>> specific anomalies
Hello,
2013/1/28 Bjørn Mork :
> Daniele Palmas writes:
>
>> Add VID, PID and fixed interface for Telit LE920
>>
>> Signed-off-by: Daniele Palmas
>> ---
>> drivers/net/usb/qmi_wwan.c |1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/net/usb/qmi_wwan.c b/dri
According to "musbhdrd usb 2.0 high-speed dual-role controller
Product Specification"
the number of dma channels can be read from register RAMINFO.
it is not always that number of dma channels is MUSB_HSDMA_CHANNELS, some
SOC may have little dma channels.
Signed-off-by: Yingchun Li
---
drivers/us
60 matches
Mail list logo
