- Original Message -
From: Shilimkar, Santosh santosh.shilim...@ti.com
---
#define L3_IO_OFFSET 0x9000
#define __L3_IO_ADDRESS(pa) ((pa) + L3_IO_OFFSET)/* Works for L3 */
#define __OMAP2_L3_IO_ADDRESS(pa) ((pa) + L3_IO_OFFSET)/* Works for L3
*/
#define l3_io_v2p(va) ((va) -
-Original Message-
From: V, Hemanth
Sent: Monday, August 24, 2009 11:40 AM
To: Shilimkar, Santosh; Pandita, Vikram; t...@atomide.com;
khil...@deeprootsystems.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/5] ARM: OMAP2/3/4: Split OMAP2_IO_ADDRESS to L3 and
L4
This patch splits OMAP2_IO_ADDRESS to OMAP2_L3_IO_ADDRESS and
OMAP2_L4_IO_ADDRESS to reclaim more IO space.
The omap_read*() and omap_write*() functions will work only over
L4 address space. Current omap kernel stack uses these functions
only to access registers over L4 io address space
: [PATCH 1/5] ARM: OMAP2/3/4: Split OMAP2_IO_ADDRESS to L3 and L4
That sure is a big cleanup patch and would take patience to complete!!
This patch splits OMAP2_IO_ADDRESS to OMAP2_L3_IO_ADDRESS and
OMAP2_L4_IO_ADDRESS to reclaim more IO space.
There is no reclaim of space with this patch. Its
: [PATCH 1/5] ARM: OMAP2/3/4: Split OMAP2_IO_ADDRESS to L3 and L4
That sure is a big cleanup patch and would take patience to complete!!
This patch splits OMAP2_IO_ADDRESS to OMAP2_L3_IO_ADDRESS and
OMAP2_L4_IO_ADDRESS to reclaim more IO space.
There is no reclaim of space with this patch
