Use the new generic-dpi-panel platform driver instead of the old
omap_dss_driver.

Signed-off-by: Tomi Valkeinen <[email protected]>
---
 arch/arm/mach-omap2/board-ldp.c |   22 +++++++++-------------
 1 file changed, 9 insertions(+), 13 deletions(-)

diff --git a/arch/arm/mach-omap2/board-ldp.c b/arch/arm/mach-omap2/board-ldp.c
index b12fe96..78e0470 100644
--- a/arch/arm/mach-omap2/board-ldp.c
+++ b/arch/arm/mach-omap2/board-ldp.c
@@ -206,27 +206,22 @@ static void ldp_panel_disable_lcd(struct omap_dss_device 
*dssdev)
 }
 
 static struct panel_generic_dpi_data ldp_panel_data = {
+       .display_name           = "lcd",
+       .source                 = "dpi.0",
        .name                   = "nec_nl2432dr22-11b",
+       .data_lines             = 18,
        .platform_enable        = ldp_panel_enable_lcd,
        .platform_disable       = ldp_panel_disable_lcd,
 };
 
-static struct omap_dss_device ldp_lcd_device = {
-       .name                   = "lcd",
-       .driver_name            = "generic_dpi_panel",
-       .type                   = OMAP_DISPLAY_TYPE_DPI,
-       .phy.dpi.data_lines     = 18,
-       .data                   = &ldp_panel_data,
-};
-
-static struct omap_dss_device *ldp_dss_devices[] = {
-       &ldp_lcd_device,
+static struct platform_device ldp_lcd_device = {
+       .name                   = "generic_dpi_panel",
+       .id                     = 0,
+       .dev.platform_data      = &ldp_panel_data,
 };
 
 static struct omap_dss_board_info ldp_dss_data = {
-       .num_devices    = ARRAY_SIZE(ldp_dss_devices),
-       .devices        = ldp_dss_devices,
-       .default_device = &ldp_lcd_device,
+       .default_display_name = "lcd",
 };
 
 static void __init ldp_display_init(void)
@@ -364,6 +359,7 @@ static struct omap2_hsmmc_info mmc[] __initdata = {
 
 static struct platform_device *ldp_devices[] __initdata = {
        &ldp_gpio_keys_device,
+       &ldp_lcd_device,
 };
 
 #ifdef CONFIG_OMAP_MUX
-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to