About allocate the memory with non-secure attribute
kgene.kim at samsung.com
Fri Nov 6 02:58:39 EST 2009
In default case, the ARM CPU is in the secure state until secure state
attribute is changed.
We are developing the system MMU device driver which makes multimedia device
can use virtual address instead of physical address.
Our system MMU operates as follows;
1. The device driver requests the virtually continuous memory to the OS.
2. When OS returns the page table as a result, the system MMU receives the
pointer of page table.
3. When HW Device generates the virtual addressing transaction, system MMU
translate it into the physical address by referring page table.
4. If the secure attribute of device's transaction is not matched with the
attribute of its page table, system MMU generate the fault interrupt, and
returns bus decode error to the HW Device.
The problem is "the HW device generates the non-secure transaction, while
page table has secure attribute."
And, we don't want to make HW device generates the secure transaction.
Is there any solution to allocate the memory with non-secure attribute?
Kukjin Kim <kgene.kim at samsung.com>, Senior Engineer,
System LSI Division, SAMSUNG ELECTRONICS CO., LTD.
More information about the linux-arm-kernel