summaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorArchit Taneja <archit@ti.com>2013-02-12 12:16:46 +0100
committerTomi Valkeinen <tomi.valkeinen@ti.com>2013-04-03 14:17:45 +0200
commita0d8dde9cbde712fad65822152d2721eec1ca656 (patch)
treee12462a19878429057245e9afc6daa46375caa0c /security
parentLinux 3.9-rc5 (diff)
downloadlinux-a0d8dde9cbde712fad65822152d2721eec1ca656.tar.xz
linux-a0d8dde9cbde712fad65822152d2721eec1ca656.zip
OMAPDSS: panels: keep platform data of all panels in a single header
Structs for platform data of omapdss panels are found in headers in the 'include/video/' path. Board files populate these structs with platform specific values, and the panel driver uses these to configure the panel. Currently, each panel has it's own header in the above path. Move all the omapdss panel platform data structs to a single header omap-panel-data.h. This is useful because: - All other omapdss panel drivers will be modified to use platform data. This would lead to a lot of panel headers usable only by omapdss. A lot of these platform data structs are trivial, and don't really need a separate header. - Platform data would be eventually removed, and platform information would be passed via device tree. Therefore, omapdss panel platform data structs are temporary, and will be easier to remove if they are all in the same header. - All board files will have to include the same header to configure a panel's platform data, that makes the board files more consistent. Signed-off-by: Archit Taneja <archit@ti.com>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions