In a similar light to the i8253 series, this consolidates 17 ARM
MMIO counter clocksources into a single common implementation. This
common implementation caters for 32-bit and 16-bit register access
sizes, up and down counters, and various bit sizes of those counters.
Patch 1 is already in John
The OMAP1 clocksource interrupt handler just increments a variable
which otherwise isn't used, so this seems to be unnecessary. Tony
Lindgren confirms, so lets remove it.
Cc: Tony Lindgren t...@atomide.com
Cc: linux-omap@vger.kernel.org
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
---
Cc: Tony Lindgren t...@atomide.com
Cc: linux-omap@vger.kernel.org
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
---
arch/arm/mach-omap1/time.c | 31 ---
1 files changed, 16 insertions(+), 15 deletions(-)
diff --git a/arch/arm/mach-omap1/time.c
Add a generic mmio clocksource, covering both 32-bit and 16-bit register
access sizes, for up or down counters. This can be used to easily
create clocksources for simple counter-based implementations.
Cc: Alessandro Rubini rub...@unipv.it
Cc: Colin Cross ccr...@android.com
Cc: Eric Miao
Convert the OMAP1 32-bit down counting clocksource to the generic
clocksource infrastructure.
Cc: Tony Lindgren t...@atomide.com
Cc: linux-omap@vger.kernel.org
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
---
arch/arm/mach-omap1/time.c | 23 ++-
On Tue, May 10, 2011 at 08:29:18AM +0100, Russell King - ARM Linux wrote:
Add a generic mmio clocksource, covering both 32-bit and 16-bit register
access sizes, for up or down counters. This can be used to easily
create clocksources for simple counter-based implementations.
Cc: Alessandro
On Tue, May 10, 2011 at 10:38:41AM +0200, Sascha Hauer wrote:
You forgot to initialize cs-reg. With this:
Damnit. Fixed.
Tested-by: Sascha Hauer s.ha...@pengutronix.de
Thanks.
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
When DBG() is used in a simple if-else, the resulting code path
currently depends on the definition of DBG(). Inserting the statement in
a do { ... } while (0) prevents this possible misuse.
Signed-off-by: Niels de Vos nde...@redhat.com
---
Note, I have not found any offenders, but a mistake can
On Mon, 2011-05-09 at 20:48 +0530, Mayuresh Janorkar wrote:
picodlp panel driver is required for driving DLP dpp2600.
It consists of a dss driver and an i2c_client.
i2c_client is required for sending commands to dpp (DLP Pico Projector).
The power-up sequence consists of:
Setting PWRGOOD
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Niels de Vos
Sent: Tuesday, May 10, 2011 2:51 PM
To: linux-omap@vger.kernel.org
Cc: linux-fb...@vger.kernel.org;
linux-ker...@vger.kernel.org; Niels de Vos
Subject:
On Tue, May 10, 2011 at 11:20, Niels de Vos nde...@redhat.com wrote:
When DBG() is used in a simple if-else, the resulting code path
currently depends on the definition of DBG(). Inserting the statement in
a do { ... } while (0) prevents this possible misuse.
Signed-off-by: Niels de Vos
On Tue, May 10, 2011 at 08:29:18AM +0100, Russell King - ARM Linux wrote:
+cycle_t clocksource_mmio_readl_up(struct clocksource *c)
+{
+ return readl_relaxed(to_mmio_clksrc(c)-reg);
+}
+
+cycle_t clocksource_mmio_readl_down(struct clocksource *c)
+{
+ return
-Original Message-
From: Valkeinen, Tomi
Sent: Tuesday, May 10, 2011 3:03 PM
To: Janorkar, Mayuresh
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v3 4/4] OMAP: DSS: Add picodlp panel driver
On Mon, 2011-05-09 at 20:48 +0530, Mayuresh Janorkar wrote:
snip
+/* This
Add API to determine IO-PAD wakeup event status for a given
hwmod dynamic_mux pad.
Signed-off-by: Govindraj.R govindraj.r...@ti.com
---
arch/arm/mach-omap2/mux.c| 28 ++
arch/arm/mach-omap2/mux.h| 13
Add two API's to set IO Pad wakeup capability based on hwmod
mux pins available and also to check the status of IO Pad wakeup
event.
This two patches are separated from uart_runtime patches posted
earlier and uart_runtime adaptation relies on these two API's.
Based on 2.6.39-rc6
Changes from
Add API to enable IO pad wakeup capability based on mux dynamic pad and
wake_up enable flag available from hwmod_mux initialization.
Use the wakeup_enable flag and enable wakeup capability
for the given pads. Wakeup capability will be enabled/disabled
during hmwod idle transition based on whether
Hi,
On Sat, May 7, 2011 at 3:19 AM, Paul Walmsley p...@pwsan.com wrote:
On Thu, 21 Apr 2011, Gulati, Shweta wrote:
Yes, but in current code clk_set_rate of dpll3_m2 -
'omap3_core_dpll_m2_set_rate'
doesn't update clk.rate, I will submit patch fixing that bug and will
make sure that
set_rate
On Tue, May 10, 2011 at 10:42 AM, Geert Uytterhoeven
ge...@linux-m68k.org wrote:
On Tue, May 10, 2011 at 11:20, Niels de Vos nde...@redhat.com wrote:
When DBG() is used in a simple if-else, the resulting code path
currently depends on the definition of DBG(). Inserting the statement in
a do {
When DBG() is used in a simple if-else, the resulting code path
currently depends on the definition of DBG(). Inserting the statement in
a do { ... } while (0) prevents this possible misuse.
Signed-off-by: Niels de Vos nde...@redhat.com
---
V2: add the missing closing }
Note, I have not found
On Tue, 2011-05-10 at 15:57 +0530, Janorkar, Mayuresh wrote:
It is better to request and initialize the GPIOs in the board file. The
reason for this is that the PicoDLP device should be off if it's not
used, or if the driver is not even compiled in. So the board file should
make sure that
This patch adds a basic nand support for the omap3evm.
Signed-off-by: Bryan DE FARIA bdefa...@adeneo-embedded.com
---
arch/arm/mach-omap2/board-omap3evm.c | 38 ++
1 files changed, 38 insertions(+), 0 deletions(-)
diff --git
-Original Message-
From: Valkeinen, Tomi
Sent: Tuesday, May 10, 2011 4:44 PM
To: Janorkar, Mayuresh
Cc: linux-omap@vger.kernel.org
Subject: RE: [PATCH v3 4/4] OMAP: DSS: Add picodlp panel driver
On Tue, 2011-05-10 at 15:57 +0530, Janorkar, Mayuresh wrote:
It is better to
On Tue, 2011-05-10 at 11:42 +0200, Geert Uytterhoeven wrote:
What about using the standard pr_debug()/dev_dbg() instead?
With dynamic debug, it can be enabled at run time.
As a bonus, you get printf()-style format checking if debugging is disabled.
Yes, dev_dbg co. would be better.
However,
On Tue, May 10, 2011 at 14:08, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Tue, 2011-05-10 at 11:42 +0200, Geert Uytterhoeven wrote:
What about using the standard pr_debug()/dev_dbg() instead?
With dynamic debug, it can be enabled at run time.
As a bonus, you get printf()-style format
On Tue, 2011-05-10 at 12:07 +0100, Niels de Vos wrote:
When DBG() is used in a simple if-else, the resulting code path
currently depends on the definition of DBG(). Inserting the statement in
a do { ... } while (0) prevents this possible misuse.
Signed-off-by: Niels de Vos nde...@redhat.com
Tony Lindgren t...@atomide.com writes:
* Russell King - ARM Linux li...@arm.linux.org.uk [110508 19:24]:
MPU timer 2 is used on OMAP1 for the clock source and scheduler clock.
It registers an interrupt, which counts the number of overflows of
this timer. However, this counter is only
On Mon, 2011-05-09 at 21:19 +0200, Mark Brown wrote:
On Mon, May 09, 2011 at 06:34:34PM +0300, Tomi Valkeinen wrote:
The second thing is that even if the power source for vdds_dsi may be
configured differently on different boards, the same vdds_dsi goes to
multiple DSS HW blocks inside
Hi Tony,
On Friday 29 April 2011 12:03:10 Laurent Pinchart wrote:
Hi Tony,
On Wednesday 27 April 2011 16:03:02 Laurent Pinchart wrote:
The iommu shares an interrupt line with the OMAP3 ISP. The iommu
interrupt handler must check the fault status and return IRQ_HANDLED
when no fault
The code contains the similarities in the error path of probe function. Let's
combine them at one place.
Signed-off-by: Andy Shevchenko ext-andriy.shevche...@nokia.com
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
drivers/mmc/host/omap_hsmmc.c | 17 ++---
1 files
There are two places where the same calculations are done. Let's split them to
separate function.
In addition the new function is simplified by usage DIV_ROUND_UP kernel macro.
Signed-off-by: Andy Shevchenko ext-andriy.shevche...@nokia.com
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
Russell King - ARM Linux li...@arm.linux.org.uk writes:
The OMAP1 clocksource interrupt handler just increments a variable
which otherwise isn't used, so this seems to be unnecessary. Tony
Lindgren confirms, so lets remove it.
Cc: Tony Lindgren t...@atomide.com
Cc:
picodlp projector is supported by OMAP.
OMAP4430 SDP and EVM boards have an on board projector called as picodlp
projector.
picodlp would be connected to display sub system as a display panel.
It has a dlp pico processor dpp2600.
The panel would be connected using 24 bit parallel interface.
GPIO
picodlp is a TI projector supported by OMAP
picodlp is interfaced with host processor using pwrgood and emu_done pins.
In programming sequence it is required to send high to pwrgood to low
wait for a fraction of seconds and then wait for emu_done signal to go low.
picodlp would be ready to send/
From: Mythri P K mythr...@ti.com
picodlp is a projector connected supported by OMAP.
DLP used in OMAP4 is dpp2600 (DLP Pico Projector)
The DLP requires commands to be sent over i2c for configurations,
Commands are defined together in this header file
To know more about dpp2600 commands please
An on-board projector named picodlp is available for OMAP4430 SDP.
Entry for this picodlp as a panel is being added in dss_devices array
to the board file.
It needs 4 GPIO pins for interfacing with host processor
and these are defined and two of them are configured in board file.
Two GPIOs
picodlp panel driver is required for driving DLP dpp2600.
It consists of a dss driver and an i2c_client.
i2c_client is required for sending commands to dpp (DLP Pico Projector).
Based on original design from Mythri P K mythr...@ti.com
The power-up sequence consists of:
Setting PWRGOOD to a
* Laurent Pinchart laurent.pinch...@ideasonboard.com [110510 15:35]:
Hi Tony,
On Friday 29 April 2011 12:03:10 Laurent Pinchart wrote:
Hi Tony,
On Wednesday 27 April 2011 16:03:02 Laurent Pinchart wrote:
The iommu shares an interrupt line with the OMAP3 ISP. The iommu
interrupt
From: ext Laurent Pinchart laurent.pinch...@ideasonboard.com
Subject: Re: [URGENT - PATCH FOR 2.6.39] omap: iommu: Return IRQ_HANDLED in
fault handler when no fault occured
Date: Tue, 10 May 2011 14:39:56 +0200
Hi Tony,
On Friday 29 April 2011 12:03:10 Laurent Pinchart wrote:
Hi Tony,
On
* Tomi Valkeinen tomi.valkei...@ti.com [110509 19:58]:
On Mon, 2011-05-09 at 10:36 +0300, Tomi Valkeinen wrote:
Hi Tony,
I posted last week a patch set porting most of the old omapfb OMAP2/3
drivers
to DSS2 (http://marc.info/?l=linux-fbdevm=130451207802788w=2). That patch
set
On Tue, May 10, 2011 at 04:25:19PM +0530, Gulati, Shweta wrote:
Hi,
On Sat, May 7, 2011 at 3:19 AM, Paul Walmsley p...@pwsan.com wrote:
On Thu, 21 Apr 2011, Gulati, Shweta wrote:
Yes, but in current code clk_set_rate of dpll3_m2 -
'omap3_core_dpll_m2_set_rate'
doesn't update
On Tue, May 10, 2011 at 03:30:52PM +0300, Tomi Valkeinen wrote:
This sounds just the thing we need here. Do you think there's a chance
the code could get merged in the next window? And I'm also happy to test
the code with omapdss, whenever you have something ready.
Patch is below, tested with
On Tue, 2011-05-10 at 16:35 +0300, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [110509 19:58]:
On Mon, 2011-05-09 at 10:36 +0300, Tomi Valkeinen wrote:
Hi Tony,
I posted last week a patch set porting most of the old omapfb OMAP2/3
drivers
to DSS2
Commit d594f1f31afe13edd8c02f3854a65cc58cfb3b74 (omap: IOMMU: add
support to callback during fault handling) broke interrupt line sharing
between the OMAP3 ISP and its IOMMU. Because of this, every interrupt
generated by the OMAP3 ISP is handled by the IOMMU driver instead of
being passed to the
Here are some smallish fixes and cleanups I made while porting N800's display
driver to DSS2.
Tomi
Tomi Valkeinen (8):
OMAP: DSS2: Add missing dummy functions
OMAPFB: fix wrong clock aliases and device name
OMAP: DSS2: RFBI: add rfbi_bus_lock
OMAP: DSS2: RFIB: clock enable/disable
dpi.c does not compile if DSI is not compiled in. Add the missing dummy
functions so that dpi.c compiles.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/dss.h | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git
The clock aliases and the dss platform device name have changed, and
omapfb fails to initialize. Update the names to correct ones.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap/dispc.c |4 ++--
drivers/video/omap/omapfb_main.c |2 +-
Add similar bus lock to RFBI as is in DSI. The panel driver can use the
bus lock to mark that the RFBI bus is currently in use.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/plat-omap/include/plat/display.h |2 ++
drivers/video/omap2/dss/rfbi.c| 16
RFBI enables and disables clocks inside almost every function to get a
finegrained control to the clocks. However, the current understanding is
that this is not necessary power-management-wise.
Change the clocking scheme so that RFI clocks are enabled when the
omapdss_rfbi_display_enable is
Add omap_rfbi_configure() which the panel driver can use to reconfigure
the data element size and the number of data lines in the RFBI bus.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/plat-omap/include/plat/display.h |2 ++
drivers/video/omap2/dss/rfbi.c|
The RFBI driver is quite messy. Remove dead and unneeded code and add
statics to functions.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/dss.h |7 --
drivers/video/omap2/dss/rfbi.c | 124 +---
2 files changed, 3
Remove old unused code lying inside #if 0.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/omapfb/omapfb-main.c | 29 -
1 files changed, 0 insertions(+), 29 deletions(-)
diff --git a/drivers/video/omap2/omapfb/omapfb-main.c
omapfb_mode_to_timings() had struct fb_info, struct fb_var and struct
fb_ops allocated from stack. This caused the stack usage grow quite
high.
Use kzalloc to allocate the structs instead.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/omapfb/omapfb-main.c | 49
From 5796d8d8a0ea5aee342b78ca6ead229971cff6c5 Mon Sep 17 00:00:00 2001
From: Suman Anna s-a...@ti.com
Date: Wed, 4 May 2011 17:45:37 -0500
Subject: [PATCH] omap: iommu: fix pte attributes for super section
The PTE programming causes a 16MB entry to be interpreted
as a 4K entry because of the
On Tue, May 10, 2011 at 02:26:57PM +0200, Kevin Hilman wrote:
Tony Lindgren t...@atomide.com writes:
* Russell King - ARM Linux li...@arm.linux.org.uk [110508 19:24]:
MPU timer 2 is used on OMAP1 for the clock source and scheduler clock.
It registers an interrupt, which counts the number
Hi,
Tomi Valkeinen [tomi.valkei...@ti.com]:
omapfb_mode_to_timings() had struct fb_info, struct fb_var and struct
fb_ops allocated from stack. This caused the stack usage grow quite
high.
Use kzalloc to allocate the structs instead.
[...]
+ fbi = kzalloc(sizeof(*fbi), GFP_KERNEL);
On Mon, Mar 14, 2011 at 06:38, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
On OMAP SMP configuartion, both processors share the voltage
and clock. So both CPUs needs to be scaled together and hence
needs software co-ordination.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
-Original Message-
From: linux-fbdev-ow...@vger.kernel.org [mailto:linux-fbdev-
ow...@vger.kernel.org] On Behalf Of Valkeinen, Tomi
Sent: Tuesday, May 10, 2011 9:54 PM
To: linux-omap@vger.kernel.org; linux-fb...@vger.kernel.org
Cc: Valkeinen, Tomi
Subject: [PATCH 0/8] OMAP: DSS2:
-Original Message-
From: linux-fbdev-ow...@vger.kernel.org [mailto:linux-fbdev-
ow...@vger.kernel.org] On Behalf Of Valkeinen, Tomi
Sent: Tuesday, May 10, 2011 9:54 PM
To: linux-omap@vger.kernel.org; linux-fb...@vger.kernel.org
Cc: Valkeinen, Tomi
Subject: [PATCH 8/8] OMAP: DSS2:
58 matches
Mail list logo
