On Mon, Aug 9, 2010 at 9:30 PM, stanley.miao <stanley.miao@xxxxxxxxxxxxx> wrote:
> Cliff Brake wrote:
>>
>> Functionally, what does this statement mean? The 3503 seems to have
>> the EN_IO [8] bit, but I've yet to figure out what the EN_IO_CHAIN
>> [16] means.
>>
>
> Please reference to Chapter 4.11 PRCM Off-Mode Management in OMAP35x TRM.
Thanks for the pointer. Do you know offhand what TI documentation
details the differences between the 3503 and the 3530 in this regard.
I'm also trying to piece together what practical impact this will have
on a system.
I have an older 3503 system, and it is still spewing "Wake up daisy
chain activation failed" messages. Do you expect the following patch
would have fixed this?
So I then instrumented the following macros:
CLIFF: cpu_is_omap3503 = 0
CLIFF: cpu_is_omap3515 = 0
CLIFF: cpu_is_omap3525 = 0
CLIFF: cpu_is_omap3530 = 0
CLIFF: is_omap3430 = 0
CLIFF: omap3_has_iva = 2
CLIFF: omap3_has_sgx = 0
CLIFF: omap3_has_io_wakeup = 64
Perhaps it is not a 3503??? The kernel prints the following on bootup:
OMAP3525 ES2.1 (l2cache iva neon isp )
But, then I look at u-boot, and see:
OMAP3503-GP ES2.1, CPU-OPP2, L3-165MHz, Max clock-600Mhz
So not everyone is telling the same story. Anyway, it seems we have a
problem in that the cpu_is_xxx macros are not working.
Thanks,
Cliff
commit ad0c63f1d623ea9d3e0c0521d5ce9cd522c4e1f0
Author: stanley.miao <stanley.miao@xxxxxxxxxxxxx>
Date: Mon Aug 2 14:21:40 2010 +0300
OMAP3: AM3505/3517 do not have IO wakeup capability
AM3505/3517 doesn't have IO wakeup capability, so we do not need to set
the bit OMAP3430_EN_IO and the bit OMAP3430_EN_IO_CHAIN in the register
PM_WKEN_WKUP when the system enters suspend state.
Tested on AM3517EVM and OMAP3530EVM.
Signed-off-by: Stanley.Miao <stanley.miao@xxxxxxxxxxxxx>
Acked-by: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
