2009-08-07 17:15:50 +07:00
|
|
|
/*
|
|
|
|
* linux/drivers/video/omap2/dss/dpi.c
|
|
|
|
*
|
|
|
|
* Copyright (C) 2009 Nokia Corporation
|
|
|
|
* Author: Tomi Valkeinen <tomi.valkeinen@nokia.com>
|
|
|
|
*
|
|
|
|
* Some code and ideas taken from drivers/video/omap/ driver
|
|
|
|
* by Imre Deak.
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify it
|
|
|
|
* under the terms of the GNU General Public License version 2 as published by
|
|
|
|
* the Free Software Foundation.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful, but WITHOUT
|
|
|
|
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
|
|
|
|
* more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License along with
|
|
|
|
* this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#define DSS_SUBSYS_NAME "DPI"
|
|
|
|
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/delay.h>
|
2011-07-11 00:20:26 +07:00
|
|
|
#include <linux/export.h>
|
2010-02-04 22:03:41 +07:00
|
|
|
#include <linux/err.h>
|
2009-08-07 17:15:50 +07:00
|
|
|
#include <linux/errno.h>
|
2010-02-04 22:03:41 +07:00
|
|
|
#include <linux/platform_device.h>
|
|
|
|
#include <linux/regulator/consumer.h>
|
2012-09-28 14:03:03 +07:00
|
|
|
#include <linux/string.h>
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2011-05-11 18:05:07 +07:00
|
|
|
#include <video/omapdss.h>
|
2009-08-07 17:15:50 +07:00
|
|
|
|
|
|
|
#include "dss.h"
|
2012-08-22 13:14:06 +07:00
|
|
|
#include "dss_features.h"
|
2009-08-07 17:15:50 +07:00
|
|
|
|
|
|
|
static struct {
|
2010-02-04 22:03:41 +07:00
|
|
|
struct regulator *vdds_dsi_reg;
|
2011-05-12 18:56:26 +07:00
|
|
|
struct platform_device *dsidev;
|
2012-06-29 15:49:13 +07:00
|
|
|
|
2012-07-05 14:22:46 +07:00
|
|
|
struct mutex lock;
|
|
|
|
|
2012-08-08 15:58:54 +07:00
|
|
|
struct omap_video_timings timings;
|
2012-06-29 15:49:13 +07:00
|
|
|
struct dss_lcd_mgr_config mgr_config;
|
2012-07-06 17:00:52 +07:00
|
|
|
int data_lines;
|
2012-09-26 18:00:49 +07:00
|
|
|
|
|
|
|
struct omap_dss_output output;
|
2009-08-07 17:15:50 +07:00
|
|
|
} dpi;
|
|
|
|
|
2012-10-22 20:12:58 +07:00
|
|
|
static struct platform_device *dpi_get_dsidev(enum omap_channel channel)
|
2011-05-12 18:56:26 +07:00
|
|
|
{
|
OMAPDSS: fix TV-out issue with DSI PLL
Commit 0e8276ef75f5c7811b038d1d23b2b42c16efc5ac (OMAPDSS: DPI: always
use DSI PLL if available) made dpi.c use DSI PLL for its clock. This
works fine, for DPI, but has a nasty side effect on OMAP3:
On OMAP3 the same clock is used for DISPC fclk and LCD output. Thus,
after the above patch, DSI PLL is used for DISPC and LCD output. If
TV-out is used, the TV-out needs DISPC. And if DPI is turned off, the
DSI PLL is also turned off, disabling DISPC.
For this to work, we'd need proper DSS internal clock handling, with
refcounts, which is a non-trivial project.
This patch fixes the issue for now by disabling the use of DSI PLL for
DPI on OMAP3.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-12-13 19:21:30 +07:00
|
|
|
/*
|
|
|
|
* XXX we can't currently use DSI PLL for DPI with OMAP3, as the DSI PLL
|
|
|
|
* would also be used for DISPC fclk. Meaning, when the DPI output is
|
|
|
|
* disabled, DISPC clock will be disabled, and TV out will stop.
|
|
|
|
*/
|
|
|
|
switch (omapdss_get_version()) {
|
|
|
|
case OMAPDSS_VER_OMAP24xx:
|
|
|
|
case OMAPDSS_VER_OMAP34xx_ES1:
|
|
|
|
case OMAPDSS_VER_OMAP34xx_ES3:
|
|
|
|
case OMAPDSS_VER_OMAP3630:
|
|
|
|
case OMAPDSS_VER_AM35xx:
|
|
|
|
return NULL;
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2012-10-22 20:12:58 +07:00
|
|
|
switch (channel) {
|
|
|
|
case OMAP_DSS_CHANNEL_LCD:
|
|
|
|
return dsi_get_dsidev_from_id(0);
|
|
|
|
case OMAP_DSS_CHANNEL_LCD2:
|
|
|
|
return dsi_get_dsidev_from_id(1);
|
|
|
|
default:
|
|
|
|
return NULL;
|
|
|
|
}
|
2011-05-12 18:56:26 +07:00
|
|
|
}
|
|
|
|
|
2012-10-22 20:12:58 +07:00
|
|
|
static enum omap_dss_clk_source dpi_get_alt_clk_src(enum omap_channel channel)
|
2011-04-12 15:22:26 +07:00
|
|
|
{
|
2012-10-22 20:12:58 +07:00
|
|
|
switch (channel) {
|
|
|
|
case OMAP_DSS_CHANNEL_LCD:
|
|
|
|
return OMAP_DSS_CLK_SRC_DSI_PLL_HSDIV_DISPC;
|
|
|
|
case OMAP_DSS_CHANNEL_LCD2:
|
|
|
|
return OMAP_DSS_CLK_SRC_DSI2_PLL_HSDIV_DISPC;
|
|
|
|
default:
|
|
|
|
/* this shouldn't happen */
|
|
|
|
WARN_ON(1);
|
|
|
|
return OMAP_DSS_CLK_SRC_FCK;
|
|
|
|
}
|
2011-04-12 15:22:26 +07:00
|
|
|
}
|
|
|
|
|
2012-11-27 21:41:16 +07:00
|
|
|
static int dpi_set_dsi_clk(enum omap_channel channel,
|
2010-12-02 18:27:11 +07:00
|
|
|
unsigned long pck_req, unsigned long *fck, int *lck_div,
|
|
|
|
int *pck_div)
|
2009-08-07 17:15:50 +07:00
|
|
|
{
|
|
|
|
struct dsi_clock_info dsi_cinfo;
|
|
|
|
struct dispc_clock_info dispc_cinfo;
|
|
|
|
int r;
|
|
|
|
|
2012-06-21 11:03:55 +07:00
|
|
|
r = dsi_pll_calc_clock_div_pck(dpi.dsidev, pck_req, &dsi_cinfo,
|
|
|
|
&dispc_cinfo);
|
2009-08-07 17:15:50 +07:00
|
|
|
if (r)
|
|
|
|
return r;
|
|
|
|
|
2011-05-12 18:56:26 +07:00
|
|
|
r = dsi_pll_set_clock_div(dpi.dsidev, &dsi_cinfo);
|
2009-08-07 17:15:50 +07:00
|
|
|
if (r)
|
|
|
|
return r;
|
|
|
|
|
2012-11-27 21:41:16 +07:00
|
|
|
dss_select_lcd_clk_source(channel,
|
|
|
|
dpi_get_alt_clk_src(channel));
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2012-06-29 15:49:13 +07:00
|
|
|
dpi.mgr_config.clock_info = dispc_cinfo;
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2011-02-24 15:47:30 +07:00
|
|
|
*fck = dsi_cinfo.dsi_pll_hsdiv_dispc_clk;
|
2009-08-07 17:15:50 +07:00
|
|
|
*lck_div = dispc_cinfo.lck_div;
|
|
|
|
*pck_div = dispc_cinfo.pck_div;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
2011-04-12 15:22:26 +07:00
|
|
|
|
2012-11-27 21:41:16 +07:00
|
|
|
static int dpi_set_dispc_clk(unsigned long pck_req, unsigned long *fck,
|
|
|
|
int *lck_div, int *pck_div)
|
2009-08-07 17:15:50 +07:00
|
|
|
{
|
|
|
|
struct dss_clock_info dss_cinfo;
|
|
|
|
struct dispc_clock_info dispc_cinfo;
|
|
|
|
int r;
|
|
|
|
|
2012-06-21 11:03:55 +07:00
|
|
|
r = dss_calc_clock_div(pck_req, &dss_cinfo, &dispc_cinfo);
|
2009-08-07 17:15:50 +07:00
|
|
|
if (r)
|
|
|
|
return r;
|
|
|
|
|
|
|
|
r = dss_set_clock_div(&dss_cinfo);
|
|
|
|
if (r)
|
|
|
|
return r;
|
|
|
|
|
2012-06-29 15:49:13 +07:00
|
|
|
dpi.mgr_config.clock_info = dispc_cinfo;
|
2009-08-07 17:15:50 +07:00
|
|
|
|
|
|
|
*fck = dss_cinfo.fck;
|
|
|
|
*lck_div = dispc_cinfo.lck_div;
|
|
|
|
*pck_div = dispc_cinfo.pck_div;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2012-11-27 21:41:16 +07:00
|
|
|
static int dpi_set_mode(struct omap_overlay_manager *mgr)
|
2009-08-07 17:15:50 +07:00
|
|
|
{
|
2012-08-08 15:58:54 +07:00
|
|
|
struct omap_video_timings *t = &dpi.timings;
|
2011-04-12 15:22:26 +07:00
|
|
|
int lck_div = 0, pck_div = 0;
|
|
|
|
unsigned long fck = 0;
|
2009-08-07 17:15:50 +07:00
|
|
|
unsigned long pck;
|
|
|
|
int r = 0;
|
|
|
|
|
2012-10-22 20:03:39 +07:00
|
|
|
if (dpi.dsidev)
|
2012-11-27 21:41:16 +07:00
|
|
|
r = dpi_set_dsi_clk(mgr->id, t->pixel_clock * 1000, &fck,
|
2012-06-21 11:03:55 +07:00
|
|
|
&lck_div, &pck_div);
|
2011-04-12 15:22:26 +07:00
|
|
|
else
|
2012-11-27 21:41:16 +07:00
|
|
|
r = dpi_set_dispc_clk(t->pixel_clock * 1000, &fck,
|
2012-06-21 11:03:55 +07:00
|
|
|
&lck_div, &pck_div);
|
2009-08-07 17:15:50 +07:00
|
|
|
if (r)
|
2011-05-27 14:52:19 +07:00
|
|
|
return r;
|
2009-08-07 17:15:50 +07:00
|
|
|
|
|
|
|
pck = fck / lck_div / pck_div / 1000;
|
|
|
|
|
|
|
|
if (pck != t->pixel_clock) {
|
|
|
|
DSSWARN("Could not find exact pixel clock. "
|
|
|
|
"Requested %d kHz, got %lu kHz\n",
|
|
|
|
t->pixel_clock, pck);
|
|
|
|
|
|
|
|
t->pixel_clock = pck;
|
|
|
|
}
|
|
|
|
|
2012-09-07 19:23:38 +07:00
|
|
|
dss_mgr_set_timings(mgr, t);
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2011-05-27 14:52:19 +07:00
|
|
|
return 0;
|
2009-08-07 17:15:50 +07:00
|
|
|
}
|
|
|
|
|
2012-11-27 21:41:16 +07:00
|
|
|
static void dpi_config_lcd_manager(struct omap_overlay_manager *mgr)
|
2009-08-07 17:15:50 +07:00
|
|
|
{
|
2012-06-29 15:49:13 +07:00
|
|
|
dpi.mgr_config.io_pad_mode = DSS_IO_PAD_MODE_BYPASS;
|
2011-08-22 19:11:57 +07:00
|
|
|
|
2012-06-29 15:49:13 +07:00
|
|
|
dpi.mgr_config.stallmode = false;
|
|
|
|
dpi.mgr_config.fifohandcheck = false;
|
|
|
|
|
2012-07-06 17:00:52 +07:00
|
|
|
dpi.mgr_config.video_port_width = dpi.data_lines;
|
2012-06-29 15:49:13 +07:00
|
|
|
|
|
|
|
dpi.mgr_config.lcden_sig_polarity = 0;
|
|
|
|
|
2012-09-07 19:23:38 +07:00
|
|
|
dss_mgr_set_lcd_config(mgr, &dpi.mgr_config);
|
2009-08-07 17:15:50 +07:00
|
|
|
}
|
|
|
|
|
2010-01-12 20:12:07 +07:00
|
|
|
int omapdss_dpi_display_enable(struct omap_dss_device *dssdev)
|
2009-08-07 17:15:50 +07:00
|
|
|
{
|
2012-11-27 21:41:16 +07:00
|
|
|
struct omap_dss_output *out = &dpi.output;
|
2009-08-07 17:15:50 +07:00
|
|
|
int r;
|
|
|
|
|
2012-07-05 14:22:46 +07:00
|
|
|
mutex_lock(&dpi.lock);
|
|
|
|
|
2012-08-22 13:14:06 +07:00
|
|
|
if (dss_has_feature(FEAT_DPI_USES_VDDS_DSI) && !dpi.vdds_dsi_reg) {
|
2012-02-07 16:44:55 +07:00
|
|
|
DSSERR("no VDSS_DSI regulator\n");
|
2012-07-05 14:22:46 +07:00
|
|
|
r = -ENODEV;
|
|
|
|
goto err_no_reg;
|
2012-02-07 16:44:55 +07:00
|
|
|
}
|
|
|
|
|
2012-09-07 19:23:38 +07:00
|
|
|
if (out == NULL || out->manager == NULL) {
|
|
|
|
DSSERR("failed to enable display: no output/manager\n");
|
2012-07-05 14:22:46 +07:00
|
|
|
r = -ENODEV;
|
2012-09-07 19:23:38 +07:00
|
|
|
goto err_no_out_mgr;
|
2011-06-23 20:38:21 +07:00
|
|
|
}
|
|
|
|
|
2009-08-07 17:15:50 +07:00
|
|
|
r = omap_dss_start_device(dssdev);
|
|
|
|
if (r) {
|
|
|
|
DSSERR("failed to start device\n");
|
2011-05-27 14:52:19 +07:00
|
|
|
goto err_start_dev;
|
2009-08-07 17:15:50 +07:00
|
|
|
}
|
|
|
|
|
2012-08-22 13:14:06 +07:00
|
|
|
if (dss_has_feature(FEAT_DPI_USES_VDDS_DSI)) {
|
2010-02-04 22:03:41 +07:00
|
|
|
r = regulator_enable(dpi.vdds_dsi_reg);
|
|
|
|
if (r)
|
2011-05-27 14:52:19 +07:00
|
|
|
goto err_reg_enable;
|
2010-02-04 22:03:41 +07:00
|
|
|
}
|
|
|
|
|
2011-05-27 14:52:19 +07:00
|
|
|
r = dispc_runtime_get();
|
2009-08-07 17:15:50 +07:00
|
|
|
if (r)
|
2011-05-27 14:52:19 +07:00
|
|
|
goto err_get_dispc;
|
|
|
|
|
2012-11-27 21:41:16 +07:00
|
|
|
r = dss_dpi_select_source(out->manager->id);
|
2012-09-21 16:09:54 +07:00
|
|
|
if (r)
|
|
|
|
goto err_src_sel;
|
|
|
|
|
2012-10-22 20:03:39 +07:00
|
|
|
if (dpi.dsidev) {
|
2011-05-27 14:52:19 +07:00
|
|
|
r = dsi_runtime_get(dpi.dsidev);
|
|
|
|
if (r)
|
|
|
|
goto err_get_dsi;
|
|
|
|
|
2011-05-12 18:56:26 +07:00
|
|
|
r = dsi_pll_init(dpi.dsidev, 0, 1);
|
2011-04-12 15:22:26 +07:00
|
|
|
if (r)
|
2011-05-27 14:52:19 +07:00
|
|
|
goto err_dsi_pll_init;
|
2011-04-12 15:22:26 +07:00
|
|
|
}
|
|
|
|
|
2012-11-27 21:41:16 +07:00
|
|
|
r = dpi_set_mode(out->manager);
|
2009-08-07 17:15:50 +07:00
|
|
|
if (r)
|
2011-05-27 14:52:19 +07:00
|
|
|
goto err_set_mode;
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2012-11-27 21:41:16 +07:00
|
|
|
dpi_config_lcd_manager(out->manager);
|
2012-06-29 15:49:13 +07:00
|
|
|
|
2009-08-07 17:15:50 +07:00
|
|
|
mdelay(2);
|
|
|
|
|
2012-09-07 19:23:38 +07:00
|
|
|
r = dss_mgr_enable(out->manager);
|
2011-11-21 18:42:58 +07:00
|
|
|
if (r)
|
|
|
|
goto err_mgr_enable;
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2012-07-05 14:22:46 +07:00
|
|
|
mutex_unlock(&dpi.lock);
|
|
|
|
|
2009-08-07 17:15:50 +07:00
|
|
|
return 0;
|
|
|
|
|
2011-11-21 18:42:58 +07:00
|
|
|
err_mgr_enable:
|
2011-05-27 14:52:19 +07:00
|
|
|
err_set_mode:
|
2012-10-22 20:03:39 +07:00
|
|
|
if (dpi.dsidev)
|
2011-05-18 15:33:44 +07:00
|
|
|
dsi_pll_uninit(dpi.dsidev, true);
|
2011-05-27 14:52:19 +07:00
|
|
|
err_dsi_pll_init:
|
2012-10-22 20:03:39 +07:00
|
|
|
if (dpi.dsidev)
|
2011-05-27 14:52:19 +07:00
|
|
|
dsi_runtime_put(dpi.dsidev);
|
|
|
|
err_get_dsi:
|
2012-09-21 16:09:54 +07:00
|
|
|
err_src_sel:
|
2011-05-27 14:52:19 +07:00
|
|
|
dispc_runtime_put();
|
|
|
|
err_get_dispc:
|
2012-08-22 13:14:06 +07:00
|
|
|
if (dss_has_feature(FEAT_DPI_USES_VDDS_DSI))
|
2010-02-04 22:03:41 +07:00
|
|
|
regulator_disable(dpi.vdds_dsi_reg);
|
2011-05-27 14:52:19 +07:00
|
|
|
err_reg_enable:
|
2009-08-07 17:15:50 +07:00
|
|
|
omap_dss_stop_device(dssdev);
|
2011-05-27 14:52:19 +07:00
|
|
|
err_start_dev:
|
2012-09-07 19:23:38 +07:00
|
|
|
err_no_out_mgr:
|
2012-07-05 14:22:46 +07:00
|
|
|
err_no_reg:
|
|
|
|
mutex_unlock(&dpi.lock);
|
2009-08-07 17:15:50 +07:00
|
|
|
return r;
|
|
|
|
}
|
2010-01-12 20:12:07 +07:00
|
|
|
EXPORT_SYMBOL(omapdss_dpi_display_enable);
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2010-01-12 20:12:07 +07:00
|
|
|
void omapdss_dpi_display_disable(struct omap_dss_device *dssdev)
|
2009-08-07 17:15:50 +07:00
|
|
|
{
|
2012-11-27 21:41:16 +07:00
|
|
|
struct omap_overlay_manager *mgr = dpi.output.manager;
|
2012-09-07 19:23:38 +07:00
|
|
|
|
2012-07-05 14:22:46 +07:00
|
|
|
mutex_lock(&dpi.lock);
|
|
|
|
|
2012-09-07 19:23:38 +07:00
|
|
|
dss_mgr_disable(mgr);
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2012-10-22 20:03:39 +07:00
|
|
|
if (dpi.dsidev) {
|
OMAPDSS: hide dss_select_dispc_clk_source()
dss.c currently exposes functions to configure the dispc source clock
and lcd source clock. There are configured separately from the output
drivers.
However, there is no safe way for the output drivers to handle dispc
clock, as it's shared between the outputs. Thus, if, say, the DSI driver
sets up DSI PLL and configures both the dispc and lcd clock sources to
that DSI PLL, the resulting dispc clock could be too low for, say, HDMI.
Thus the output drivers should really only be concerned about the lcd
clock, which is what the output drivers actually use. There's lot to do
to clean up the dss clock handling, but this patch takes one step
forward and removes the use of dss_select_dispc_clk_source() from the
output drivers.
After this patch, the output drivers only configure the lcd source
clock. On omap4+ the dispc src clock is never changed from the default
PRCM source. On omap3, where the dispc and lcd clocks are actually the
same, setting the lcd clock source sets the dispc clock source.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-10-22 20:58:36 +07:00
|
|
|
dss_select_lcd_clk_source(mgr->id, OMAP_DSS_CLK_SRC_FCK);
|
2011-05-12 18:56:26 +07:00
|
|
|
dsi_pll_uninit(dpi.dsidev, true);
|
2011-05-27 14:52:19 +07:00
|
|
|
dsi_runtime_put(dpi.dsidev);
|
2011-04-12 15:22:26 +07:00
|
|
|
}
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2011-05-27 14:52:19 +07:00
|
|
|
dispc_runtime_put();
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2012-08-22 13:14:06 +07:00
|
|
|
if (dss_has_feature(FEAT_DPI_USES_VDDS_DSI))
|
2010-02-04 22:03:41 +07:00
|
|
|
regulator_disable(dpi.vdds_dsi_reg);
|
|
|
|
|
2009-08-07 17:15:50 +07:00
|
|
|
omap_dss_stop_device(dssdev);
|
2012-07-05 14:22:46 +07:00
|
|
|
|
|
|
|
mutex_unlock(&dpi.lock);
|
2009-08-07 17:15:50 +07:00
|
|
|
}
|
2010-01-12 20:12:07 +07:00
|
|
|
EXPORT_SYMBOL(omapdss_dpi_display_disable);
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2012-08-08 15:58:54 +07:00
|
|
|
void omapdss_dpi_set_timings(struct omap_dss_device *dssdev,
|
|
|
|
struct omap_video_timings *timings)
|
2009-08-07 17:15:50 +07:00
|
|
|
{
|
|
|
|
DSSDBG("dpi_set_timings\n");
|
2012-07-05 14:22:46 +07:00
|
|
|
|
|
|
|
mutex_lock(&dpi.lock);
|
|
|
|
|
2012-08-08 15:58:54 +07:00
|
|
|
dpi.timings = *timings;
|
|
|
|
|
2012-07-05 14:22:46 +07:00
|
|
|
mutex_unlock(&dpi.lock);
|
2009-08-07 17:15:50 +07:00
|
|
|
}
|
2012-08-08 15:58:54 +07:00
|
|
|
EXPORT_SYMBOL(omapdss_dpi_set_timings);
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2010-01-20 17:11:25 +07:00
|
|
|
int dpi_check_timings(struct omap_dss_device *dssdev,
|
2009-08-07 17:15:50 +07:00
|
|
|
struct omap_video_timings *timings)
|
|
|
|
{
|
|
|
|
int r;
|
2012-11-27 21:41:16 +07:00
|
|
|
struct omap_overlay_manager *mgr = dpi.output.manager;
|
2009-08-07 17:15:50 +07:00
|
|
|
int lck_div, pck_div;
|
|
|
|
unsigned long fck;
|
|
|
|
unsigned long pck;
|
2011-04-12 15:22:26 +07:00
|
|
|
struct dispc_clock_info dispc_cinfo;
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2012-10-24 17:27:02 +07:00
|
|
|
if (mgr && !dispc_mgr_timings_ok(mgr->id, timings))
|
2009-08-07 17:15:50 +07:00
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
if (timings->pixel_clock == 0)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2012-10-22 20:03:39 +07:00
|
|
|
if (dpi.dsidev) {
|
2009-08-07 17:15:50 +07:00
|
|
|
struct dsi_clock_info dsi_cinfo;
|
2012-06-21 11:03:55 +07:00
|
|
|
r = dsi_pll_calc_clock_div_pck(dpi.dsidev,
|
2009-08-07 17:15:50 +07:00
|
|
|
timings->pixel_clock * 1000,
|
|
|
|
&dsi_cinfo, &dispc_cinfo);
|
|
|
|
|
|
|
|
if (r)
|
|
|
|
return r;
|
|
|
|
|
2011-02-24 15:47:30 +07:00
|
|
|
fck = dsi_cinfo.dsi_pll_hsdiv_dispc_clk;
|
2011-04-12 15:22:26 +07:00
|
|
|
} else {
|
2009-08-07 17:15:50 +07:00
|
|
|
struct dss_clock_info dss_cinfo;
|
2012-06-21 11:03:55 +07:00
|
|
|
r = dss_calc_clock_div(timings->pixel_clock * 1000,
|
2009-08-07 17:15:50 +07:00
|
|
|
&dss_cinfo, &dispc_cinfo);
|
|
|
|
|
|
|
|
if (r)
|
|
|
|
return r;
|
|
|
|
|
|
|
|
fck = dss_cinfo.fck;
|
|
|
|
}
|
2011-04-12 15:22:26 +07:00
|
|
|
|
|
|
|
lck_div = dispc_cinfo.lck_div;
|
|
|
|
pck_div = dispc_cinfo.pck_div;
|
2009-08-07 17:15:50 +07:00
|
|
|
|
|
|
|
pck = fck / lck_div / pck_div / 1000;
|
|
|
|
|
|
|
|
timings->pixel_clock = pck;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
2010-01-20 17:11:25 +07:00
|
|
|
EXPORT_SYMBOL(dpi_check_timings);
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2012-07-06 17:00:52 +07:00
|
|
|
void omapdss_dpi_set_data_lines(struct omap_dss_device *dssdev, int data_lines)
|
|
|
|
{
|
|
|
|
mutex_lock(&dpi.lock);
|
|
|
|
|
|
|
|
dpi.data_lines = data_lines;
|
|
|
|
|
|
|
|
mutex_unlock(&dpi.lock);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(omapdss_dpi_set_data_lines);
|
|
|
|
|
2012-10-30 17:57:43 +07:00
|
|
|
static int __init dpi_verify_dsi_pll(struct platform_device *dsidev)
|
|
|
|
{
|
|
|
|
int r;
|
|
|
|
|
|
|
|
/* do initial setup with the PLL to see if it is operational */
|
|
|
|
|
|
|
|
r = dsi_runtime_get(dsidev);
|
|
|
|
if (r)
|
|
|
|
return r;
|
|
|
|
|
|
|
|
r = dsi_pll_init(dsidev, 0, 1);
|
|
|
|
if (r) {
|
|
|
|
dsi_runtime_put(dsidev);
|
|
|
|
return r;
|
|
|
|
}
|
|
|
|
|
|
|
|
dsi_pll_uninit(dsidev, true);
|
|
|
|
dsi_runtime_put(dsidev);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-02-13 16:23:54 +07:00
|
|
|
/*
|
|
|
|
* Return a hardcoded channel for the DPI output. This should work for
|
|
|
|
* current use cases, but this can be later expanded to either resolve
|
|
|
|
* the channel in some more dynamic manner, or get the channel as a user
|
|
|
|
* parameter.
|
|
|
|
*/
|
|
|
|
static enum omap_channel dpi_get_channel(void)
|
|
|
|
{
|
|
|
|
switch (omapdss_get_version()) {
|
|
|
|
case OMAPDSS_VER_OMAP24xx:
|
|
|
|
case OMAPDSS_VER_OMAP34xx_ES1:
|
|
|
|
case OMAPDSS_VER_OMAP34xx_ES3:
|
|
|
|
case OMAPDSS_VER_OMAP3630:
|
|
|
|
case OMAPDSS_VER_AM35xx:
|
|
|
|
return OMAP_DSS_CHANNEL_LCD;
|
|
|
|
|
|
|
|
case OMAPDSS_VER_OMAP4430_ES1:
|
|
|
|
case OMAPDSS_VER_OMAP4430_ES2:
|
|
|
|
case OMAPDSS_VER_OMAP4:
|
|
|
|
return OMAP_DSS_CHANNEL_LCD2;
|
|
|
|
|
|
|
|
case OMAPDSS_VER_OMAP5:
|
|
|
|
return OMAP_DSS_CHANNEL_LCD3;
|
|
|
|
|
|
|
|
default:
|
|
|
|
DSSWARN("unsupported DSS version\n");
|
|
|
|
return OMAP_DSS_CHANNEL_LCD;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2012-03-01 21:58:39 +07:00
|
|
|
static int __init dpi_init_display(struct omap_dss_device *dssdev)
|
2009-08-07 17:15:50 +07:00
|
|
|
{
|
2012-10-22 20:12:58 +07:00
|
|
|
struct platform_device *dsidev;
|
|
|
|
|
2009-08-07 17:15:50 +07:00
|
|
|
DSSDBG("init_display\n");
|
|
|
|
|
2012-08-22 13:14:06 +07:00
|
|
|
if (dss_has_feature(FEAT_DPI_USES_VDDS_DSI) &&
|
|
|
|
dpi.vdds_dsi_reg == NULL) {
|
2011-02-22 20:53:46 +07:00
|
|
|
struct regulator *vdds_dsi;
|
2009-08-07 17:15:50 +07:00
|
|
|
|
2011-02-22 20:53:46 +07:00
|
|
|
vdds_dsi = dss_get_vdds_dsi();
|
|
|
|
|
|
|
|
if (IS_ERR(vdds_dsi)) {
|
2010-02-04 22:03:41 +07:00
|
|
|
DSSERR("can't get VDDS_DSI regulator\n");
|
2011-02-22 20:53:46 +07:00
|
|
|
return PTR_ERR(vdds_dsi);
|
2010-02-04 22:03:41 +07:00
|
|
|
}
|
2011-02-22 20:53:46 +07:00
|
|
|
|
|
|
|
dpi.vdds_dsi_reg = vdds_dsi;
|
2010-02-04 22:03:41 +07:00
|
|
|
}
|
|
|
|
|
2013-02-13 16:23:54 +07:00
|
|
|
dsidev = dpi_get_dsidev(dpi.output.dispc_channel);
|
2012-10-30 17:57:43 +07:00
|
|
|
|
2012-11-12 21:52:11 +07:00
|
|
|
if (dsidev && dpi_verify_dsi_pll(dsidev)) {
|
2012-10-22 20:12:58 +07:00
|
|
|
dsidev = NULL;
|
|
|
|
DSSWARN("DSI PLL not operational\n");
|
2011-05-12 18:56:26 +07:00
|
|
|
}
|
|
|
|
|
2012-10-22 20:12:58 +07:00
|
|
|
if (dsidev)
|
|
|
|
DSSDBG("using DSI PLL for DPI clock\n");
|
|
|
|
|
|
|
|
dpi.dsidev = dsidev;
|
|
|
|
|
2009-08-07 17:15:50 +07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
static struct omap_dss_device * __init dpi_find_dssdev(struct platform_device *pdev)
|
2011-02-22 20:53:46 +07:00
|
|
|
{
|
OMAPDSS: interface drivers register their panel devices
Currently the higher level omapdss platform driver gets the list of
displays in its platform data, and uses that list to create the
omap_dss_device for each display.
With DT, the logical way to do the above is to list the displays under
each individual output, i.e. we'd have "dpi" node, under which we would
have the display that uses DPI. In other words, each output driver
handles the displays that use that particular output.
To make the current code ready for DT, this patch modifies the output
drivers so that each of them creates the display devices which use that
output. However, instead of changing the platform data to suit this
method, each output driver is passed the full list of displays, and the
drivers pick the displays that are meant for them. This allows us to
keep the old platform data, and thus we avoid the need to change the
board files.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-03-01 20:45:53 +07:00
|
|
|
struct omap_dss_board_info *pdata = pdev->dev.platform_data;
|
2012-10-29 17:40:46 +07:00
|
|
|
const char *def_disp_name = omapdss_get_default_display_name();
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
struct omap_dss_device *def_dssdev;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
def_dssdev = NULL;
|
OMAPDSS: interface drivers register their panel devices
Currently the higher level omapdss platform driver gets the list of
displays in its platform data, and uses that list to create the
omap_dss_device for each display.
With DT, the logical way to do the above is to list the displays under
each individual output, i.e. we'd have "dpi" node, under which we would
have the display that uses DPI. In other words, each output driver
handles the displays that use that particular output.
To make the current code ready for DT, this patch modifies the output
drivers so that each of them creates the display devices which use that
output. However, instead of changing the platform data to suit this
method, each output driver is passed the full list of displays, and the
drivers pick the displays that are meant for them. This allows us to
keep the old platform data, and thus we avoid the need to change the
board files.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-03-01 20:45:53 +07:00
|
|
|
|
|
|
|
for (i = 0; i < pdata->num_devices; ++i) {
|
|
|
|
struct omap_dss_device *dssdev = pdata->devices[i];
|
|
|
|
|
|
|
|
if (dssdev->type != OMAP_DISPLAY_TYPE_DPI)
|
|
|
|
continue;
|
|
|
|
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
if (def_dssdev == NULL)
|
|
|
|
def_dssdev = dssdev;
|
|
|
|
|
|
|
|
if (def_disp_name != NULL &&
|
|
|
|
strcmp(dssdev->name, def_disp_name) == 0) {
|
|
|
|
def_dssdev = dssdev;
|
|
|
|
break;
|
2012-03-01 21:58:39 +07:00
|
|
|
}
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
}
|
2012-03-01 21:58:39 +07:00
|
|
|
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
return def_dssdev;
|
|
|
|
}
|
|
|
|
|
2012-09-10 17:58:29 +07:00
|
|
|
static void __init dpi_probe_pdata(struct platform_device *dpidev)
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
{
|
2012-09-10 17:58:29 +07:00
|
|
|
struct omap_dss_device *plat_dssdev;
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
struct omap_dss_device *dssdev;
|
|
|
|
int r;
|
|
|
|
|
2012-09-10 17:58:29 +07:00
|
|
|
plat_dssdev = dpi_find_dssdev(dpidev);
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
|
2012-09-10 17:58:29 +07:00
|
|
|
if (!plat_dssdev)
|
|
|
|
return;
|
|
|
|
|
|
|
|
dssdev = dss_alloc_and_init_device(&dpidev->dev);
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
if (!dssdev)
|
|
|
|
return;
|
|
|
|
|
2012-09-10 17:58:29 +07:00
|
|
|
dss_copy_device_pdata(dssdev, plat_dssdev);
|
|
|
|
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
r = dpi_init_display(dssdev);
|
|
|
|
if (r) {
|
|
|
|
DSSERR("device %s init failed: %d\n", dssdev->name, r);
|
2012-09-10 17:58:29 +07:00
|
|
|
dss_put_device(dssdev);
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2012-12-07 17:50:08 +07:00
|
|
|
r = omapdss_output_set_device(&dpi.output, dssdev);
|
|
|
|
if (r) {
|
|
|
|
DSSERR("failed to connect output to new device: %s\n",
|
|
|
|
dssdev->name);
|
|
|
|
dss_put_device(dssdev);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2012-09-10 17:58:29 +07:00
|
|
|
r = dss_add_device(dssdev);
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
if (r) {
|
|
|
|
DSSERR("device %s register failed: %d\n", dssdev->name, r);
|
2012-12-07 17:50:08 +07:00
|
|
|
omapdss_output_unset_device(&dpi.output);
|
2012-09-10 17:58:29 +07:00
|
|
|
dss_put_device(dssdev);
|
OMAPDSS: register only one display device per output
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical switch to select the active display.
These are supported by omapdss so that we add all the possible display
devices at probe, but the displays are inactive until somebody enables
one. At this point the panel driver starts using the DSS, thus reserving
the physcal resource and excluding the other panels.
This is problematic:
- Panel drivers can't allocate their resources properly at probe(),
because the resources can be shared with other panels. Thus they can
be only reserved at enable time.
- Managing this in omapdss is confusing. It's not natural to have
child devices, which may not even exist (for example, a daughterboard
that is not connected).
Only some boards have multiple displays per output, and of those, only
very few have possibility of switching the display during runtime.
Because of the above points:
- We don't want to make omapdss and all the panel drivers more complex
just because some boards have complex setups.
- Only few boards support runtime switching, and afaik even then it's
not required. So we don't need to support runtime switching.
Thus we'll change to a model where we will have only one display device
per output and this cannot be (currently) changed at runtime. We'll
still have the possibility to select the display from multiple options
during boot with the default display option.
This patch accomplishes the above by changing how the output drivers
register the display device. Instead of registering all the devices
given from the board file, we'll only register one. If the default
display option is set, the output driver selects that display from its
displays. If the default display is not set, or the default display is
not one of the output's displays, the output driver selects the first
display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-09-06 18:29:31 +07:00
|
|
|
return;
|
OMAPDSS: interface drivers register their panel devices
Currently the higher level omapdss platform driver gets the list of
displays in its platform data, and uses that list to create the
omap_dss_device for each display.
With DT, the logical way to do the above is to list the displays under
each individual output, i.e. we'd have "dpi" node, under which we would
have the display that uses DPI. In other words, each output driver
handles the displays that use that particular output.
To make the current code ready for DT, this patch modifies the output
drivers so that each of them creates the display devices which use that
output. However, instead of changing the platform data to suit this
method, each output driver is passed the full list of displays, and the
drivers pick the displays that are meant for them. This allows us to
keep the old platform data, and thus we avoid the need to change the
board files.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-03-01 20:45:53 +07:00
|
|
|
}
|
2012-05-02 18:55:12 +07:00
|
|
|
}
|
|
|
|
|
2012-09-26 18:00:49 +07:00
|
|
|
static void __init dpi_init_output(struct platform_device *pdev)
|
|
|
|
{
|
|
|
|
struct omap_dss_output *out = &dpi.output;
|
|
|
|
|
|
|
|
out->pdev = pdev;
|
|
|
|
out->id = OMAP_DSS_OUTPUT_DPI;
|
|
|
|
out->type = OMAP_DISPLAY_TYPE_DPI;
|
2013-02-18 18:06:01 +07:00
|
|
|
out->name = "dpi.0";
|
2013-02-13 16:23:54 +07:00
|
|
|
out->dispc_channel = dpi_get_channel();
|
2012-09-26 18:00:49 +07:00
|
|
|
|
|
|
|
dss_register_output(out);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void __exit dpi_uninit_output(struct platform_device *pdev)
|
|
|
|
{
|
|
|
|
struct omap_dss_output *out = &dpi.output;
|
|
|
|
|
|
|
|
dss_unregister_output(out);
|
|
|
|
}
|
|
|
|
|
2012-05-02 18:55:12 +07:00
|
|
|
static int __init omap_dpi_probe(struct platform_device *pdev)
|
|
|
|
{
|
2012-07-05 14:22:46 +07:00
|
|
|
mutex_init(&dpi.lock);
|
|
|
|
|
2012-09-26 18:00:49 +07:00
|
|
|
dpi_init_output(pdev);
|
|
|
|
|
2012-05-02 18:55:12 +07:00
|
|
|
dpi_probe_pdata(pdev);
|
OMAPDSS: interface drivers register their panel devices
Currently the higher level omapdss platform driver gets the list of
displays in its platform data, and uses that list to create the
omap_dss_device for each display.
With DT, the logical way to do the above is to list the displays under
each individual output, i.e. we'd have "dpi" node, under which we would
have the display that uses DPI. In other words, each output driver
handles the displays that use that particular output.
To make the current code ready for DT, this patch modifies the output
drivers so that each of them creates the display devices which use that
output. However, instead of changing the platform data to suit this
method, each output driver is passed the full list of displays, and the
drivers pick the displays that are meant for them. This allows us to
keep the old platform data, and thus we avoid the need to change the
board files.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-03-01 20:45:53 +07:00
|
|
|
|
2011-02-22 20:53:46 +07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2012-02-17 22:41:13 +07:00
|
|
|
static int __exit omap_dpi_remove(struct platform_device *pdev)
|
2009-08-07 17:15:50 +07:00
|
|
|
{
|
2012-09-10 17:58:29 +07:00
|
|
|
dss_unregister_child_devices(&pdev->dev);
|
OMAPDSS: interface drivers register their panel devices
Currently the higher level omapdss platform driver gets the list of
displays in its platform data, and uses that list to create the
omap_dss_device for each display.
With DT, the logical way to do the above is to list the displays under
each individual output, i.e. we'd have "dpi" node, under which we would
have the display that uses DPI. In other words, each output driver
handles the displays that use that particular output.
To make the current code ready for DT, this patch modifies the output
drivers so that each of them creates the display devices which use that
output. However, instead of changing the platform data to suit this
method, each output driver is passed the full list of displays, and the
drivers pick the displays that are meant for them. This allows us to
keep the old platform data, and thus we avoid the need to change the
board files.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2012-03-01 20:45:53 +07:00
|
|
|
|
2012-09-26 18:00:49 +07:00
|
|
|
dpi_uninit_output(pdev);
|
|
|
|
|
2012-02-20 21:57:37 +07:00
|
|
|
return 0;
|
2009-08-07 17:15:50 +07:00
|
|
|
}
|
|
|
|
|
2012-02-20 21:57:37 +07:00
|
|
|
static struct platform_driver omap_dpi_driver = {
|
2012-02-17 22:41:13 +07:00
|
|
|
.remove = __exit_p(omap_dpi_remove),
|
2012-02-20 21:57:37 +07:00
|
|
|
.driver = {
|
|
|
|
.name = "omapdss_dpi",
|
|
|
|
.owner = THIS_MODULE,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
|
2012-02-17 22:41:13 +07:00
|
|
|
int __init dpi_init_platform_driver(void)
|
2012-02-20 21:57:37 +07:00
|
|
|
{
|
2012-03-07 17:53:38 +07:00
|
|
|
return platform_driver_probe(&omap_dpi_driver, omap_dpi_probe);
|
2012-02-20 21:57:37 +07:00
|
|
|
}
|
|
|
|
|
2012-02-17 22:41:13 +07:00
|
|
|
void __exit dpi_uninit_platform_driver(void)
|
2012-02-20 21:57:37 +07:00
|
|
|
{
|
|
|
|
platform_driver_unregister(&omap_dpi_driver);
|
|
|
|
}
|