diff options
| author | Jon Hunter <jon-hunter@ti.com> | 2013-02-20 15:53:38 -0600 |
|---|---|---|
| committer | Jon Hunter <jon-hunter@ti.com> | 2013-04-01 14:53:40 -0500 |
| commit | 9f8331562aa1fd72e80dd6037c958cb3faf4cc38 (patch) | |
| tree | d1989fd4b4ec933b36f5645948094e31d51c0e13 /arch/arm/mach-omap2/usb-tusb6010.c | |
| parent | be9f10c04fb13d32fc30d599c1971a10916a2209 (diff) | |
| download | blackbird-op-linux-9f8331562aa1fd72e80dd6037c958cb3faf4cc38.tar.gz blackbird-op-linux-9f8331562aa1fd72e80dd6037c958cb3faf4cc38.zip | |
ARM: OMAP2+: Add variable to store number of GPMC waitpins
The GPMC has wait-pin signals that can be assigned to a chip-select
to monitor the ready signal of an external device. Add a variable to
indicate the total number of wait-pins for a given device. This will
allow us to detect if the wait-pin being selected is valid or not.
When booting with device-tree read the number of wait-pins from the
device-tree blob. When device-tree is not used set the number of
wait-pins to 4 which is valid for OMAP2-5 devices. Newer devices
that have less wait-pins (such as AM335x) only support booting with
device-tree and so hard-coding the wait-pin number when not using
device-tree is fine.
Signed-off-by: Jon Hunter <jon-hunter@ti.com>
Tested-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Diffstat (limited to 'arch/arm/mach-omap2/usb-tusb6010.c')
0 files changed, 0 insertions, 0 deletions
