diff options
| author | Gupta Pekon <pekon@ti.com> | 2013-05-31 17:31:30 +0530 |
|---|---|---|
| committer | Evan Wilson <evan@oliodevices.com> | 2014-11-29 14:43:56 -0800 |
| commit | eaf1871a1fcfa62d1bda2b6720b1e891ab811fe1 (patch) | |
| tree | 2f3f731d9d9c19f871358ecfa5758057d1e09eb6 /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | df1e67f66d719856a5e906bbd79962718d7e2618 (diff) | |
| download | olio-linux-3.10-eaf1871a1fcfa62d1bda2b6720b1e891ab811fe1.tar.xz olio-linux-3.10-eaf1871a1fcfa62d1bda2b6720b1e891ab811fe1.zip | |
ARM: OMAP2+: gpmc: get number of useable GPMC chip-selects via DT
This patch enables usage of DT property 'gpmc,num-cs' as already documented in
Documentation/devicetree/bindings/bus/ti-gpmc.txt
Though GPMC hardware supports upto 8 chip-selects, but all chip-selects may
not be available for use because:
- chip-select pin may not be bonded out at SoC device boundary.
- chip-select pin-mux may conflict with other pins usage.
- board level constrains.
gpmc,num-cs allows user to configure maximum number of GPMC chip-selects
available for use on any given platform. This ensures:
- GPMC child nodes having chip-selects within allowed range are only probed.
- And un-used GPMC chip-selects remain blocked.(may be for security reasons).
Signed-off-by: Gupta, Pekon <pekon@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions