Hi Kukjin,
On Fri, Mar 15, 2013 at 1:32 PM, Vivek Gautam wrote:
> This patch-set is in continuation with patch-series:
> [PATCH v4 0/4] Enable ehci, ohci and dwc3 devices on exynos5250
> out of which follwowing patches have been picked up:
> ARM: Exynos5250: Enabling ehci-s5p driver
> ARM: Exyno
Hi Kukjin,
On Fri, Mar 15, 2013 at 1:26 PM, Vivek Gautam wrote:
> Based on 'for-next' of linux-samsung tree with following patches
> from Doug on top:
> usb: Document clocks in samsung, exynos4210-ehci/ohci bindings
> ARM: dts: add usb 2.0 clock references to exynos5250 device tree
>
> Also depe
"len" comes from the USB transfer and it's probably correct. The thing
is that we already have similar checks like:
if (data[i] >= serial->num_ports) {
So adding a sanity test here matches the rest of the code and is a good
idea.
Signed-off-by: Dan Carpenter
diff --git a/drivers/usb/s
We can remove the "if (urb->actual_length) {" check because checking for
"while (i < urb->actual_length) {" is sufficient. This lets us pull the
code in one indent level.
Signed-off-by: Dan Carpenter
diff --git a/drivers/usb/serial/keyspan.c b/drivers/usb/serial/keyspan.c
index 5b912fc..c773ac7
Hi Tony,
On Thursday 04 April 2013 05:12 AM, Tony Lindgren wrote:
> Hi,
>
[]..
>> @@ -1663,6 +1664,40 @@ static struct omap_clk omap44xx_clks[] = {
>> CLK(NULL, "cpufreq_ck", &dpll_mpu_ck, CK_443X),
>> };
>>
>> +static struct clk *scrm_clks[] = {
>> +&auxclk0_ck,
>> +&a
Felipe
>
> 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
Hi Sarah,
On Wed, Apr 3, 2013 at 10:57 PM, Sarah Sharp
wrote:
> Question: Do you still need this patch for 3.10?
Felipe's 'next' is closed for 3.10, so this series won't be making it
to 3.10 now, as a whole. :-(
>
> http://marc.info/?l=linux-usb&m=136057666911621&w=2
>
> Does this patchset bui
Hello,
I want to test USB keyboard for XHCI in u-boot and to do that i need the
Interrupt transfer code in XHCI controller driver in u-boot. If
possible, can you help me to give that piece of code or can you help me
to figure out in kernel where can i find it so that i can try to
replicate it in u
Hi,
>>> > the parameter is file=/dev/mmcblk0p1
>>
>> Perhaps you have already realized this... mmcblk0p1 is the first
>> partition of the mmcblk0 device. Block 0 of the partition is the boot
>> sector, not the MBR. The MBR is block 0 of the mmcblk0 device. So
>> perhaps you really meant to use
Hi,
>> > the parameter is file=/dev/mmcblk0p1
>
> Perhaps you have already realized this... mmcblk0p1 is the first
> partition of the mmcblk0 device. Block 0 of the partition is the boot
> sector, not the MBR. The MBR is block 0 of the mmcblk0 device. So
> perhaps you really meant to use:
>
>
On 04/03/2013 06:53 AM, 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
> using phandle, the p
Hi,
* Roger Quadros [130319 07:31]:
> Register a device tree clock provider for AUX clocks
> on the OMAP4 SoC. Also provide the binding information.
>
> Signed-off-by: Roger Quadros
> ---
> .../devicetree/bindings/clock/omap4-clock.txt | 32 ++
> arch/arm/boot/dts/omap4.
On 04/03/2013 06:53 AM, Kishon Vijay Abraham I wrote:
> 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 usi
It is possible that we fail on xhci_mem_init, just before doing
the INIT_LIST_HEAD, and calling xhci_mem_cleanup.
Problem is that, the list_for_each_entry_safe macro, dereferences next
assuming is not NULL (which is the case for a uninitialized list).
Let's protect from that.
Signed-off-by: Serg
Support host and device usb modes for the chipidea controller in AR933x.
The controller doesn't support OTG functionality so the platform code
forces one of the modes based on the state of GPIO13 pin at startup.
Signed-off-by: Svetoslav Neykov
---
arch/mips/ath79/dev-usb.c |
Add support for the usb controller in AR933x platform.
The controller supports both host or device mode (defined at startup)
but not OTG.
The patches are tested on WR703n router running OpenWRT in device mode.
Changes since v2:
Removed the glue driver, now dev-usb.c directly registers ci_hdrc.
C
On 04/03/2013 02:53 PM, Kishon Vijay Abraham I wrote:
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/phy-bindings.txt
@@ -0,0 +1,67 @@
+This document explains only the dt data binding. For general information about
s/dt data/device tree ?
+PHY subsystem refer Documentation/phy.txt
The cleanup path checks whether the transceiver was properly initialized
using IS_ERR(). However it can also happen that the cleanup path is run
before the transceiver was initialized (or the operating mode isn't set
to TEGRA_USB_OTG) and is therefore NULL. Add a separate label for error
unwinding
On 03/19/2013 01:51 PM, Stephen Warren wrote:
> On 03/18/2013 06:29 AM, Venu Byravarasu wrote:
>> As part of this series, apart from patch containing changes to register TEGRA
>> USB PHY driver as platform driver, prepared below patches:
>> 1. Re-arranging & adding new DT properties.
>> 2. Getting
On 03/19/2013 01:53 PM, Stephen Warren wrote:
> On 03/18/2013 06:29 AM, Venu Byravarasu wrote:
>> 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
On 04/03/2013 02:41 AM, Venu Byravarasu wrote:
> Check return values from all GPIO APIs and handle errors accordingly.
> Remove clk_disable_unprepare which is no more needed.
checkpatch fails:
> WARNING: line over 80 characters
> #27: FILE: drivers/usb/phy/phy-tegra-usb.c:547:
> + dev
On 03/19/2013 02:10 PM, Stephen Warren wrote:
> On 03/18/2013 06:29 AM, Venu Byravarasu wrote:
>> Check return values from all GPIO APIs and handle errors accordingly.
>
>> Remove clk_disable_unprepare which is no more needed.
>
> The call to clk_disable_unprepare is incorrect in the current code
On Wed, Apr 03, 2013 at 09:02:50PM +0200, Tomasz Miś wrote:
> Dnia Środa, 3 Kwietnia 2013 20:26 Greg KH napisał(a)
> >
> > A: No.
> > Q: Should I include quotations after my reply?
> >
> > http://daringfireball.net/2007/07/on_top
> >
> > On Wed, Apr 03, 2013 at 08:16:47PM +0200, Tomasz Miś
On 04/03/2013 02:41 AM, Venu Byravarasu wrote:
> 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 bisectab
Hi,
The 2nd release candidate for libusbx v1.0.15 is now available at
http://sourceforge.net/projects/libusbx/files/releases/1.0.15/source/
This version brings the following improvements:
* Improve tranfer cancellation and avoid short read failures on broken
descriptors
* Filter out 8-bit ch
On 04/03/2013 02:41 AM, Venu Byravarasu wrote:
> 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 bisectab
On 04/03/2013 02:41 AM, Venu Byravarasu wrote:
> The existing Tegra USB bindings have a few issues:
...
> This patch fixes the binding definition to resolve these issues.
> diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt
> b/Documentation/devicetree/bindings/usb/nvid
Dnia Środa, 3 Kwietnia 2013 20:26 Greg KH napisał(a)
>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
>
> On Wed, Apr 03, 2013 at 08:16:47PM +0200, Tomasz Miś wrote:
> > Welcome. Yes You're right. However, I reported that at this point
On 03/20/2013 05:45 PM, Christopher Waid wrote:
On 03/20/2013 02:57 PM, Gustavo Padovan wrote:
* Christopher Waid [2013-03-20 14:13:14 -0400]:
On 03/18/2013 03:13 PM, Greg KH wrote:
On Mon, Mar 18, 2013 at 02:57:43PM -0400, Christopher Waid wrote:
Bus 001 Device 007: ID 0a12:0001 Cambridge
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
On Tue, Apr 02, 2013 at 10:40:50PM +0200, Thierry Reding wrote:
> The cleanup path checks whether the transceiver was properly initialized
> using IS_ERR(). However it can also happen that the cleanup path is run
> before the transceiver was initialized (or the operating mode isn't set
> to TEGRA_U
On Wed, Apr 03, 2013 at 02:09:23PM -0400, Alan Stern wrote:
> On Wed, 3 Apr 2013, Christian Engelmayer wrote:
>
> > Commit 756aa6b3d536afe85e151138cb03a293998887b3 (ehci-hub: improved
> > over-current recovery) added port power cycling on overcurrent indications
> > as
> > needed by the MPC8349 U
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Apr 03, 2013 at 08:16:47PM +0200, Tomasz Miś wrote:
> Welcome. Yes You're right. However, I reported that at this point,
> because of the effects it causes. You can not see absolutely no
> nega
On Wed, 3 Apr 2013, Felipe Balbi wrote:
> 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/drive
Welcome. Yes You're right. However, I reported that at this point, because of
the effects it causes. You can not see absolutely no negative side effects of
network solutions. However, there are "effects" about which I wrote on the USB
drive.
Established "symptoms" appear both in my kernels [pur
On Wed, 3 Apr 2013, Felipe Balbi wrote:
> > Lets suppose DWC3 enables runtime_pm on USB 2 type phy,
> > it will try to go into suspend state and thereby call runtime_suspend(), if
> > any.
> > And PHY will come to active state only when its consumer wakes it up,
> > and this consumer is operation
On Wed, Apr 03, 2013 at 09:03:18PM +0300, Felipe Balbi wrote:
> recent changes to gadget framework have
> exposed a flaw in nokia.c where it uses
> f_ecm.c but it wasn't including it like
> other gadget drivers.
>
> This is a temporary patch until all other
> function drivers are converted to new
On Wed, 3 Apr 2013, Felipe Balbi wrote:
> 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,
On Wed, 3 Apr 2013, Christian Engelmayer wrote:
> 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 ha
recent changes to gadget framework have
exposed a flaw in nokia.c where it uses
f_ecm.c but it wasn't including it like
other gadget drivers.
This is a temporary patch until all other
function drivers are converted to new API
where each function driver becomes a module
and binding is done through
On Wed, 3 Apr 2013, victor yeo wrote:
> > the parameter is file=/dev/mmcblk0p1
Perhaps you have already realized this... mmcblk0p1 is the first
partition of the mmcblk0 device. Block 0 of the partition is the boot
sector, not the MBR. The MBR is block 0 of the mmcblk0 device. So
perhaps yo
On 04/03/2013 01:23 PM, Sarah Sharp wrote:
Hmm, actually, this patch doesn't apply any more. Sorry for not getting
to it sooner. Can you resend this against Greg's latest usb-next
branch?
Sarah Sharp
Yes, will do.
On Wed, Apr 03, 2013 at 10:21:56AM -0700, Sarah Sharp wrote:
Hi Tony,
Jus
Question: Do you still need this patch for 3.10?
http://marc.info/?l=linux-usb&m=136057666911621&w=2
Does this patchset build on top of that?
I'm really behind on my patches for 3.10, sorry.
Sarah Sharp
On Mon, Apr 01, 2013 at 07:23:59PM +0530, Vivek Gautam wrote:
> This patch-series enables r
Hmm, actually, this patch doesn't apply any more. Sorry for not getting
to it sooner. Can you resend this against Greg's latest usb-next
branch?
Sarah Sharp
On Wed, Apr 03, 2013 at 10:21:56AM -0700, Sarah Sharp wrote:
> Hi Tony,
>
> Just a note that I'm queuing this patch to Greg for 3.10. I'
Hi Tony,
Just a note that I'm queuing this patch to Greg for 3.10. I'm working
on a bug fix patch for 3.9 that includes turning off runtime PM, and
should fix the issue with the compliance timer causing list corruption
on resume.
Sarah Sharp
On Tue, Feb 19, 2013 at 08:59:35AM -0500, Tony Camuso
Hello.
On 04/03/2013 02:18 PM, Christian Engelmayer wrote:
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
From: Kishon Vijay Abraham I
Date: Wed, 3 Apr 2013 12:05:30 +0530
> This patch series is about drivers/phy which will be used for now by
> usb, sata and maybe some video PHY's. Network itself has a
> comprehensive PHY in drivers/net/phy which we'd like to merge it with
> drivers/phy so that we ha
Hi,
On Wed, Apr 03, 2013 at 02:55:47PM +, Arnd Bergmann wrote:
> On Wednesday 03 April 2013, Felipe Balbi wrote:
> > const ? Maybe provide a:
> >
> > #define DEFINE_PHY_OPS(name)\
> > const struct phy_ops #name_phy_ops = {
> >
> > macro ? This will force people to add the const keyword :
Hi,
On Wed, Apr 03, 2013 at 08:02:52PM +0530, Kishon Vijay Abraham I wrote:
> + ret = -EINVAL;
> + goto err0;
> + }
> +
> + if (!phy_class)
> + phy_core_init();
> >>>
> >>>why don't you setup the class on module_init ? Then this would be a
> >>>terri
Hi,
On Wed, Apr 03, 2013 at 07:22:38AM -0700, Greg KH wrote:
> 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
> > > warning
On 03.04.2013 17:19, Michael Trimarchi wrote:
> Hi Daniel
>
> On 03/04/13 17:00, Daniel Mack wrote:
>> Hi Michael,
>>
>> On 03.04.2013 16:11, Michael Trimarchi wrote:
>>> On 03/04/13 15:55, Michael Trimarchi wrote:
On 03/04/13 12:23, Daniel Mack wrote:
> Hi David,
>
> On 03.04.201
On Wed, 2013-04-03 at 16:02 +0200, Fabio Baltieri wrote:
> 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.
Could go bananas with this and all kinds of recovery schemes, but na
On Wednesday 03 April 2013, Felipe Balbi wrote:
> const ? Maybe provide a:
>
> #define DEFINE_PHY_OPS(name)\
> const struct phy_ops #name_phy_ops = {
>
> macro ? This will force people to add the const keyword :-)
Forcing people to use const structures is good, but I think it would be
better
On 04/02/2013 08:21 PM, Tony Lindgren wrote:
> * Felipe Balbi [130320 09:24]:
>> On Wed, Mar 20, 2013 at 09:13:24AM -0700, Tony Lindgren wrote:
>>> * Felipe Balbi [130320 09:00]:
On Wed, Mar 20, 2013 at 05:44:40PM +0200, Roger Quadros wrote:
> Add clk_rate parameter to platform data. If
On Wed, Apr 3, 2013 at 7:48 PM, Felipe Balbi wrote:
> 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
Hi,
On Wednesday 03 April 2013 07:57 PM, Felipe Balbi wrote:
hi,
On Wed, Apr 03, 2013 at 07:48:42PM +0530, Kishon Vijay Abraham I wrote:
+struct phy *of_phy_xlate(struct phy *phy, struct of_phandle_args *args)
+{
+ return phy;
+}
+EXPORT_SYMBOL_GPL(of_phy_xlate);
so you get a PHY and j
hi,
On Wed, Apr 03, 2013 at 07:48:42PM +0530, Kishon Vijay Abraham I wrote:
> >>+struct phy *of_phy_xlate(struct phy *phy, struct of_phandle_args *args)
> >>+{
> >>+ return phy;
> >>+}
> >>+EXPORT_SYMBOL_GPL(of_phy_xlate);
> >
> >so you get a PHY and just return it ? What gives ?? (maybe I skipp
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:
> >
> > c8801a8 regul
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
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
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 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 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,
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,
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
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
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
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
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(+
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: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 12 +---
1 file changed, 9 insert
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");
> > >> >> +
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
> >> >> ---
> >>
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 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
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
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 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 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 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
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,
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
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
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. 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
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
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
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
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
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
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
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: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/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
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
>
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,
(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
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
> -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
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
1 - 100 of 158 matches
Mail list logo
