Albert Aribaud:
To make this affect only some CPUs or even boards, you can define and use a weak function which would handle filling the page-table; the weak, default, function would fill table[0] like others, while OMAP5 would have a strong version which would clear table[0].
Hi Albert,
Thank you very much for your comments.
Here is "v2" of the patch, reworked to follow your advice. Comments are welcome. I think it is now cleaner to split it in two patches:
[PATCH 1/2] ARM: cache: introduce weak arm_setup_identity_mapping [PATCH 2/2] ARM: OMAP5: redefine arm_setup_identity_mapping
I picked the 'arm_setup_identity_mapping' name more or less arbitrarily, please advise if not.
I verified this patch series on an OMAP5 HS device (with security) and on a GP device (without security), and both work for me.
Best regards,
V.