diff options
author | 2013-02-12 15:08:09 +0530 | |
---|---|---|
committer | 2013-04-04 11:50:52 +0300 | |
commit | a05f92b70205df5927d767e9e0afecd2e5fde6d2 (patch) | |
tree | 66d90d8b92b0d846f8e3202572392a74748490ca /tools/perf/scripts/python/export-to-postgresql.py | |
parent | arm: omap: board-omap3evm: use sharp panel's gpio handling (diff) | |
download | linux-dev-a05f92b70205df5927d767e9e0afecd2e5fde6d2.tar.xz linux-dev-a05f92b70205df5927d767e9e0afecd2e5fde6d2.zip |
arm: omap: board-sdp3430: use sharp panel's gpio handling
The omap3430sdp board file currently requests gpios required by the sharp_ls dpi
panel, and provides platform_enable/disable callbacks to configure them.
These tasks have been moved to the sharp_ls panel driver itself and shouldn't
be done in the board files.
Remove the gpio requests and the platform callbacks from the board file.
Add the gpio information to panel_sharp_ls037v7dw01_data so that it's
passed to the panel driver.
Out of sharp panel's configurable pins, all apart from resb_gpio are managed by
a CPLD on the display and set to a default value. Only the configurable pin is
passed to platform data.
The backlight GPIO doesn't go directly to the sharp panel, it is used to set up
a voltage supply which goes to the LED+ pin of the panel, hence it isn't passed
to panel as platform data, and configured in the board file itself. The
backlight used to previously toggle through the platform_enable/disable
callbacks, but now it is always on. This needs to be revisited.
Signed-off-by: Archit Taneja <archit@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions