=134272967203409w=2
Signed-off-by: Raphaël Assénat r...@8d.com
Chandrabhanu has posted a series that removes a bunch of cpu_is checks
from omapdss. On of them is the use of VDDS_DSI in dpi.c.
Can you wait until I've merged those patches to omapdss master branch
(probably a few days
On 24/08/12 04:38 AM, Tomi Valkeinen wrote:
On Tue, 2012-08-21 at 10:29 -0400, Raphaël Assénat wrote:
On 21/08/12 06:49 AM, Tomi Valkeinen wrote:
On Wed, 2012-08-15 at 11:26 -0400, Raphaël Assénat wrote:
+
+ /* ChiMei G121S1-L01 */
+ {
+ {
...
+ .vsync_level
On 21/08/12 06:49 AM, Tomi Valkeinen wrote:
On Wed, 2012-08-15 at 11:26 -0400, Raphaël Assénat wrote:
+
+ /* ChiMei G121S1-L01 */
+ {
+ {
...
+ .vsync_level= OMAPDSS_SIG_ACTIVE_HIGH,
+ .hsync_level= OMAPDSS_SIG_ACTIVE_HIGH
are not used, I think the vsync_level, hsync_level and
sync_pclk_edge entries could be removed. Otherwise the updated patch
works fine as is.
Best regards,
Raphaël Assénat
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More
trying to remove the
cpu_is checks (soc_is goes in the same category).
I guess we need to add entries for the AM3xxx SoCs in the
dss_features.c.
Any idea what other differences AM3xxx has compared to OMAP3?
This is the only one I am aware of.
Best regards,
Raphaël Assénat
--
To unsubscribe
doing something to attain a similar goal in the past?
Best regards,
Raphaël Assénat
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
written
to MCR or rewriting values read from MSR on the fly).
Signed-off-by: Raphaël Assénat r...@8d.com
--- a/arch/arm/plat-omap/include/plat/omap-serial.h
+++ b/arch/arm/plat-omap/include/plat/omap-serial.h
@@ -63,6 +63,8 @@ struct omap_uart_port_info {
resource_size_t mapbase
should then call these
instead of going ahead and performing direct memory access.
Tested with 8250.c and omap-serial.c on a custom AM3505 system.
Signed-off-by: Raphaël Assénat
--- a/arch/arm/plat-omap/include/plat/serial.h
+++ b/arch/arm/plat-omap/include/plat/serial.h
@@ -105,10 +105,20
This patch provides a way to enable the GPMC limited addressing
mode which is needed to access nonmultiplexed devices.
Signed-off-by: Raphael Assenat r...@8d.com
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
index 130034b..521944a 100644
--- a/arch/arm/mach-omap2/gpmc.c
On 07/07/11 11:35 AM, Tony Lindgren wrote:
* Raphaël Assénat r...@8d.com [110707 17:36]:
This is unrelated to this thread but..
do you think we could merge this one?
[PATCH 5/5] am3505/3517: Various platform defines for UART4
http://marc.info/?l=linux-omapm=130980816418020w=4
It does
On 07/07/11 10:19 AM, Tony Lindgren wrote:
* Raphaël Assénat r...@8d.com [110706 19:47]:
Fixes according to Sanjeev's comments in previous thread.
---
This patch adds support for the AM35xx ZCN package specific muxmodes.
Thanks for doing this. Still it's quite a few lines of data.. So
I
On 06/07/11 04:54 AM, Premi, Sanjeev wrote:
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Tony Lindgren
Sent: Wednesday, July 06, 2011 12:26 PM
To: Raphaël Assénat; Paul Walmsley
Cc: linux-omap@vger.kernel.org
On 05/07/11 05:59 AM, Premi, Sanjeev wrote:
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Raphaël Assénat
Sent: Tuesday, July 05, 2011 12:59 AM
To: linux-omap@vger.kernel.org
Subject: AM3505/3517 support
Hello
This patch adds support for the AM35xx ZCN package specific muxmodes.
Signed-off-by: Raphael Assenat r...@8d.com
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index 4ae6257..5c880de 100644
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -103,6
Fixes according to Sanjeev's comments in previous thread.
---
This patch adds support for the AM35xx ZCN package specific muxmodes.
Signed-off-by: Raphael Assenat r...@8d.com
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index 4ae6257..bf452eb 100644
---
On 06/07/11 12:11 PM, Premi, Sanjeev wrote:
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Raphaël Assénat
Sent: Wednesday, July 06, 2011 8:59 PM
To: linux-omap@vger.kernel.org
Subject: [PATCH] AM3505/3517 ZCN package
With the addition of support for the ZCN package, there
are even more placeholders in the superset, such as:
_OMAP3_MUXENTRY(GPMC_A11, 0,
NULL, NULL, NULL, NULL,
NULL, NULL, NULL, NULL),
which takes a lot of space. This patch introduces and uses
On 05/07/11 07:19 AM, Tony Lindgren wrote:
* Raphaël Assénat r...@8d.com [110704 12:51]:
The am3505 is apparently so similar to the 3430 that it was treated as such
(omap_chip.oc was being set to CHIP_IS_OMAP3430ES3_1). There are however a
few differences that need to be addressed. I have
Add support for the AM35xx UART4 fclk. Based on information
found on TI's E2E forum.
Signed-off-by: Raphael Assenat r...@8d.com
diff --git a/arch/arm/mach-omap2/clock3xxx_data.c
b/arch/arm/mach-omap2/clock3xxx_data.c
index 75b119b..3706aaa 100644
--- a/arch/arm/mach-omap2/clock3xxx_data.c
+++
Add missing definitions for the AM3505/3517 UART4 such
as DMAs, INTs and base address.
Signed-of-by: Raphael Assenat
diff --git a/arch/arm/plat-omap/include/plat/dma.h
b/arch/arm/plat-omap/include/plat/dma.h
index d1c916f..dc562a5 100644
--- a/arch/arm/plat-omap/include/plat/dma.h
+++
Create a CHIP_IS macro fore AM35xx CPUs.
Signed-off-by: Raphael Assenat r...@8d.com
diff --git a/arch/arm/plat-omap/include/plat/cpu.h
b/arch/arm/plat-omap/include/plat/cpu.h
index 8198bb6..f3def59 100644
--- a/arch/arm/plat-omap/include/plat/cpu.h
+++ b/arch/arm/plat-omap/include/plat/cpu.h
@@
In cpu.h, OMAP35XX_CLASS is currently defined as 0x3534.
the cpu_is_omap34xx() return 1 even on am3505 and am3517.
I'm not sure if the CPU class bits should be changed to 0x35
(redefining OMAP35XX_CLASS to 0x3535). So instead, I'm
adding code to explicitely ignore am3505 and am3517.
Fix id.c to set CHIP_IS_AM35XX instead of CHIP_IS_OMAP3430ES3_1.
Then, in order to enable the same functionalities, we need to
add CHIP_IS_AM35XX where CHIP_IS_OMAP3430, was is used in
clockdomains2xxx_3xxx_data, omap_hwmod_3xxx_data,
powerdomains2xxx_3xxx_data and powerdomains3xxx_data.
Also in
, the CBB package is used (board-am3517evm.c for instance) but there
are differences that prevent some GPIOs from being configured properly. It would
be nice to know if someone is working on this before I start...
Best regards,
Raphaël Assénat
8D Technologies inc.
--
To unsubscribe from this list: send
24 matches
Mail list logo
