On Tuesday 27 August 2013 09:36 PM, Dave Gerlach wrote:
On 08/27/2013 05:11 AM, Rajendra Nayak wrote:
Remove the empty am33xx_sram_init() function.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap2/sram.c |7 ---
1 file changed, 7 deletions(-)
diff --git
On Mon, Aug 26, 2013 at 08:15:17PM +0200, Arnd Bergmann wrote:
On Monday 26 August 2013 19:40:57 Vinod Koul wrote:
And the selection should be done for the cases where you dont have
programmable
mux in dmac. For programmable ones passing slave_id in dma_slave_config
should
be fine.
On Tuesday 27 August 2013 04:53 PM, Sekhar Nori wrote:
On Tuesday 27 August 2013 03:41 PM, Rajendra Nayak wrote:
Use drivers/misc/sram.c driver to manage SRAM on all DT only
OMAP platforms (am33xx, am43xx, omap4 and omap5) instead of
the existing private implementation.
Address and size
On Tuesday 27 August 2013 06:55 PM, Santosh Shilimkar wrote:
+ Paul,
On Tuesday 27 August 2013 06:11 AM, Rajendra Nayak wrote:
Make all OMAP DT only platforms (am33xx, am43xx, omap4 and omap5)
use drivers/misc/sram.c driver instead of the omap internal
implementation for SRAM handling.
Hi,
Here's a pull request for the board file changes to take the new display
drivers into use.
If there's an early pull request going to Linus during the merge window, it'd
be nice to have these in that request. That would give me time to send a pull
request to Linus containing removal of the
Hi,
I'm seeing odd clock behavior with Beagle, booting with DT. I'm using
v3.11-rc7 + DSS DT patches.
It looks to me that when setting the rate of a clock, its child clock's
rate is not updated correctly. Here's pieces of boot log (full log
attached):
Here my code prints the current clocks.
On 08/28/2013 12:22 PM, Tomi Valkeinen wrote:
Hi,
I'm seeing odd clock behavior with Beagle, booting with DT. I'm using
v3.11-rc7 + DSS DT patches.
I guess you are not using the clock DT patches? Just making sure I
didn't break anything. :)
It looks to me that when setting the rate of a
On 28/08/13 12:48, Tero Kristo wrote:
On 08/28/2013 12:22 PM, Tomi Valkeinen wrote:
Hi,
I'm seeing odd clock behavior with Beagle, booting with DT. I'm using
v3.11-rc7 + DSS DT patches.
I guess you are not using the clock DT patches? Just making sure I
didn't break anything. :)
No, plain
On Wednesday 28 August 2013 11:53 AM, Rajendra Nayak wrote:
On Tuesday 27 August 2013 04:53 PM, Sekhar Nori wrote:
On Tuesday 27 August 2013 03:41 PM, Rajendra Nayak wrote:
Use drivers/misc/sram.c driver to manage SRAM on all DT only
OMAP platforms (am33xx, am43xx, omap4 and omap5) instead of
Here are some basic OMAP test results for Linux v3.11-rc7.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.11-rc7/20130825195715/
Test summary
Build: uImage:
Pass (14/14): n800_multi_omap2xxx, n800_only_a, omap1_defconfig,
Hi,
On Wednesday 28 August 2013 12:50 AM, Felipe Balbi wrote:
Hi,
On Mon, Aug 26, 2013 at 01:44:49PM +0530, Kishon Vijay Abraham I wrote:
On Wednesday 21 August 2013 11:16 AM, Kishon Vijay Abraham I wrote:
Added a generic PHY framework that provides a set of APIs for the PHY
drivers
to
On 08/28/2013 01:14 PM, Tomi Valkeinen wrote:
On 28/08/13 12:48, Tero Kristo wrote:
On 08/28/2013 12:22 PM, Tomi Valkeinen wrote:
Hi,
I'm seeing odd clock behavior with Beagle, booting with DT. I'm using
v3.11-rc7 + DSS DT patches.
I guess you are not using the clock DT patches? Just making
On Tuesday 27 August 2013 19:18:55 Wolfram Sang wrote:
The driver should support the same chip models reardless of whether it's
used with or without DT. If an entry in the OF table has no corresponding
entry in the I2C table I would consider that as a driver bug.
Linus Walleij posted a
Hi Paul,
On Wednesday 21 August 2013 08:23 AM, Paul Walmsley wrote:
Currently there is no public TRM available for AM43x.
Can you think of any way that the data can be doublechecked against some
reference or against the reality of the chip?
This series has been tested on a pre-silicon
Hi Paul,
On Wednesday 21 August 2013 08:50 AM, Paul Walmsley wrote:
+/* PRM instances */
+#define AM43XX_PRM_OCP_SOCKET_INST 0x
+#define AM43XX_PRM_MPU_INST 0x0300
+#define AM43XX_PRM_GFX_INST 0x0400
+#define
Hi Benoit,
On Tuesday 20 August 2013 02:48 PM, Benoit Cousson wrote:
Otherwise, I guess that most of these patches should be non-intrusive
for other OMAPs beside that one (ARM: OMAP2+: CM: reintroduce SW_SLEEP
for OMAP4). And for the moment, that's maybe the most important point.
Have you
Hi Rajendra,
On Wednesday 21 August 2013 12:43 PM, Rajendra Nayak wrote:
+void omap4_cminst_clkdm_force_sleep(u8 part, s16 inst, u16 cdoffs)
+{
+_clktrctrl_write(OMAP34XX_CLKSTCTRL_FORCE_SLEEP, part, inst, cdoffs);
I guess this won't work on omap4/5 where some clockdomains do not
Hi Rajendra,
On Wednesday 21 August 2013 05:00 PM, Rajendra Nayak wrote:
On Friday 02 August 2013 07:08 PM, Afzal Mohammed wrote:
Reuse OMAP4 operations on AM43x.
Signed-off-by: Ambresh K ambr...@ti.com
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/omap_hwmod.c |
On Wednesday 28 August 2013 02:29 AM, Nayak, Rajendra wrote:
On Tuesday 27 August 2013 06:55 PM, Santosh Shilimkar wrote:
+ Paul,
On Tuesday 27 August 2013 06:11 AM, Rajendra Nayak wrote:
Make all OMAP DT only platforms (am33xx, am43xx, omap4 and omap5)
use drivers/misc/sram.c driver instead
On Wednesday 28 August 2013 07:08 PM, Santosh Shilimkar wrote:
On Wednesday 28 August 2013 02:29 AM, Nayak, Rajendra wrote:
On Tuesday 27 August 2013 06:55 PM, Santosh Shilimkar wrote:
+ Paul,
On Tuesday 27 August 2013 06:11 AM, Rajendra Nayak wrote:
Make all OMAP DT only platforms (am33xx,
Bump up the order, since extcon is a framework and needed by
other drivers. With the previous order it failed to detect
extcon device in DWC3 when both were compiled built-in.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/Makefile | 2 +-
1 file changed, 1 insertion(+), 1
Add
-extcon nodes for USB ID pin detection.
-i2c nodes.
-pcf nodes to which USB ID pin is connected.
Signed-off-by: George Cherian george.cher...@ti.com
---
arch/arm/boot/dts/dra7-evm.dts | 52 +-
1 file changed, 51 insertions(+), 1
Hi,
These patches add generic support for USB VBUS/ID pin detection using extcon
framework.
The USB ID pin on DRA7xx is connected via the gpio expander pcf8575.
The interrupt line of the same is connected to the gpio 11 of bank 6.
The following driver relies on the gpio interrupt to notify
Add a generic USB VBUS/ID detection EXTCON driver. This driver expects
the ID/VBUS pin are connected via GPIOs. This driver is tested on
DRA7x board were the ID pin is routed via GPIOs. The driver supports
both VBUS and ID pin configuration and ID pin only configuration.
Signed-off-by: George
Hello.
On 08/28/2013 05:59 PM, George Cherian wrote:
Add
-extcon nodes for USB ID pin detection.
-i2c nodes.
-pcf nodes to which USB ID pin is connected.
Signed-off-by: George Cherian george.cher...@ti.com
---
arch/arm/boot/dts/dra7-evm.dts | 52
On Wednesday 28 August 2013 09:42 AM, Rajendra Nayak wrote:
On Wednesday 28 August 2013 07:08 PM, Santosh Shilimkar wrote:
On Wednesday 28 August 2013 02:29 AM, Nayak, Rajendra wrote:
On Tuesday 27 August 2013 06:55 PM, Santosh Shilimkar wrote:
+ Paul,
On Tuesday 27 August 2013 06:11 AM,
Hi Ted,
On Tue, Aug 27, 2013 at 6:01 PM, Theodore Ts'o ty...@mit.edu wrote:
On Tue, Aug 27, 2013 at 05:47:22PM -0400, Kevyn-Alexandre Paré wrote:
mmcblk0: error -110 sending status command, retrying
mmcblk0: error -110 sending status command, retrying
mmcblk0: error -110 sending status
Kevin,
On 08/27/2013 04:25 PM, Kevin Hilman wrote:
Suman Anna s-a...@ti.com writes:
Kevin,
On 08/26/2013 10:50 PM, Kevin Hilman wrote:
Suman Anna s-a...@ti.com writes:
The WkupM3 mailbox used for triggering PM operations such as suspend
and resume on AM33x/AM43x is special in that the
Hi,
These patches add generic support for USB VBUS/ID pin detection using extcon
framework.
The USB ID pin on DRA7xx is connected via the gpio expander pcf8575.
The interrupt line of the same is connected to the gpio 11 of bank 6.
The following driver relies on the gpio interrupt to notify the
Bump up the order, since extcon is a framework and needed by
other drivers. With the previous order it failed to detect
extcon device in DWC3 when both were compiled built-in.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/Makefile | 2 +-
1 file changed, 1 insertion(+), 1
Add a generic USB VBUS/ID detection EXTCON driver. This driver expects
the ID/VBUS pin are connected via GPIOs. This driver is tested on
DRA7x board were the ID pin is routed via GPIOs. The driver supports
both VBUS and ID pin configuration and ID pin only configuration.
Signed-off-by: George
On 8/28/2013 7:29 PM, George Cherian wrote:
Hi,
These patches add generic support for USB VBUS/ID pin detection using extcon
framework.
The USB ID pin on DRA7xx is connected via the gpio expander pcf8575.
The interrupt line of the same is connected to the gpio 11 of bank 6.
The following
On Wed, Aug 28, 2013 at 11:22:58AM -0400, Kevyn-Alexandre Paré wrote:
We try multiple of our system ( Different micro SD from SanDisk +
Overo with OMAP3) and they are all doing this with the SanDisk 64GB,
32GB :
On 08/28/2013 09:33 PM, George Cherian wrote:
Add
-extcon nodes for USB ID pin detection.
-i2c nodes.
-pcf nodes to which USB ID pin is connected.
Signed-off-by: George Cherian george.cher...@ti.com
---
arch/arm/boot/dts/dra7-evm.dts | 50
Add
-extcon nodes for USB ID pin detection.
-i2c nodes.
-pcf nodes to which USB ID pin is connected.
Signed-off-by: George Cherian george.cher...@ti.com
---
arch/arm/boot/dts/dra7-evm.dts | 50 +-
1 file changed, 49 insertions(+), 1
On Thu, Aug 22, 2013 at 10:46:10PM -0700, Tony Lindgren wrote:
The following changes since commit b36f4be3de1b123d8601de062e7dbfc904f305fb:
Linux 3.11-rc6 (2013-08-18 14:36:53 -0700)
are available in the git repository at:
Hi
On Tue, 6 Aug 2013, Lokesh Vutla wrote:
Add RNG hwmod data for AM33xx SoC.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
I tried to queue this one, but it caused AM33xx boots to hang.
Thought it might be related to the patch ordering -- seems to me that
the clock change patch needed
On Thu, Aug 22, 2013 at 10:46:10PM -0700, Tony Lindgren wrote:
Matus Ujhelyi (1):
ARM: OMAP2+: am33xx-restart: trigger warm reset on omap2+ boards
Sigh. am33xx has been a bit of a pain this release cycle. Can you please
start double-checking builds when you apply am33xx stuff? :(
This
On Thu, 22 Aug 2013 18:00:14 +0200, Wolfram Sang w...@the-dreams.de wrote:
I2C of helpers used to live in of_i2c.c but experience (from SPI) shows
that it is much cleaner to have this in the core. This also removes a
circular dependency between the helpers and the core, and so we can
finally
Hi George,
You didn't modify this patchset about my comment on v1 patchset.
Please pay attention to comment.
On 08/29/2013 02:33 AM, George Cherian wrote:
Add a generic USB VBUS/ID detection EXTCON driver. This driver expects
the ID/VBUS pin are connected via GPIOs. This driver is tested on
Hi Chanwoo,
Thanks for the review and sorry for all the trivial mistakes.
On 8/29/2013 7:05 AM, Chanwoo Choi wrote:
Hi George,
You didn't modify this patchset about my comment on v1 patchset.
Please pay attention to comment.
On 08/29/2013 02:33 AM, George Cherian wrote:
Add a generic USB
On 8/28/2013 11:24 PM, Sergei Shtylyov wrote:
On 08/28/2013 09:33 PM, George Cherian wrote:
Add
-extcon nodes for USB ID pin detection.
-i2c nodes.
-pcf nodes to which USB ID pin is connected.
Signed-off-by: George Cherian george.cher...@ti.com
---
* Olof Johansson o...@lixom.net [130828 11:58]:
On Thu, Aug 22, 2013 at 10:46:10PM -0700, Tony Lindgren wrote:
Matus Ujhelyi (1):
ARM: OMAP2+: am33xx-restart: trigger warm reset on omap2+ boards
Sigh. am33xx has been a bit of a pain this release cycle. Can you please
start
43 matches
Mail list logo
