diff options
author | 2013-03-06 12:00:10 -0600 | |
---|---|---|
committer | 2013-04-03 20:13:39 -0500 | |
commit | c71f8e9bef8a3e022537361505c09f8c357ffd18 (patch) | |
tree | 0e7307933173ecd17a19b7a671729885a4d14bd9 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | ARM: OMAP2+: Convert ONENAND to retrieve GPMC settings from DT (diff) | |
download | linux-dev-c71f8e9bef8a3e022537361505c09f8c357ffd18.tar.xz linux-dev-c71f8e9bef8a3e022537361505c09f8c357ffd18.zip |
ARM: OMAP2+: Detect incorrectly aligned GPMC base address
Each GPMC chip-select can be configured to map 16MB, 32MB, 64MB or 128MB
of address space. The physical base address where a chip-select starts
is also configurable and must be aligned on a boundary that is equal to
or greater than the size of the address space mapped bt the chip-select.
When enabling a GPMC chip-select, ensure that the base address is aligned
to the appropriate boundary.
Reported-by: Mark Jackson <mpfj-list@mimc.co.uk>
Signed-off-by: Jon Hunter <jon-hunter@ti.com>
Tested-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions