From: Andreas Naumann anaum...@ultratronik.de
This is a hard to reproduce problem which leads to non-functional USB-OTG port
in 0.1%-1% of all boots.
Tracked it down to commit e25bec160158abe86c276d7d206264afc3646281, which
introduces save/restore of OTG_INTERFSEL over suspend.
Since the resume
On Fri, Nov 22, 2013 at 12:51 AM, Sebastian Reichel s...@ring0.de wrote:
Hi Tony,
On Thu, Nov 21, 2013 at 10:58:45AM -0800, Tony Lindgren wrote:
Also, I just posted a patch to fix the eMMC that you may want to
try out.
Let's move eMMC diskussion to that patch :)
[...]
My
We have a custom AM335x board where the USB0_ID pin has been left floating.
By default, this puts the USB controller into peripheral mode, but we need
to force it into host mode.
This can be achieved in s/w by setting some bits in the relevant USB mode
register (see TRM 16.5.2.35).
This mode
On 11/21/2013 09:51 PM, Felipe Balbi wrote:
Hi,
On Thu, Nov 21, 2013 at 07:56:51PM -0600, Joel Fernandes wrote:
[...]
New functions for OF-only boot are introduced, and we can soon delete the old
versions once we migrate all platforms. Currently only AM335x is migrated and
actually,
Hi,
* Joel Fernandes jo...@ti.com [131121 18:00]:
Multiplatform support has made arch/arm/plat-omap/include/plat/ inaccessible
to
drivers outside the plat-omap directory [1]. Due to this the following drivers
are disabled with !CONFIG_ARCH_MULTIPLATFORM:
CONFIG_IR_RX51
The IDDIG input pin is normally used to determine the USB mode
(i.e. HOST or DEVICE).
On some systems (e.g. AM335x) leaving this pin floating allows
the USB mode to be set via software.
This patch adds support for this via the device tree.
Signed-off-by: Mark Jackson m...@newflow.co.uk
---
* Joel Fernandes jo...@ti.com [131121 18:00]:
+Required properties for system timers (clockevents/clocksource):
+- ti,timer-parent: System timer's parent mux clock needs to be setup.
+ This is currently hardcoded in code, for DT boot we
+ move this to
On Thu, Nov 21, 2013 at 7:56 PM, Joel Fernandes jo...@ti.com wrote:
This work is a migration effort of OMAP system timers to the
clocksource/clockevent framework. Consider this as a first-pass in this
effort.
There are few cleanups that need to be done first. The HWMOD code is
intertwined
On 11/22/2013 09:33 AM, Tony Lindgren wrote:
Hi,
* Joel Fernandes jo...@ti.com [131121 18:00]:
Multiplatform support has made arch/arm/plat-omap/include/plat/ inaccessible
to
drivers outside the plat-omap directory [1]. Due to this the following
drivers
are disabled with
On 11/22/2013 04:55 PM, Mark Jackson wrote:
The IDDIG input pin is normally used to determine the USB mode
(i.e. HOST or DEVICE).
On some systems (e.g. AM335x) leaving this pin floating allows
the USB mode to be set via software.
So you have a board where musb is used only as host or only
Hi Tony,
Thanks for your comments, few replies inline below..
On 11/22/2013 09:58 AM, Tony Lindgren wrote:
* Joel Fernandes jo...@ti.com [131121 18:00]:
+Required properties for system timers (clockevents/clocksource):
+- ti,timer-parent: System timer's parent mux clock needs to be setup.
+
On Thu, Nov 21, 2013 at 03:57:29PM -0800, Tony Lindgren wrote:
Well let's use just vaux3 then with a comment to the .dts file if that
works also on your 0x2204. It works on my 0x0010 too.
I folded in your changes to the updated patch below. Care to reply with
your Signed-off-by too assuming
Hallo,
On Fri, Nov 22, 2013 at 03:55:59PM +, Mark Jackson wrote:
The IDDIG input pin is normally used to determine the USB mode
(i.e. HOST or DEVICE).
On some systems (e.g. AM335x) leaving this pin floating allows
the USB mode to be set via software.
This patch adds support for this
On 11/22/2013 09:58 AM, Rob Herring wrote:
On Thu, Nov 21, 2013 at 7:56 PM, Joel Fernandes jo...@ti.com wrote:
This work is a migration effort of OMAP system timers to the
clocksource/clockevent framework. Consider this as a first-pass in this
effort.
There are few cleanups that need to be
On 22/11/13 16:38, Michael Grzeschik wrote:
Hallo,
On Fri, Nov 22, 2013 at 03:55:59PM +, Mark Jackson wrote:
The IDDIG input pin is normally used to determine the USB mode
(i.e. HOST or DEVICE).
On some systems (e.g. AM335x) leaving this pin floating allows
the USB mode to be set via
On 22/11/13 16:33, Sebastian Andrzej Siewior wrote:
On 11/22/2013 04:55 PM, Mark Jackson wrote:
The IDDIG input pin is normally used to determine the USB mode
(i.e. HOST or DEVICE).
On some systems (e.g. AM335x) leaving this pin floating allows
the USB mode to be set via software.
So you
On 11/22/2013 05:49 PM, Mark Jackson wrote:
and the ID pin not on ground or 3.3V?
What are the side effects? I remember correctly Bin wanted to avoid
settings this if it could be avoided.
Yes ... we have a host only USB port and an unconnected ID pin.
Is it too late to connect that pin?
On 11/22/2013 09:58 AM, Tony Lindgren wrote:
* Joel Fernandes jo...@ti.com [131121 18:00]:
+Required properties for system timers (clockevents/clocksource):
+- ti,timer-parent: System timer's parent mux clock needs to be setup.
+This is currently hardcoded in code, for DT
On 22/11/13 17:01, Sebastian Andrzej Siewior wrote:
On 11/22/2013 05:49 PM, Mark Jackson wrote:
and the ID pin not on ground or 3.3V?
What are the side effects? I remember correctly Bin wanted to avoid
settings this if it could be avoided.
Yes ... we have a host only USB port and an
* Joel Fernandes jo...@ti.com [131122 08:37]:
Hi Tony,
Thanks for your comments, few replies inline below..
On 11/22/2013 09:58 AM, Tony Lindgren wrote:
* Joel Fernandes jo...@ti.com [131121 18:00]:
+Required properties for system timers (clockevents/clocksource):
+- ti,timer-parent:
* Joel Fernandes jo...@ti.com [131122 09:06]:
On 11/22/2013 09:58 AM, Tony Lindgren wrote:
* Joel Fernandes jo...@ti.com [131121 18:00]:
+Required properties for system timers (clockevents/clocksource):
+- ti,timer-parent:System timer's parent mux clock needs to be
setup.
+
* Sebastian Reichel s...@ring0.de [131122 08:38]:
On Thu, Nov 21, 2013 at 03:57:29PM -0800, Tony Lindgren wrote:
Well let's use just vaux3 then with a comment to the .dts file if that
works also on your 0x2204. It works on my 0x0010 too.
I folded in your changes to the updated patch
On 11/22/2013 06:07 PM, Mark Jackson wrote:
Do you insists on having this change merged upstream?
No ... I didn't think it would be such an issue, so I'm happy to keep this
as a local patch if that's any better.
Felipe, Bin: Second opinion on that?
Mark J.
Sebastian
--
To unsubscribe
Hi Russ,
On Fri, Jan 11, 2013 at 12:09:56AM -0800, Russ Dill wrote:
I personally like the series, it certainly adds needed functionality.
I just wish there was a way to get it without a possible 4 second
delay.
I was just going through this patches and got confused by the same
thing, could
On Fri, Nov 22, 2013 at 10:42 AM, Joel Fernandes jo...@ti.com wrote:
On 11/22/2013 09:58 AM, Rob Herring wrote:
On Thu, Nov 21, 2013 at 7:56 PM, Joel Fernandes jo...@ti.com wrote:
This work is a migration effort of OMAP system timers to the
clocksource/clockevent framework. Consider this as a
Hello.
I was wondering what that the status of 1GHz support for the am37xx is.
It looks like smartreflex/avs and ABB drivers are there. Do they need
more work (e.g., DT support)? What DT nodes and related support need
to be added?
What pieces are being worked on and which ones aren't?
Is
On 11/22/2013 11:08 AM, Tony Lindgren wrote:
* Joel Fernandes jo...@ti.com [131122 08:37]:
Hi Tony,
Thanks for your comments, few replies inline below..
On 11/22/2013 09:58 AM, Tony Lindgren wrote:
* Joel Fernandes jo...@ti.com [131121 18:00]:
+Required properties for system timers
* Joel Fernandes jo...@ti.com [131122 16:32]:
On 11/22/2013 11:08 AM, Tony Lindgren wrote:
I don't think there's a dependency here to the omap clocks as the dmtimer
can implement the clocksource separately and internally still use clk_get
using the clock alias table.
You mean
Adding Thomas to the thread since discussion is about clocksource, and Mark
Rutland as discussion is related to timers and DT, thanks.
On 11/22/2013 02:01 PM, Rob Herring wrote:
On Fri, Nov 22, 2013 at 10:42 AM, Joel Fernandes jo...@ti.com wrote:
On 11/22/2013 09:58 AM, Rob Herring wrote:
On
Sorry, resending due to an MUA issue.
Adding Thomas to the thread since discussion is about clocksource, and Mark
Rutland as discussion is related to timers and DT, thanks.
On 11/22/2013 02:01 PM, Rob Herring wrote:
On Fri, Nov 22, 2013 at 10:42 AM, Joel Fernandes jo...@ti.com wrote:
On
I wonder if we also have some dependency to some earlier versions of
u-boot as u-boot now only muxes the essential pins?
This is exactly the problem in my case. I added #define
CONFIG_SYS_ENABLE_PADS_ALL in u-boot/include/configs/omap4_common.h
and now there is output.
I guess the reason that the
31 matches
Mail list logo
