Hi,
>>> > It looks like the data is wrong, but I have no way of knowing what the
>>> > data actually should be. Only you know that.
>>> >
>>> >> f31a9740 4037054141 S Bo:2:071:1 -115 31 = 55534243 0c00 0010
>>> >> 8a28 0008 00
>>> >> f31a9740 4037054176 C Bo:
On Tue, Apr 2, 2013 at 4:36 PM, Alan Stern wrote:
> On Tue, 2 Apr 2013, Yegor Yefremov wrote:
>
>> On Tue, Apr 2, 2013 at 4:14 PM, Alan Stern wrote:
>> > On Tue, 2 Apr 2013, Yegor Yefremov wrote:
>> >
>> >> I'm making a burn-in test (see serialtest.py
>> >> http://pastebin.com/pz47gaar) for our d
inside the 'for' looping:
the return value 'rv' may override if not have a check in time.
the next checking (outside the 'for' looping):
can not find failure which generated during the 'for' looping
so need let outside know about the failure.
the original related commit is:
On Wednesday 03 April 2013 15:54:05 Chen Gang wrote:
>
> inside the 'for' looping:
> the return value 'rv' may override if not have a check in time.
>
> the next checking (outside the 'for' looping):
> can not find failure which generated during the 'for' looping
>
> so need let ou
Hi,
On Wed, Apr 03, 2013 at 11:48:39AM +0530, Vivek Gautam wrote:
> >> Adding APIs to handle runtime power management on PHY
> >> devices. PHY consumers may need to wake-up/suspend PHYs
> >> when they work across autosuspend.
> >>
> >> Signed-off-by: Vivek Gautam
> >> ---
> >> include/linux/us
Hi,
On Wed, Apr 03, 2013 at 11:35:43AM +0530, Vivek Gautam wrote:
> >> The current code in the dwc3 probe effectively disables runtime pm
> >> from ever working because it calls a get() that was never put() until
> >> device removal. Change the runtime pm code to match the standard
> >> formula a
On 2013年04月03日 16:12, Oliver Neukum wrote:
> Good catch, but I am afraid the fix is wrong. You cannot stop servicing
> the other ports just because there is an error in another port.
>
> Regards
> Oliver
ok, thanks.
and how about my original fix for it ? (the related patc
Am 01.04.2013 21:12, schrieb Greg KH:
On Mon, Apr 01, 2013 at 11:42:30AM +0200, Karsten Malcher wrote:
Am 01.04.2013 01:10, schrieb Greg KH:
On Sun, Mar 31, 2013 at 07:15:22PM +0200, Karsten Malcher wrote:
Am 31.03.2013 18:58, schrieb Greg KH:
On Sun, Mar 31, 2013 at 06:33:24PM +0200, Karsten
On Wednesday 03 April 2013 16:21:44 Chen Gang wrote:
> On 2013年04月03日 16:12, Oliver Neukum wrote:
> > Good catch, but I am afraid the fix is wrong. You cannot stop servicing
> > the other ports just because there is an error in another port.
> >
> > Regards
> > Oliver
>
> ok, th
Peter Chen writes:
> On Tue, Apr 02, 2013 at 11:31:47AM +0200, Michael Grzeschik wrote:
>> > > dma_pool_destroy(ci->td_pool);
>> > > free_qh_pool:
>> > > -dma_pool_destroy(ci->qh_pool);
>> >
>> > You may need dma_free_coherent.
>>
>> Will add that here.
>>
>
> The same for de
On 2013年04月03日 16:31, Oliver Neukum wrote:
> correct but dirty. A boolean and a comment would be nice.
ok, thanks.
I will send patch v3.
--
Chen Gang
Asianux Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kern
Hello Felipe,
This is the second series of usb updates for Ux500 drivers, covering
almost only ab8500-usb phy.
Patches includes various fixes and errata workarounds, API updates (the
devm_ stuff), and integration with modern subsystems (regulator and
pinctrl).
The whole series has been developed
Converting f_obex to the new function interface requires converting
the f_obex's function code and its users.
This patch converts the f_obex.c to the new function interface.
The file is now compiled into a separate usb_f_obex.ko module.
The old function interface is provided by means of preprocesso
From: Sakethram Bommisetti
Modify ab8500_usb_set_peripheral() and ab8500_usb_set_host() code to
schedule phy_dis_work only when necessary in order to prevent regulator
count mismatch during reboot/shutdown.
Signed-off-by: Sakethram Bommisetti
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltie
Fix last ab->phy.notifier call to use vbus_draw as notifier argument, as
that's used in ab8500_charger to control charging current.
Also drop a related TODO comment, and the additional
ux500_musb_set_vbus(musb, 0), as with this patch it was causing an
erratic behaviour of gadget ep0 state machine.
From: Patrice Chotard
Amend the ab8500-usb driver to optionally take a pin control handle and
set the state of the pins to "default" on ab8500_usb_phy_enable and to
"sleep" on ab8500_usb_phy_disable.
The pinctrl handle is released on ab8500_usb_phy_disable because USB
pins are shared with ab8505
From: Sakethram Bommisetti
ab8500_usb_delayed_work was implemented as a workaroud for the internal
only and now unsupported v1.0 version of AB850. This patch removes the
delayed work and just leave a link status update call at probe time.
Signed-off-by: Sakethram Bommisetti
Acked-by: Linus Wal
Add ab8500_usb_regulator_{enable,disable} functions to control USB phy
regulators on corresponding ab8500_usb_phy_{enable,disable} events.
This contains some workaround and optimization for specific AB8500
versions.
Signed-off-by: Mian Yousaf Kaukab
Signed-off-by: Sakethram Bommisetti
Signed-of
From: Mian Yousaf Kaukab
To prevent clock and regulator frameworks from complaining, only disable
the host or peripheral phy if they were enabled.
Reported-by: Sakethram Bommisetti
Signed-off-by: Mian Yousaf Kaukab
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/ph
Split ab8500_usb_phy_ctrl into separate enable/disable functions to make
the code more linear and readable.
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 55 +++-
1 file changed, 26 insertions(+), 29 deletions(-)
Add initial regulator support to ab8500-usb by introducing necessary
devm_regulator_get().
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 36
1 file changed, 36 insertions(+)
diff --git a/drivers/usb/phy/phy-ab8
From: Sakethram Bommisetti
Set phy tuning values proposed by the hardware teams for AB8500 and
AB8505 to improve USB eye diagram performances.
Signed-off-by: Sakethram Bommisetti
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 87 +
As GPIO information is avail through DT, used it to get Tegra ULPI
reset GPIO number. Added a new member to tegra_usb_phy structure to
store this number.
Signed-off-by: Venu Byravarasu
---
delta from v2: no change.
drivers/usb/phy/phy-tegra-usb.c | 25 +++--
include/linu
Check return values from all GPIO APIs and handle errors accordingly.
Remove clk_disable_unprepare which is no more needed.
Signed-off-by: Venu Byravarasu
---
delta from v2: no change.
drivers/usb/phy/phy-tegra-usb.c | 50 ++
1 files changed, 39 insertions(
From: Sakethram Bommisetti
AB8500 v2.0 has eye diagram issues when drawing more than 100mA from
VBUS. Force charging current to 100mA in case of standard host.
Signed-off-by: Sakethram Bommisetti
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 14
Registered Tegra USB PHY as a separate platform driver.
To synchronize host controller and PHY initialization, used deferred
probe mechanism. As PHY should be initialized before EHCI starts running,
deferred probe of Tegra EHCI driver till PHY probe gets completed.
Got rid of instance number base
In case if clk_get_sys fails, return correct error value provided by
the API.
Signed-off-by: Venu Byravarasu
---
delta from v1: no change.
drivers/usb/phy/phy-tegra-usb.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/phy/phy-tegra-usb.c b/drivers/usb/phy
On Wed, Apr 03, 2013 at 10:45:05AM +0200, Fabio Baltieri wrote:
> From: Sakethram Bommisetti
>
> AB8500 v2.0 has eye diagram issues when drawing more than 100mA from
> VBUS. Force charging current to 100mA in case of standard host.
>
> Signed-off-by: Sakethram Bommisetti
> Acked-by: Linus Wall
Hello Felipe,
On Tuesday, April 02, 2013 4:00 PM Felipe Balbi wrote:
> Hi Andrejz,
>
> On Wed, Jan 23, 2013 at 12:45:31PM +0100, Andrzej Pietrasiewicz wrote:
> > The prerequisite for providing the configfs interface for mass storage
> > and all its users is converting them to the new function i
Kernel 3.9-rc5 has trouble with USB [under 3.9-rc4 is ok]. System [Kubuntu
12.10] does not mount properly the USB drives ... or more precisely can be
mounted, but for example, KDE does not show information about the new drive ...
and you will not see errors in dmesg.
When I start the system o
This patch updates all Tegra board files so that they contain all the
properties required by the updated USB DT binding. Note that this patch
only adds the new properties and does not yet remove the old properties,
in order to maintain bisectability. The old properties will be removed
once the driv
Drop references to deprecated U5500 platform in driver comments.
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/musb/ux500_dma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/musb/ux500_dma.c b/drivers/usb/musb/ux500_dma.c
index f417b7e..
delta from v1:
This patch is prepared as follow up patch of TEGRA USB PHY driver
patch series being discussed at:
http://marc.info/?l=linux-tegra&m=136361016003625&w=2
Venu Byravarasu (7):
ARM: tegra: finalize USB EHCI and PHY bindings
ARM: tegra: update device trees for USB binding rework
Convert local data allocation to devm_kzalloc and drop unnecessary fail
path code.
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 19 +--
1 file changed, 5 insertions(+), 14 deletions(-)
diff --git a/drivers/usb/phy/phy-ab8500-usb.c
Added a new PHY mode to support OTG.
Obtained Tegra USB PHY mode using DT property.
Signed-off-by: Venu Byravarasu
---
delta from v1:
replaced gadget with peripheral.
drivers/usb/host/ehci-tegra.c |3 +--
drivers/usb/phy/phy-tegra-usb.c | 13 +++--
include/linux/usb/tegra_us
The existing Tegra USB bindings have a few issues:
1) Many properties are documented as being part of the EHCI controller
node, yet they apply more to the PHY device. They should be moved.
2) Some registers in PHY1 are shared with PHY3, and hence PHY3 needs a
reg entry to point at PHY1's register
On Wed, Apr 03, 2013 at 11:53:36AM +0300, Felipe Balbi wrote:
> On Wed, Apr 03, 2013 at 10:45:05AM +0200, Fabio Baltieri wrote:
> > From: Sakethram Bommisetti
> >
> > AB8500 v2.0 has eye diagram issues when drawing more than 100mA from
> > VBUS. Force charging current to 100mA in case of standar
Hi Felipe,
On Wed, Apr 03, 2013 at 11:58:58AM +0300, Felipe Balbi wrote:
> On Wed, Apr 03, 2013 at 11:53:36AM +0300, Felipe Balbi wrote:
> > On Wed, Apr 03, 2013 at 10:45:05AM +0200, Fabio Baltieri wrote:
> > > From: Sakethram Bommisetti
> > >
> > > AB8500 v2.0 has eye diagram issues when drawin
inside the 'for' looping:
the return value 'rv' may override if not have a check in time.
the next checking (outside the 'for' looping):
can not find failure which generated during the 'for' looping
the fix is for:
let outside know about the failure, and not stop servicing the
On Wed, Apr 03, 2013 at 11:12:00AM +0200, Fabio Baltieri wrote:
> Hi Felipe,
>
> On Wed, Apr 03, 2013 at 11:58:58AM +0300, Felipe Balbi wrote:
> > On Wed, Apr 03, 2013 at 11:53:36AM +0300, Felipe Balbi wrote:
> > > On Wed, Apr 03, 2013 at 10:45:05AM +0200, Fabio Baltieri wrote:
> > > > From: Saket
Hi folks,
my 'next' brach is now closed for v3.10. This is a giant effort. By
*far* the biggest pull request that has ever passed through myself.
Below you can find diffstat and shortlog for my next branch. Note that
the few arch/arm/ and Documentation patches are related work which had
to be don
Hi,
On Wed, Apr 03, 2013 at 10:54:24AM +0200, Andrzej Pietrasiewicz wrote:
> > > The prerequisite for providing the configfs interface for mass storage
> > > and all its users is converting them to the new function interface from
> > Sebastian.
> > >
> > > This patch series serves the purpose stat
Hi,
On Thu, Mar 28, 2013 at 11:37:32AM +0100, Andrzej Pietrasiewicz wrote:
> In order to convert to configfs the USB functions need to be converted
> to the new interface from Sebastian, which also requires turning them
> into separate modules. Some of these modules will consist of just
> one obje
Hi,
On Sun, Mar 17, 2013 at 05:59:00PM +0100, Sebastian Andrzej Siewior wrote:
> >diff --git a/drivers/usb/gadget/udc-core.c b/drivers/usb/gadget/udc-core.c
> >index 40b1d88..8a1eeb2 100644
> >--- a/drivers/usb/gadget/udc-core.c
> >+++ b/drivers/usb/gadget/udc-core.c
> >@@ -197,6 +207,8 @@ int usb
On Wed, Apr 3, 2013 at 9:12 AM, Yegor Yefremov
wrote:
> On Tue, Apr 2, 2013 at 4:36 PM, Alan Stern wrote:
>> On Tue, 2 Apr 2013, Yegor Yefremov wrote:
>>
>>> On Tue, Apr 2, 2013 at 4:14 PM, Alan Stern
>>> wrote:
>>> > On Tue, 2 Apr 2013, Yegor Yefremov wrote:
>>> >
>>> >> I'm making a burn-in t
Commit 756aa6b3d536afe85e151138cb03a293998887b3 (ehci-hub: improved
over-current recovery) added port power cycling on overcurrent indications as
needed by the MPC8349 USB controller after resolving of the overcurrent
situation in order to have the host state machine assert the correct port
status
To clear any configurations made by U-Boot on Tegra USB controller,
reset it before init in probe.
Signed-off-by: Venu Byravarasu
Acked-by: Alan Stern
Acked-by: Greg Kroah-Hartman
reviewed-by: Stephen Warren
---
This patch was already reviewed at:
http://marc.info/?l=linux-usb&m=136203353205
> -Original Message-
> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
> Sent: Tuesday, April 02, 2013 9:02 PM
> To: Venu Byravarasu
> Cc: gre...@linuxfoundation.org; st...@rowland.harvard.edu; linux-
> u...@vger.kernel.org; linux-ker...@vger.kernel.org
> Subject: Re: [PATCH] usb: host:
Hi,
On Wednesday, April 03, 2013 12:01 PM Felipe Balbi wrote:
> >
> > I think it is more acceptable to provide a small but more-or-less
> > complete solution and I intend to do further works in a manner
> > demonstrated in the above mentioned thread.
>
> alright, but do we still have the old mod
Hi Felipe,
On Thu, Mar 28, 2013 at 11:52:38AM +0100, Michael Grzeschik wrote:
> Hi,
>
> this series solves some memroy issues with the chipidea udc
>
> The series is based on v3.9-rc4.
>
> Thanks,
> Michael
>
> Michael Grzeschik (2):
> usb: chipidea: udc: fix memory access of shared memory o
Hi,
On Wednesday, April 03, 2013 12:03 PM Felipe Balbi wrote:
> On Thu, Mar 28, 2013 at 11:37:32AM +0100, Andrzej Pietrasiewicz wrote:
> > In order to convert to configfs the USB functions need to be converted
> > to the new interface from Sebastian, which also requires turning them
> > into se
Hi,
On Wed, Apr 03, 2013 at 12:57:49PM +0200, Andrzej Pietrasiewicz wrote:
> > > I think it is more acceptable to provide a small but more-or-less
> > > complete solution and I intend to do further works in a manner
> > > demonstrated in the above mentioned thread.
> >
> > alright, but do we stil
On Wed, Apr 03, 2013 at 02:12:27PM +0300, Felipe Balbi wrote:
> Hi,
>
> On Wed, Apr 03, 2013 at 12:57:49PM +0200, Andrzej Pietrasiewicz wrote:
> > > > I think it is more acceptable to provide a small but more-or-less
> > > > complete solution and I intend to do further works in a manner
> > > > de
On Wed, Apr 03, 2013 at 02:16:03PM +0300, Felipe Balbi wrote:
> On Wed, Apr 03, 2013 at 02:12:27PM +0300, Felipe Balbi wrote:
> > Hi,
> >
> > On Wed, Apr 03, 2013 at 12:57:49PM +0200, Andrzej Pietrasiewicz wrote:
> > > > > I think it is more acceptable to provide a small but more-or-less
> > > > >
Hi,
On Wed, Apr 03, 2013 at 02:27:49PM +0300, Felipe Balbi wrote:
> > > > > > I think it is more acceptable to provide a small but more-or-less
> > > > > > complete solution and I intend to do further works in a manner
> > > > > > demonstrated in the above mentioned thread.
> > > > >
> > > > > al
Hi,
On Wed, Apr 03, 2013 at 02:39:19PM +0300, Felipe Balbi wrote:
> > > > > > > I think it is more acceptable to provide a small but more-or-less
> > > > > > > complete solution and I intend to do further works in a manner
> > > > > > > demonstrated in the above mentioned thread.
> > > > > >
> >
Hi,
On Wednesday, April 03, 2013 1:39 PM Felipe Balbi wrote:
> >
> > Sebastian's email address was also broken, I fixed it all up now. Will
> > run a few tests.
>
> There is one patch which you didn't add your SoB, should I add it ?
>
> commit 0d24ccd4e2bc70662537742d82e0bd1ab012123c
> Author
Hi,
On Wed, Apr 03, 2013 at 01:48:03PM +0200, Andrzej Pietrasiewicz wrote:
> Hi,
>
> On Wednesday, April 03, 2013 1:39 PM Felipe Balbi wrote:
>
>
>
> > >
> > > Sebastian's email address was also broken, I fixed it all up now. Will
> > > run a few tests.
> >
> > There is one patch which you di
Le 04/02/13 20:19, ba...@ti.com a écrit :
Hi,
On Tue, Apr 02, 2013 at 07:10:22PM +0200, Florian Fainelli wrote:
diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
index 05e5143..ab5a3b9 100644
--- a/drivers/usb/musb/Kconfig
+++ b/drivers/usb/musb/Kconfig
@@ -6,7 +6,6 @@
# (M)HDR
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Thierry Reding
> Sent: Wednesday, April 03, 2013 2:11 AM
> To: Felipe Balbi
> Cc: Stephen Warren; Alan Stern; linux-te...@vger.kernel.org; linux-
> u...@vger.kernel.org
> Su
On 19.03.2013 14:27, Peter Korsgaard wrote:
>> "Daniel" == Daniel Mack writes:
>
> Hi,
>
> >> I know this patch reintroduces bits that have been intentionally
> >> removed before, in particular by 032ec49f53 ("usb: musb: drop
> >> useless board_mode usage"), but I don't know how this usb
Hi,
(sorry, being really busy lately)
On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
> > >> I know this patch reintroduces bits that have been intentionally
> > >> removed before, in particular by 032ec49f53 ("usb: musb: drop
> > >> useless board_mode usage"), but I don't know ho
Hi,
On Wednesday, April 03, 2013 1:50 PM Felipe Balbi wrote:
> > > >
> > > > Sebastian's email address was also broken, I fixed it all up now.
> > > > Will run a few tests.
> > >
> > > There is one patch which you didn't add your SoB, should I add it ?
> > >
> > > commit 0d24ccd4e2bc70662537742d
Hi Felipe,
On 03.04.2013 14:04, Felipe Balbi wrote:
> (sorry, being really busy lately)
>
> On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
>>> >> I know this patch reintroduces bits that have been intentionally
>>> >> removed before, in particular by 032ec49f53 ("usb: musb: drop
>
Le 04/02/13 20:06, Alan Stern a écrit :
On Tue, 2 Apr 2013, Florian Fainelli wrote:
This patch removes the depends on USB from all config symbols in
drivers/usb/host/Kconfig and replace that with an if USB / endif block
as suggested by Alan Stern. Some source ... Kconfig lines have been
shuffle
On Wed, Apr 03, 2013 at 02:11:13PM +0200, Florian Fainelli wrote:
> Le 04/02/13 20:06, Alan Stern a écrit :
> >On Tue, 2 Apr 2013, Florian Fainelli wrote:
> >
> >>This patch removes the depends on USB from all config symbols in
> >>drivers/usb/host/Kconfig and replace that with an if USB / endif bl
Le 04/03/13 14:15, Felipe Balbi a écrit :
On Wed, Apr 03, 2013 at 02:11:13PM +0200, Florian Fainelli wrote:
Le 04/02/13 20:06, Alan Stern a écrit :
On Tue, 2 Apr 2013, Florian Fainelli wrote:
This patch removes the depends on USB from all config symbols in
drivers/usb/host/Kconfig and replace
On Wed, Apr 03, 2013 at 02:18:20PM +0200, Florian Fainelli wrote:
> Le 04/03/13 14:15, Felipe Balbi a écrit :
> >On Wed, Apr 03, 2013 at 02:11:13PM +0200, Florian Fainelli wrote:
> >>Le 04/02/13 20:06, Alan Stern a écrit :
> >>>On Tue, 2 Apr 2013, Florian Fainelli wrote:
> >>>
> This patch remo
On 03.04.2013 14:04, Felipe Balbi wrote:
> On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
>> Felipe, could you explain the background on how the dsps driver is
>> supposed to work in host mode at boot time with the rework of the driver
>> you did for 3.7? It might just be me not unde
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or without using phandle. To obtain a reference to the PHY
without using phandle, the platform specfic intialization code (say from
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. To obtain a reference to the PHY without
using phandle, the platform specfic intialization code (say from board file)
shoul
In order for controllers to get PHY in case of non dt boot, the phy
binding information should be added in the platform specific
initialization code using phy_bind.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/mach-omap2/usb-musb.c |7 ++-
1 file changed, 6 insertions(+), 1 deletio
Use the generic PHY framework API to get the PHY. The usb_phy_set_suspend
and usb_phy_set_resume is replaced with phy_suspend and phy_resume to
align with the new PHY framework.
musb->xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a separate state
Used the generic PHY framework API to create the PHY. twl4030_usb_suspend
and twl4030_usb_resume is added to phy_ops in order to align
with the new framework.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined with PHY and moving to the new
framework comp
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding information can be found at
Documentation/devicetree/bindings/phy/phy-bindings
Used the generic PHY framework API to create the PHY. omap_usb2_suspend
is split into omap_usb_suspend and omap_usb_resume in order to align
with the new framework.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined with PHY and moving to the new framewor
Hi,
On Wed, Apr 03, 2013 at 02:43:00PM +0200, Daniel Mack wrote:
> On 03.04.2013 14:04, Felipe Balbi wrote:
> > On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
>
> >> Felipe, could you explain the background on how the dsps driver is
> >> supposed to work in host mode at boot time wi
Op 3 apr. 2013, om 15:09 heeft Felipe Balbi het volgende
geschreven:
> Hi,
>
> On Wed, Apr 03, 2013 at 02:43:00PM +0200, Daniel Mack wrote:
>> On 03.04.2013 14:04, Felipe Balbi wrote:
>>> On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
>>
Felipe, could you explain the backgr
Hi Felipe,
On Wed, Apr 3, 2013 at 1:45 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Apr 03, 2013 at 11:48:39AM +0530, Vivek Gautam wrote:
>> >> Adding APIs to handle runtime power management on PHY
>> >> devices. PHY consumers may need to wake-up/suspend PHYs
>> >> when they work across autosuspen
On 03.04.2013 15:12, Koen Kooi wrote:
>
> Op 3 apr. 2013, om 15:09 heeft Felipe Balbi het
> volgende geschreven:
>
>> Hi,
>>
>> On Wed, Apr 03, 2013 at 02:43:00PM +0200, Daniel Mack wrote:
>>> On 03.04.2013 14:04, Felipe Balbi wrote:
On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wr
Hi Jan, all,
Did you manage to find a fix for the problem. Could you please share it.
Thanks in Advance
Arshad
--
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-i
On Wed, Apr 03, 2013 at 06:23:49PM +0530, Kishon Vijay Abraham I wrote:
> The PHY framework provides a set of APIs for the PHY drivers to
> create/destroy a PHY and APIs for the PHY users to obtain a reference to the
> PHY with or without using phandle. To obtain a reference to the PHY without
> us
Hi,
On Wed, Apr 03, 2013 at 03:12:11PM +0200, Koen Kooi wrote:
> > On Wed, Apr 03, 2013 at 02:43:00PM +0200, Daniel Mack wrote:
> >> On 03.04.2013 14:04, Felipe Balbi wrote:
> >>> On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
> >>
> Felipe, could you explain the background on
Hi,
On Wed, Apr 03, 2013 at 03:16:05PM +0200, Daniel Mack wrote:
> On 03.04.2013 15:12, Koen Kooi wrote:
> >
> > Op 3 apr. 2013, om 15:09 heeft Felipe Balbi het
> > volgende geschreven:
> >
> >> Hi,
> >>
> >> On Wed, Apr 03, 2013 at 02:43:00PM +0200, Daniel Mack wrote:
> >>> On 03.04.2013 14:0
On Wed, Apr 03, 2013 at 06:23:50PM +0530, Kishon Vijay Abraham I wrote:
> Used the generic PHY framework API to create the PHY. omap_usb2_suspend
> is split into omap_usb_suspend and omap_usb_resume in order to align
> with the new framework.
>
> However using the old USB PHY library cannot be com
HI,
On Wed, Apr 03, 2013 at 06:42:48PM +0530, Vivek Gautam wrote:
> >> >> Adding APIs to handle runtime power management on PHY
> >> >> devices. PHY consumers may need to wake-up/suspend PHYs
> >> >> when they work across autosuspend.
> >> >>
> >> >> Signed-off-by: Vivek Gautam
> >> >> ---
> >>
Hi,
On Wed, Apr 03, 2013 at 04:54:14PM +0300, Felipe Balbi wrote:
> > >> >> +static inline void usb_phy_autopm_enable(struct usb_phy *x)
> > >> >> +{
> > >> >> + if (!x || !x->dev) {
> > >> >> + dev_err(x->dev, "no PHY or attached device
> > >> >> available\n");
> > >> >> +
Since regulator_enable() is going to be marked as __must_check in the
next merge window, always check regulator_enable() return value and
print a warning if it fails.
Cc: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 12 +---
1 file changed, 9 insert
Since regulator_enable() is going to be marked as __must_check in the
next merge window, always check regulator_enable() return value and
print a warning if it fails.
Cc: Kalle Jokiniemi
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-twl4030-usb.c | 18 +++---
1 file changed,
Since regulator_enable() is going to be marked as __must_check in the
next merge window, always check regulator_enable() return value and
print a warning if it fails.
Cc: Hema HK
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-twl6030-usb.c | 11 +--
1 file changed, 9 insertions(+
Hello Felipe,
While testing your 'next' branch merged with today's next I got some new
warnings, caused by a recently introduced __must_check in:
c8801a8 regulator: core: Mark all get and enable calls as __must_check
These patches introduces a check for regulator_enable() return value in
all thr
Hi,
On Wed, Apr 03, 2013 at 04:02:24PM +0200, Fabio Baltieri wrote:
> While testing your 'next' branch merged with today's next I got some new
> warnings, caused by a recently introduced __must_check in:
>
> c8801a8 regulator: core: Mark all get and enable calls as __must_check
>
> These patches
On Wed, Apr 03, 2013 at 10:46:46AM +0200, Tomasz Miś wrote:
> Kernel 3.9-rc5 has trouble with USB [under 3.9-rc4 is ok]. System
> [Kubuntu 12.10] does not mount properly the USB drives ... or more
> precisely can be mounted, but for example, KDE does not show
> information about the new drive ... a
Michael Grzeschik writes:
> Hi Felipe,
>
> On Thu, Mar 28, 2013 at 11:52:38AM +0100, Michael Grzeschik wrote:
>> Hi,
>>
>> this series solves some memroy issues with the chipidea udc
>>
>> The series is based on v3.9-rc4.
>>
>> Thanks,
>> Michael
>>
>> Michael Grzeschik (2):
>> usb: chipide
Hi,
On Wed, Apr 3, 2013 at 7:26 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Apr 03, 2013 at 04:54:14PM +0300, Felipe Balbi wrote:
>> > >> >> +static inline void usb_phy_autopm_enable(struct usb_phy *x)
>> > >> >> +{
>> > >> >> + if (!x || !x->dev) {
>> > >> >> + dev_err(x->dev,
Hi Felipe,
On Wed, Apr 03, 2013 at 05:06:22PM +0300, Felipe Balbi wrote:
> Hi,
>
> On Wed, Apr 03, 2013 at 04:02:24PM +0200, Fabio Baltieri wrote:
> > While testing your 'next' branch merged with today's next I got some new
> > warnings, caused by a recently introduced __must_check in:
> >
> > c
Hi Arshad,
> Did you manage to find a fix for the problem. Could you please share it.
What driver does the USB controller in your TI board use?
This problem sounds familiar to a problem I have observed in an Ralink
RT3052 board, which uses the dwc_otg / dwc2 driver. Here, the problem
was that the
Hi,
On Wed, Apr 03, 2013 at 07:40:44PM +0530, Vivek Gautam wrote:
> >> > >> >> +static inline void usb_phy_autopm_enable(struct usb_phy *x)
> >> > >> >> +{
> >> > >> >> + if (!x || !x->dev) {
> >> > >> >> + dev_err(x->dev, "no PHY or attached device
> >> > >> >> available\n");
Hi,
On Wednesday 03 April 2013 07:12 PM, Felipe Balbi wrote:
On Wed, Apr 03, 2013 at 06:23:49PM +0530, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without u
On Wed, Apr 03, 2013 at 05:10:48PM +0300, Alexander Shishkin wrote:
> Michael Grzeschik writes:
>
> > Hi Felipe,
> >
> > On Thu, Mar 28, 2013 at 11:52:38AM +0100, Michael Grzeschik wrote:
> >> Hi,
> >>
> >> this series solves some memroy issues with the chipidea udc
> >>
> >> The series is base
1 - 100 of 158 matches
Mail list logo
