On 02/27/2013 10:13 PM, Bjorn Helgaas wrote:
[+cc Andy]
On Wed, Feb 20, 2013 at 11:53 PM, Hannes Reinecke wrote:
On 02/20/2013 05:57 PM, Yinghai Lu wrote:
On Tue, Feb 19, 2013 at 11:58 PM, Hannes Reinecke wrote:
Apparently this device is meant to use MSI _only_ so the BIOS developer
did
Hi,
On Thu, Feb 28, 2013 at 08:09:33PM +0530, Vivek Gautam wrote:
> On Thu, Jan 31, 2013 at 9:08 PM, Felipe Balbi wrote:
> > On Thu, Jan 31, 2013 at 09:00:37PM +0530, Vivek Gautam wrote:
> >> Hi Felipe,
> >>
> >>
> >> On Thu, Jan 31, 2013 at 8:55 PM, Felipe Balbi wrote:
> >> > Hi,
> >> >
> >> >
Hi,
On Thu, Feb 28, 2013 at 04:51:29PM +0530, Pratyush Anand wrote:
> On 2/28/2013 4:18 PM, Felipe Balbi wrote:
> >>+ if (list_empty(&dep->req_queued))
> >>>+ dep->flags &= ~DWC3_EP_BUSY;
> >not sure this is correct. Whenever req_queue isn't empty, we call
> >dwc3_stop_active_transfer()
Hi,
On Thu, Feb 28, 2013 at 01:55:30PM +0200, Alexander Shishkin wrote:
> >> >> > > > > > > If the probe fails, the ci13xxx_add_device will not return
> >> >> > > > > > > error,
> >> >> > > > > > > (bus_probe_device doesn't has return value)
> >> >> > > > > > > therefore, the platform layer can't
On Fri, Mar 01, 2013 at 09:45:51AM +0800, Peter Chen wrote:
> On Thu, Feb 28, 2013 at 12:45:59PM +0200, Felipe Balbi wrote:
> > Hi,
> >
> > On Thu, Feb 28, 2013 at 06:06:55PM +0800, Peter Chen wrote:
> >
> > > For runtime pm disabled, we may had to add some ugly things, like
> > > notify core pro
Smatch complains because we only allocate ONETOUCH_PKT_LEN (2) bytes
but later when we call usb_fill_int_urb() we assume maxp can be up
to 8 bytes. I talked to the maintainer and maxp should be capped at
ONETOUCH_PKT_LEN.
Signed-off-by: Dan Carpenter
diff --git a/drivers/usb/storage/onetouch.c
On Thu, Feb 28, 2013 at 10:53:21PM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> USB uses the .find_bridge() callback from struct acpi_bus_type
> incorrectly, because as a result of the way it is used by USB every
> device in the system that doesn't have a bus type or parent is
>
Even in failed case of pm_runtime_get_sync, the usage_count
is incremented. In order to keep the usage_count with correct
value and runtime power management to behave correctly, call
pm_runtime_put(_sync/noidle) in such case.
Signed-off-by Liu Chuansheng
Signed-off-by: Li Fei
---
drivers/usb/co
Even in failed case of pm_runtime_get_sync, the usage_count
is incremented. In order to keep the usage_count with correct
value and runtime power management to behave correctly, call
pm_runtime_put(_sync/noidle) in such case.
Signed-off-by Liu Chuansheng
Signed-off-by: Li Fei
---
drivers/usb/c
> -Original Message-
> From: Rafael J. Wysocki [mailto:r...@sisk.pl]
> Sent: Friday, March 01, 2013 10:22 AM
> To: Liu, Chuansheng
> Cc: Li, Fei; gre...@linuxfoundation.org; Lan, Tianyu;
> st...@rowland.harvard.edu; sarah.a.sh...@linux.intel.com;
> linux-usb@vger.kernel.org; linux-ker...@
On Friday, March 01, 2013 02:07:54 AM Liu, Chuansheng wrote:
>
> > -Original Message-
> > From: Li, Fei
> > Sent: Thursday, February 28, 2013 5:06 PM
> > To: gre...@linuxfoundation.org; Lan, Tianyu; st...@rowland.harvard.edu;
> > sarah.a.sh...@linux.intel.com
> > Cc: r...@sisk.pl; linux-us
On Friday, March 01, 2013 12:59:23 AM Liu, Chuansheng wrote:
>
> > -Original Message-
> > From: Rafael J. Wysocki [mailto:r...@sisk.pl]
> > Sent: Friday, March 01, 2013 8:51 AM
> > To: Liu, Chuansheng
> > Cc: Alan Stern; Li, Fei; gre...@linuxfoundation.org; Lan, Tianyu;
> > sarah.a.sh...@l
> -Original Message-
> From: Li, Fei
> Sent: Thursday, February 28, 2013 5:06 PM
> To: gre...@linuxfoundation.org; Lan, Tianyu; st...@rowland.harvard.edu;
> sarah.a.sh...@linux.intel.com
> Cc: r...@sisk.pl; linux-usb@vger.kernel.org; linux-ker...@vger.kernel.org;
> Liu,
> Chuansheng; Li,
On Thu, Feb 28, 2013 at 12:45:59PM +0200, Felipe Balbi wrote:
> Hi,
>
> On Thu, Feb 28, 2013 at 06:06:55PM +0800, Peter Chen wrote:
>
> > For runtime pm disabled, we may had to add some ugly things, like
> > notify core probe fail, and platform layer needs to handle this failed
> > notify.
>
> P
On Thu, Feb 28, 2013 at 01:16:04PM +0200, Alexander Shishkin wrote:
> Peter Chen writes:
>
> > On Tue, Feb 26, 2013 at 02:47:34PM +0100, Marc Kleine-Budde wrote:
> >> On 02/26/2013 02:25 PM, Alexander Shishkin wrote:
> >> > Marc Kleine-Budde writes:
> >> >
> >> >> On 02/26/2013 11:56 AM, Alexan
> -Original Message-
> From: Rafael J. Wysocki [mailto:r...@sisk.pl]
> Sent: Friday, March 01, 2013 8:51 AM
> To: Liu, Chuansheng
> Cc: Alan Stern; Li, Fei; gre...@linuxfoundation.org; Lan, Tianyu;
> sarah.a.sh...@linux.intel.com; linux-usb@vger.kernel.org;
> linux-ker...@vger.kernel.org
On Friday, March 01, 2013 12:38:07 AM Liu, Chuansheng wrote:
>
> > -Original Message-
> > From: Alan Stern [mailto:st...@rowland.harvard.edu]
> > Sent: Thursday, February 28, 2013 11:17 PM
> > To: Li, Fei
> > Cc: gre...@linuxfoundation.org; Lan, Tianyu; sarah.a.sh...@linux.intel.com;
> > r
> -Original Message-
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Thursday, February 28, 2013 11:17 PM
> To: Li, Fei
> Cc: gre...@linuxfoundation.org; Lan, Tianyu; sarah.a.sh...@linux.intel.com;
> r...@sisk.pl; linux-usb@vger.kernel.org; linux-ker...@vger.kernel.org; Liu,
On Thursday, February 28, 2013 05:13:27 PM Jeff Garzik wrote:
> On 02/28/2013 04:53 PM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > After PCI and USB have stopped using the .find_bridge() callback in
> > struct acpi_bus_type, the only remaining user of it is SATA, but SATA
> > onl
On Thursday, February 28, 2013 02:29:56 PM Yinghai Lu wrote:
> On Thu, Feb 28, 2013 at 1:53 PM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > USB uses the .find_bridge() callback from struct acpi_bus_type
> > incorrectly, because as a result of the way it is used by USB every
> > d
On Thu, Feb 28, 2013 at 1:53 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> USB uses the .find_bridge() callback from struct acpi_bus_type
> incorrectly, because as a result of the way it is used by USB every
> device in the system that doesn't have a bus type or parent is
> passed to
On 02/28/2013 04:53 PM, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki
After PCI and USB have stopped using the .find_bridge() callback in
struct acpi_bus_type, the only remaining user of it is SATA, but SATA
only pretends to be a user, because it points that callback to a stub
always returni
On Wednesday, February 27, 2013 06:33:13 PM Greg Kroah-Hartman wrote:
> On Thu, Feb 28, 2013 at 02:11:58AM +0100, Rafael J. Wysocki wrote:
> > On Wednesday, February 27, 2013 02:20:32 PM Greg Kroah-Hartman wrote:
> > > On Wed, Feb 27, 2013 at 11:06:52PM +0100, Rafael J. Wysocki wrote:
> > > > From:
From: Rafael J. Wysocki
USB uses the .find_bridge() callback from struct acpi_bus_type
incorrectly, because as a result of the way it is used by USB every
device in the system that doesn't have a bus type or parent is
passed to usb_acpi_find_device() for inspection.
What USB actually needs, thou
From: Rafael J. Wysocki
After PCI and USB have stopped using the .find_bridge() callback in
struct acpi_bus_type, the only remaining user of it is SATA, but SATA
only pretends to be a user, because it points that callback to a stub
always returning -ENODEV.
For this reason, drop the SATA's dummy
On Thu, 28 Feb 2013, Adrian Bassett wrote:
> > First, things will be a lot easier if you do your testing with a 3.8
> > kernel rather than 3.7.7.
>
> Ok. using 3.8 checked out from the linux-stable git tree from kernel.org. I
> built three test kernels - 1/ vanilla, 2/ 640c3339 reverted, 3/ no
From: Dave Tubbs
Make sure each c67x00 TD has been executed or retry using the existing
retry mechanism. Reference Cypress Semiconductor BIOS User's Manual 1.2,
page 3-16
Signed-off-by: Dave Tubbs
---
drivers/usb/c67x00/c67x00-sched.c |6 ++
1 files changed, 6 insertions(+), 0 deletion
Hello.
On 02/28/2013 09:39 PM, Dave Tubbs wrote:
From: Dave Tubbs
Make sure each c67x00 TD has been executed or retry using the existing
retry mechanism. Reference Cypress Semiconductor BIOS User's Manual 1.2,
page 3-16
Signed-off-by: Dave Tubbs
---
drivers/usb/c67x00/c67x00-sched.c |6
On 02/28/2013 11:52 AM, Alan Stern wrote:
> On Thu, 28 Feb 2013, Stephen Warren wrote:
>
>> I think this patch might cause unintended consequences.
>>
>> When the Tegra PHY code is converted to a driver (i.e. has its own
>> probe), the initial order of execution of the PHY and EHCI driver probes
>
On Thu, 28 Feb 2013, Stephen Warren wrote:
> I think this patch might cause unintended consequences.
>
> When the Tegra PHY code is converted to a driver (i.e. has its own
> probe), the initial order of execution of the PHY and EHCI driver probes
> will not be guaranteed.
>
> In particular, sinc
From: Dave Tubbs
Make sure each c67x00 TD has been executed or retry using the existing
retry mechanism. Reference Cypress Semiconductor BIOS User's Manual 1.2,
page 3-16
Signed-off-by: Dave Tubbs
---
drivers/usb/c67x00/c67x00-sched.c |6 ++
1 files changed, 6 insertions(+), 0 deletion
> "Dave" == Dave Tubbs writes:
Dave> From: Dave Tubbs
Dave> Make sure each c67x00 TD has been executed or retry using the existing
Dave> retry mechanism. Reference Cypress Semiconductor BIOS User's Manual 1.2,
Dave> page 3-16
Dave> Signed-off-by: Dave Tubbs
Dave> ---
Dave> drivers/
From: Dave Tubbs
Make sure each c67x00 TD has been executed or retry using the existing
retry mechanism. Reference Cypress Semiconductor BIOS User's Manual 1.2,
page 3-16
Signed-off-by: Dave Tubbs
---
drivers/usb/c67x00/c67x00-sched.c |6 ++
1 files changed, 6 insertions(+), 0 deletion
On 02/27/2013 11:36 PM, Venu Byravarasu wrote:
> To clear any configurations made by U-Boot on Tegra USB controller,
> reset it before init in probe.
> diff --git a/drivers/usb/host/ehci-tegra.c b/drivers/usb/host/ehci-tegra.c
> @@ -691,6 +692,10 @@ static int tegra_ehci_probe(struct platform_dev
On 02/28/2013 08:09 AM, Alan Stern wrote:
> On Thu, 28 Feb 2013, Venu Byravarasu wrote:
>
>> To clear any configurations made by U-Boot on Tegra USB controller,
>> reset it before init in probe.
>>
>> Signed-off-by: Venu Byravarasu
>> ---
>> When U-Boot configures a Tegra USB controller in device
On 02/27/2013 07:20 PM, Sarah Sharp wrote:
Basically, I'd like Tony to make his first patch work, rather than
pursuing moving the timer manipulation to xhci_bus_suspend/resume.
Not to add confusion, but here is a less intrusive patch that simply
checks to see if the Compliance Mode Recovery T
On 02/27/2013 10:13 PM, Bjorn Helgaas wrote:
[+cc Andy]
On Wed, Feb 20, 2013 at 11:53 PM, Hannes Reinecke wrote:
On 02/20/2013 05:57 PM, Yinghai Lu wrote:
On Tue, Feb 19, 2013 at 11:58 PM, Hannes Reinecke wrote:
Apparently this device is meant to use MSI _only_ so the BIOS developer
did
Hi Sarah, Tony,
On 2/27/2013 6:20 PM, Sarah Sharp wrote:> On Wed, Feb 27, 2013 at 04:41:45PM
-0500, Alan Stern wrote:
> Well, at this point, I have to say that Alex knows more about the quirk
> than I do. However, my gut feeling is that bus_suspend/resume is not
> the right place to stop the com
On Thu, 28 Feb 2013, Li Fei wrote:
>
> Even in failed case of pm_runtime_get_sync, the usage_count
> is incremented. In order to keep the usage_count with correct
> value and runtime power management to behave correctly, call
> pm_runtime_put(_sync) in such case.
>
> Signed-off-by Liu Chuansheng
On Thu, 28 Feb 2013, Lan Tianyu wrote:
> Hi Alan:
> Further thinking, the device should be disconnected since the port
> can't be resumed and the device will not work normally. Something like
> following. Does this make sense?
> ---
> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hu
On Thu, 28 Feb 2013, Venu Byravarasu wrote:
> To clear any configurations made by U-Boot on Tegra USB controller,
> reset it before init in probe.
>
> Signed-off-by: Venu Byravarasu
> ---
> When U-Boot configures a Tegra USB controller in device mode and if the EHCI
> driver of kernel tries to s
Hi,
On Thu, Jan 31, 2013 at 9:08 PM, Felipe Balbi wrote:
> On Thu, Jan 31, 2013 at 09:00:37PM +0530, Vivek Gautam wrote:
>> Hi Felipe,
>>
>>
>> On Thu, Jan 31, 2013 at 8:55 PM, Felipe Balbi wrote:
>> > Hi,
>> >
>> > On Thu, Jan 31, 2013 at 08:53:27PM +0530, Vivek Gautam wrote:
>> >> >> Moreover,
Hello.
On 28-02-2013 13:59, Peter Korsgaard wrote:
Dave> From: Dave Tubbs
Dave> Make sure each c67x00 TD has been executed or retry using the existing
Dave> retry mechanism. Reference Cypress Semiconductor BIOS User's Manual 1.2,
Dave> page 3-16
Dave> Signed-off-by: Dave Tubbs
On 02/28/2013 12:16 PM, Alexander Shishkin wrote:
> Peter Chen writes:
>
>> On Tue, Feb 26, 2013 at 02:47:34PM +0100, Marc Kleine-Budde wrote:
>>> On 02/26/2013 02:25 PM, Alexander Shishkin wrote:
Marc Kleine-Budde writes:
> On 02/26/2013 11:56 AM, Alexander Shishkin wrote:
>>
Felipe Balbi writes:
> Hi,
>
> On Thu, Feb 28, 2013 at 11:32:09AM +0200, Alexander Shishkin wrote:
>> >> > > > > > > If the probe fails, the ci13xxx_add_device will not return
>> >> > > > > > > error,
>> >> > > > > > > (bus_probe_device doesn't has return value)
>> >> > > > > > > therefore, the
Marc Kleine-Budde writes:
> This patch converts the mxs-phy driver from readl_relaxed(), writel_relaxed()
> to the plain readl(), writel() functions, which are available on all
> platforms.
> This is done to enable compile time testing on non ARM platforms.
>
> Reported-by: Alexander Shishkin
On 2/28/2013 4:18 PM, Felipe Balbi wrote:
+ if (list_empty(&dep->req_queued))
>+ dep->flags &= ~DWC3_EP_BUSY;
not sure this is correct. Whenever req_queue isn't empty, we call
dwc3_stop_active_transfer() which will clear DWC3_EP_BUSY flag.
Yes, if we clear DWC3_EP_BUSY in dwc3
On Thu, Feb 28, 2013 at 10:23:03AM +0100, Marc Kleine-Budde wrote:
> On 02/28/2013 08:57 AM, Felipe Balbi wrote:
> > On Wed, Feb 27, 2013 at 03:16:29PM +0100, Marc Kleine-Budde wrote:
> >> From: Michael Grzeschik
> >>
> >> This adds two little devicetree helper functions for determining the
> >>
Peter Chen writes:
> On Tue, Feb 26, 2013 at 02:47:34PM +0100, Marc Kleine-Budde wrote:
>> On 02/26/2013 02:25 PM, Alexander Shishkin wrote:
>> > Marc Kleine-Budde writes:
>> >
>> >> On 02/26/2013 11:56 AM, Alexander Shishkin wrote:
>> >>> Peter Chen writes:
>> >>>
>> Hi Alex,
>> >>>
>> >
From: Sascha Hauer
Even if a chipidea core is otg capable the board may not. This allows
to explicitly set the core to host/peripheral mode. Without these
flags the driver falls back to the old behaviour.
Signed-off-by: Sascha Hauer
Signed-off-by: Marc Kleine-Budde
---
drivers/usb/chipidea/co
From: Michael Grzeschik
This patch makes it possible to configure the PTW and PTS bits inside
the portsc register for host and device mode before the driver starts
and the phy can be addressed as hardware implementation is designed.
Signed-off-by: Michael Grzeschik
Signed-off-by: Sascha Hauer
From: Michael Grzeschik
This patch removes the limitation of having only one instance of the
ci13xxx-imx platformdata and makes different configurations possible.
Reviewed-by: Peter Chen
Signed-off-by: Michael Grzeschik
Signed-off-by: Sascha Hauer
Signed-off-by: Marc Kleine-Budde
---
driver
From: Sascha Hauer
The dr_mode devicetree property allows to explicitly specify the
host/peripheral/otg mode. This is necessary for boards without proper
ID pin handling.
Reviewed-by: Peter Chen
Signed-off-by: Sascha Hauer
Signed-off-by: Marc Kleine-Budde
---
Documentation/devicetree/binding
From: Sascha Hauer
This patch replaces the hand crafted code to retrieve the phy's phandle from
the DT by the helper function devm_usb_get_phy_by_phandle() which has been
added in commit:
"5d3c28b usb: otg: add device tree support to otg library"
Reviewed-by: Kishon Vijay Abraham I
Reviewe
Hello,
this series depends on the series "[PATCH 0/3] otg-for-v3.10-v2: separate phy
code and add DT helper" (a.k.a. tags/otg-for-v3.10-v2) posted earlier and is
intended for v3.10. The chipidea driver is converted to make use of the DT
helper functions.
No changes since v1, just rebased to otg-f
On 02/28/2013 10:40 AM, Alexander Shishkin wrote:
> Marc Kleine-Budde writes:
>
>> On 02/28/2013 09:01 AM, Felipe Balbi wrote:
>>> hi,
>>>
>>> On Wed, Feb 27, 2013 at 03:16:30PM +0100, Marc Kleine-Budde wrote:
From: Sascha Hauer
We now have usb_add_phy_dev(), so use it to register
Hello,
this series depends on the bugfix patch "USB otg: use try_module_get in all
usb_get_phy functions and add missing module_put" (a.k.a tags/otg-for-v3.9-v1)
posted earlier and is inteded for v3.10. It separates the phy from the otg code
and adds DT helper functions. In mxs-phy the {read,write
From: Sascha Hauer
Most of otg/otg.c is not otg specific, but phy specific, so move it
to the phy directory.
Cc: Felipe Balbi
Reported-by: Kishon Vijay Abraham I
Signed-off-by: Sascha Hauer
Signed-off-by: Marc Kleine-Budde
---
drivers/usb/otg/otg.c| 427
From: Sascha Hauer
We now have usb_add_phy_dev(), so use it to register with the framework
to be able to find the phy from the USB driver.
Reviewed-by: Kishon Vijay Abraham I
Reviewed-by: Peter Chen
Acked-by: Felipe Balbi
Signed-off-by: Sascha Hauer
Signed-off-by: Marc Kleine-Budde
---
dri
This patch converts the mxs-phy driver from readl_relaxed(), writel_relaxed()
to the plain readl(), writel() functions, which are available on all platforms.
This is done to enable compile time testing on non ARM platforms.
Reported-by: Alexander Shishkin
Signed-off-by: Marc Kleine-Budde
---
dr
From: Michael Grzeschik
This adds two little devicetree helper functions for determining the dr_mode
(host, peripheral, otg, dual-role) and phy_type (utmi, ulpi,...) from the
devicetree.
Cc: Felipe Balbi
Signed-off-by: Michael Grzeschik
Signed-off-by: Sascha Hauer
Signed-off-by: Marc Kleine-B
Hi,
On Thu, Feb 28, 2013 at 04:05:31PM +0530, Pratyush Anand wrote:
> To reproduce the issue:
>
> -- Gadget dequeues all submitted requests to the endpoint.
> -- Some of them was not even queued to the dwc3 core.
> -- Such requests will never complete and a transfer completion interrupt
> for the
Hi,
On Thu, Feb 28, 2013 at 06:06:55PM +0800, Peter Chen wrote:
> > >> > > > > > > If the probe fails, the ci13xxx_add_device will not return
> > >> > > > > > > error,
> > >> > > > > > > (bus_probe_device doesn't has return value)
> > >> > > > > > > therefore, the platform layer can't know whethe
Hi,
On Thu, Feb 28, 2013 at 11:32:09AM +0200, Alexander Shishkin wrote:
> >> > > > > > > If the probe fails, the ci13xxx_add_device will not return
> >> > > > > > > error,
> >> > > > > > > (bus_probe_device doesn't has return value)
> >> > > > > > > therefore, the platform layer can't know whethe
AB8500 versions preceding 2.0 were only used internally by ST-Ericsson
and are not supported anymore. This patch drops all v1.0 and v1.1
support code.
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/otg/ab8500-usb.c | 139 ---
1 fil
From: Virupax Sadashivpetimath
Fix dma_controller_create() fail path in case memory resource is
missing.
Acked-by: Linus Walleij
Signed-off-by: Virupax Sadashivpetimath
Signed-off-by: Fabio Baltieri
---
drivers/usb/musb/ux500_dma.c | 12 +++-
1 file changed, 11 insertions(+), 1 dele
Add transceiver notifier event handling to the ux500 driver to set vbus
on specific transceiver events.
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/musb/ux500.c | 41 +
1 file changed, 41 insertions(+)
diff --git a/drivers/usb/m
Update irq handling code to notify all possible link status changes of
AB8500 and AB8505 to the ux500-musb glue driver. The additional event
codes will be used for pm-runtime implementation, and are defined in a
separate ux500-specific header.
This also modify the irq registration code to use dev
Add ux500_musb_set_vbus() implementation for ux500.
This is based on the version originally developed inside ST-Ericsson.
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/musb/ux500.c | 64
1 file changed, 64 insertions(+)
Hello Felipe,
This series is an initial effort to update current UX500 specific
MUSB/OTG drivers with the various improvements and fixes developed
internally by ST-Ericsson since the driver was initially merged.
The driver currently deployed by STE includes many updates such as
runtime PM support
To reproduce the issue:
-- Gadget dequeues all submitted requests to the endpoint.
-- Some of them was not even queued to the dwc3 core.
-- Such requests will never complete and a transfer completion interrupt
for them will never be received.
-- In such situation, we will not be clearing DWC3_EP_B
On Thu, Feb 28, 2013 at 11:32:09AM +0200, Alexander Shishkin wrote:
> Felipe Balbi writes:
>
> > Hi,
> >
> > On Thu, Feb 28, 2013 at 04:31:44PM +0800, Peter Chen wrote:
> >> > > > > > > If the probe fails, the ci13xxx_add_device will not return
> >> > > > > > > error,
> >> > > > > > > (bus_probe
> "Dave" == Dave Tubbs writes:
Dave> From: Dave Tubbs
Dave> Make sure each c67x00 TD has been executed or retry using the existing
Dave> retry mechanism. Reference Cypress Semiconductor BIOS User's Manual 1.2,
Dave> page 3-16
Dave> Signed-off-by: Dave Tubbs
Dave> ---
Dave> drivers/
> "Dave" == Dave Tubbs writes:
Dave> From: Dave Tubbs
Dave> RetryCnt value in c67x00 TD should be 3 (both bits set to 1). Reference
Dave> Cypress Semiconductor BIOS User's Manual 1.2, page 3-14
Acked-by: Peter Korsgaard
Dave> Signed-off-by: Dave Tubbs
Dave> ---
Dave> drivers/usb/c
> "Dave" == Dave Tubbs writes:
Dave> From: Dave Tubbs
Dave> TD data length is 10 bits, correct TD_PORTLENMASK_DL. Reference
Dave> Cypress Semiconductor BIOS User's Manual 1.2, page 3-10
Dave> Signed-off-by: Dave Tubbs
Acked-by: Peter Korsgaard
Dave> ---
Dave> drivers/usb/c67x00/c
Marc Kleine-Budde writes:
> On 02/28/2013 09:01 AM, Felipe Balbi wrote:
>> hi,
>>
>> On Wed, Feb 27, 2013 at 03:16:30PM +0100, Marc Kleine-Budde wrote:
>>> From: Sascha Hauer
>>>
>>> We now have usb_add_phy_dev(), so use it to register with the framework
>>> to be able to find the phy from the
Felipe Balbi writes:
> Hi,
>
> On Thu, Feb 28, 2013 at 04:31:44PM +0800, Peter Chen wrote:
>> > > > > > > If the probe fails, the ci13xxx_add_device will not return error,
>> > > > > > > (bus_probe_device doesn't has return value)
>> > > > > > > therefore, the platform layer can't know whether co
On 02/28/2013 08:57 AM, Felipe Balbi wrote:
> On Wed, Feb 27, 2013 at 03:16:29PM +0100, Marc Kleine-Budde wrote:
>> From: Michael Grzeschik
>>
>> This adds two little devicetree helper functions for determining the dr_mode
>> (host, peripheral, otg, dual-role) and phy_type (utmi, ulpi,...) from th
On 02/28/2013 09:01 AM, Felipe Balbi wrote:
> hi,
>
> On Wed, Feb 27, 2013 at 03:16:30PM +0100, Marc Kleine-Budde wrote:
>> From: Sascha Hauer
>>
>> We now have usb_add_phy_dev(), so use it to register with the framework
>> to be able to find the phy from the USB driver.
>>
>> Reviewed-by: Kishon
Even in failed case of pm_runtime_get_sync, the usage_count
is incremented. In order to keep the usage_count with correct
value and runtime power management to behave correctly, call
pm_runtime_put(_sync) in such case.
Signed-off-by Liu Chuansheng
Signed-off-by: Li Fei
---
drivers/usb/core/hub
> -Original Message-
> From: Lan, Tianyu
> Sent: Thursday, February 28, 2013 4:37 PM
> To: Li, Fei; st...@rowland.harvard.edu
> Cc: gre...@linuxfoundation.org; sarah.a.sh...@linux.intel.com; r...@sisk.pl;
> linux-usb@vger.kernel.org; linux-ker...@vger.kernel.org; Liu, Chuansheng
> Subject:
Hi,
On Thu, Feb 28, 2013 at 04:31:44PM +0800, Peter Chen wrote:
> > > > > > > If the probe fails, the ci13xxx_add_device will not return error,
> > > > > > > (bus_probe_device doesn't has return value)
> > > > > > > therefore, the platform layer can't know whether core's probe
> > > > > > > is suc
On 2013年02月28日 15:57, Li Fei wrote:
>
> Even in failed case of pm_runtime_get_sync, the usage_count
> is incremented. In order to keep the usage_count with correct
> value and runtime power management to behave correctly, call
> pm_runtime_put(_sync) in such case.
Hi Fei:
It's not necessa
On Thu, Feb 28, 2013 at 09:26:17AM +0200, Felipe Balbi wrote:
> Hi,
>
> On Thu, Feb 28, 2013 at 11:11:20AM +0800, Peter Chen wrote:
> > On Wed, Feb 27, 2013 at 02:12:38PM +0200, Felipe Balbi wrote:
> > > Hi,
> > >
> > > On Wed, Feb 27, 2013 at 10:22:03AM +0800, Peter Chen wrote:
> > > > On Tue, F
On Thu, Feb 28, 2013 at 09:29:46AM +0200, Felipe Balbi wrote:
> On Thu, Feb 28, 2013 at 02:06:09PM +0800, Peter Chen wrote:
> > On Wed, Feb 27, 2013 at 09:08:11PM +0200, Alexander Shishkin wrote:
> > >On Feb 27, 2013 8:34 AM, "Peter Chen" wrote:
> > >>
> > >> - For host, the vbus shoul
originally, when deleted the relative code, left some 'another'.
need delete 'another', too.
the relative patches are:
commit 96f8db6a77e3490608e5b5b3f57e7201f8c85496
Author: Felipe Balbi
Date: Mon Oct 10 10:33:47 2011 +0300
usb: gadget: net2272: convert to new style
Converting rndis to the new function interface requires converting
the USB rndis' function code and its users.
This patch converts the f_rndis.c to the new function interface.
The file is now compiled into a separate f_rndis_usb.ko module.
The old function interface is provided by means of a prepro
hi,
On Wed, Feb 27, 2013 at 03:16:30PM +0100, Marc Kleine-Budde wrote:
> From: Sascha Hauer
>
> We now have usb_add_phy_dev(), so use it to register with the framework
> to be able to find the phy from the USB driver.
>
> Reviewed-by: Kishon Vijay Abraham I
> Reviewed-by: Peter Chen
> Acked-b
88 matches
Mail list logo
