On 6/11/2012 6:59 PM, Paul Walmsley wrote:
On Mon, 11 Jun 2012, Cousson, Benoit wrote:
In fact, neither prm_clkdm not cm_clkdm are valid clock domain on OMAP4
:-(.
I've just realized that you introduced that for 3.5, but this is wrong.
We should not start adding some fake clock domains just
Hi Afzal,
On 06/11/2012 09:26 AM, Afzal Mohammed wrote:
A driver is being created out of GPMC code. This is being
attempted to acheive by not breaking existing interface,
necessitating requirement of GPMC peripherals being able
to work with as well as without the help of driver. To not
break
On Mon, Jun 11, 2012 at 10:20:49AM +0530, Vinod Koul wrote:
I think it is a good idea. And I would like to extend it even a little
bit. Do we have any users of peripheral to peripheral slave dma?
IIRC that is not the case, or does anyone know of existence or plans
for such a h/w?
We have
On 06/11/2012 09:26 AM, Afzal Mohammed wrote:
Create a minimal driver out of gpmc code.
Responsibilities handled by earlier gpmc
initialization is now achieved in probe.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 170
On 06/11/2012 09:26 AM, Afzal Mohammed wrote:
Helpers for propulating given resource structure
with memory interrupt information.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 45
1 file changed, 45
On 6/11/2012 7:26 PM, Paul Walmsley wrote:
On Mon, 11 Jun 2012, Benoit Cousson wrote:
The following commit (794b480a37e3d284d6ee7344d8a737ef60476ed5) was adding
the PRCM IPs data for PRCM, CM, PRCM_MPU and SCRM.
The clkdm entry are not the correct ones and does not exist in the system.
On 06/11/2012 09:27 AM, Afzal Mohammed wrote:
Some of the GPMC peripherals depend on bootloader to do the
configuration. This facility is deprecated, notify user
about the present GPMC settings inform that that relying
on bootloader for GPMC setting is deprecated.
Nit, holler is slang. Just
On 06/11/2012 09:27 AM, Afzal Mohammed wrote:
Helper for configuring waitpin. There are two parts to it;
configuring at CS level and the other at device level.
A device embedding multiple CS has been provided the
capability to use same waitpin (different waitpins has not
been supported as
On 06/11/2012 09:27 AM, Afzal Mohammed wrote:
Helper for reconfiguring CS, peripheral that necessitated
it was OneNAND.
Why? I think you need to add more about why this was needed.
Jon
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 32
Hi Jon,
On Mon, Jun 11, 2012 at 21:13:45, Hunter, Jon wrote:
Which boards have been tested with this change?
Beagle board
Reviewed-by: Jon Hunter jon-hun...@ti.com
Thanks
Regards
Afzal
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
101 - 110 of 110 matches
Mail list logo