2009-08-05 21:18:44 +08:00
|
|
|
/*
|
|
|
|
* linux/drivers/video/omap2/dss/sdi.c
|
|
|
|
*
|
|
|
|
* Copyright (C) 2009 Nokia Corporation
|
|
|
|
* Author: Tomi Valkeinen <tomi.valkeinen@nokia.com>
|
|
|
|
*
|
|
|
|
* 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 "SDI"
|
|
|
|
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <linux/err.h>
|
2010-03-17 20:35:21 +08:00
|
|
|
#include <linux/regulator/consumer.h>
|
2011-07-11 01:20:26 +08:00
|
|
|
#include <linux/export.h>
|
2012-02-20 22:57:37 +08:00
|
|
|
#include <linux/platform_device.h>
|
2012-09-28 15:03:03 +08:00
|
|
|
#include <linux/string.h>
|
2013-12-16 21:13:24 +08:00
|
|
|
#include <linux/of.h>
|
OMAPDSS: componentize omapdss
omapdss kernel module contains drivers for multiple devices, one for
each DSS submodule. The probing we have at the moment is a mess, and
doesn't give us proper deferred probing nor ensure that all the devices
are probed before omapfb/omapdrm start using omapdss.
This patch solves the mess by using the component system for DSS
submodules.
The changes to all DSS submodules (dispc, dpi, dsi, hdmi4/5, rfbi, sdi,
venc) are the same: probe & remove functions are changed to bind &
unbind, and new probe & remove functions are added which call
component_add/del.
The dss_core driver (dss.c) acts as a component master. Adding and
matching the components is simple: all dss device's child devices are
added as components.
However, we do have some dependencies between the drivers. The order in
which they should be probed is reflected by the list in core.c
(dss_output_drv_reg_funcs). The drivers are registered in that order,
which causes the components to be added in that order, which makes the
components to be bound in that order. This feels a bit fragile, and we
probably should improve the code to manage binds in random order.
However, for now, this works fine.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
2015-06-04 20:22:23 +08:00
|
|
|
#include <linux/component.h>
|
2009-08-05 21:18:44 +08:00
|
|
|
|
2016-05-27 19:40:49 +08:00
|
|
|
#include "omapdss.h"
|
2009-08-05 21:18:44 +08:00
|
|
|
#include "dss.h"
|
|
|
|
|
|
|
|
static struct {
|
2013-03-19 19:46:40 +08:00
|
|
|
struct platform_device *pdev;
|
|
|
|
|
2009-08-05 21:18:44 +08:00
|
|
|
bool update_enabled;
|
2010-03-17 20:35:21 +08:00
|
|
|
struct regulator *vdds_sdi_reg;
|
2009-08-05 21:18:44 +08:00
|
|
|
|
2012-06-29 17:03:18 +08:00
|
|
|
struct dss_lcd_mgr_config mgr_config;
|
2016-09-22 19:07:04 +08:00
|
|
|
struct videomode vm;
|
2012-07-20 19:48:49 +08:00
|
|
|
int datapairs;
|
2012-09-26 19:00:49 +08:00
|
|
|
|
OMAPDSS: combine omap_dss_output into omap_dss_device
We currently have omap_dss_device, which represents an external display
device, sometimes an external encoder, sometimes a panel. Then we have
omap_dss_output, which represents DSS's output encoder.
In the future with new display device model, we construct a video
pipeline from the display blocks. To accomplish this, all the blocks
need to be presented by the same entity.
Thus, this patch combines omap_dss_output into omap_dss_device. Some of
the fields in omap_dss_output are already found in omap_dss_device, but
some are not. This means we'll have DSS output specific fields in
omap_dss_device, which is not very nice. However, it is easier to just
keep those output specific fields there for now, and after transition to
new display device model is made, they can be cleaned up easier than
could be done now.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2013-04-19 20:09:34 +08:00
|
|
|
struct omap_dss_device output;
|
2013-12-16 21:13:24 +08:00
|
|
|
|
|
|
|
bool port_initialized;
|
2012-06-29 17:03:18 +08:00
|
|
|
} sdi;
|
2010-12-02 19:27:10 +08:00
|
|
|
|
2013-03-05 23:06:26 +08:00
|
|
|
struct sdi_clk_calc_ctx {
|
|
|
|
unsigned long pck_min, pck_max;
|
|
|
|
|
2014-01-28 14:50:47 +08:00
|
|
|
unsigned long fck;
|
2013-03-05 23:06:26 +08:00
|
|
|
struct dispc_clock_info dispc_cinfo;
|
|
|
|
};
|
|
|
|
|
|
|
|
static bool dpi_calc_dispc_cb(int lckd, int pckd, unsigned long lck,
|
|
|
|
unsigned long pck, void *data)
|
|
|
|
{
|
|
|
|
struct sdi_clk_calc_ctx *ctx = data;
|
|
|
|
|
|
|
|
ctx->dispc_cinfo.lck_div = lckd;
|
|
|
|
ctx->dispc_cinfo.pck_div = pckd;
|
|
|
|
ctx->dispc_cinfo.lck = lck;
|
|
|
|
ctx->dispc_cinfo.pck = pck;
|
|
|
|
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2013-10-31 20:44:23 +08:00
|
|
|
static bool dpi_calc_dss_cb(unsigned long fck, void *data)
|
2013-03-05 23:06:26 +08:00
|
|
|
{
|
|
|
|
struct sdi_clk_calc_ctx *ctx = data;
|
|
|
|
|
2013-10-31 20:44:23 +08:00
|
|
|
ctx->fck = fck;
|
2013-03-05 23:06:26 +08:00
|
|
|
|
|
|
|
return dispc_div_calc(fck, ctx->pck_min, ctx->pck_max,
|
|
|
|
dpi_calc_dispc_cb, ctx);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int sdi_calc_clock_div(unsigned long pclk,
|
2013-10-31 20:44:23 +08:00
|
|
|
unsigned long *fck,
|
2013-03-05 23:06:26 +08:00
|
|
|
struct dispc_clock_info *dispc_cinfo)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
struct sdi_clk_calc_ctx ctx;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* DSS fclk gives us very few possibilities, so finding a good pixel
|
|
|
|
* clock may not be possible. We try multiple times to find the clock,
|
|
|
|
* each time widening the pixel clock range we look for, up to
|
|
|
|
* +/- 1MHz.
|
|
|
|
*/
|
|
|
|
|
|
|
|
for (i = 0; i < 10; ++i) {
|
|
|
|
bool ok;
|
|
|
|
|
|
|
|
memset(&ctx, 0, sizeof(ctx));
|
|
|
|
if (pclk > 1000 * i * i * i)
|
|
|
|
ctx.pck_min = max(pclk - 1000 * i * i * i, 0lu);
|
|
|
|
else
|
|
|
|
ctx.pck_min = 0;
|
|
|
|
ctx.pck_max = pclk + 1000 * i * i * i;
|
|
|
|
|
2013-10-31 22:41:57 +08:00
|
|
|
ok = dss_div_calc(pclk, ctx.pck_min, dpi_calc_dss_cb, &ctx);
|
2013-03-05 23:06:26 +08:00
|
|
|
if (ok) {
|
2013-10-31 20:44:23 +08:00
|
|
|
*fck = ctx.fck;
|
2013-03-05 23:06:26 +08:00
|
|
|
*dispc_cinfo = ctx.dispc_cinfo;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
2012-06-29 17:03:18 +08:00
|
|
|
static void sdi_config_lcd_manager(struct omap_dss_device *dssdev)
|
2009-08-05 21:18:44 +08:00
|
|
|
{
|
2015-11-05 15:57:04 +08:00
|
|
|
enum omap_channel channel = dssdev->dispc_channel;
|
2012-09-04 14:19:30 +08:00
|
|
|
|
2012-06-29 17:03:18 +08:00
|
|
|
sdi.mgr_config.io_pad_mode = DSS_IO_PAD_MODE_BYPASS;
|
2010-12-02 19:27:10 +08:00
|
|
|
|
2012-06-29 17:03:18 +08:00
|
|
|
sdi.mgr_config.stallmode = false;
|
|
|
|
sdi.mgr_config.fifohandcheck = false;
|
|
|
|
|
|
|
|
sdi.mgr_config.video_port_width = 24;
|
|
|
|
sdi.mgr_config.lcden_sig_polarity = 1;
|
|
|
|
|
2015-11-05 15:57:04 +08:00
|
|
|
dss_mgr_set_lcd_config(channel, &sdi.mgr_config);
|
2009-08-05 21:18:44 +08:00
|
|
|
}
|
|
|
|
|
2013-05-22 18:14:37 +08:00
|
|
|
static int sdi_display_enable(struct omap_dss_device *dssdev)
|
2009-08-05 21:18:44 +08:00
|
|
|
{
|
OMAPDSS: combine omap_dss_output into omap_dss_device
We currently have omap_dss_device, which represents an external display
device, sometimes an external encoder, sometimes a panel. Then we have
omap_dss_output, which represents DSS's output encoder.
In the future with new display device model, we construct a video
pipeline from the display blocks. To accomplish this, all the blocks
need to be presented by the same entity.
Thus, this patch combines omap_dss_output into omap_dss_device. Some of
the fields in omap_dss_output are already found in omap_dss_device, but
some are not. This means we'll have DSS output specific fields in
omap_dss_device, which is not very nice. However, it is easier to just
keep those output specific fields there for now, and after transition to
new display device model is made, they can be cleaned up easier than
could be done now.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2013-04-19 20:09:34 +08:00
|
|
|
struct omap_dss_device *out = &sdi.output;
|
2015-11-05 15:57:04 +08:00
|
|
|
enum omap_channel channel = dssdev->dispc_channel;
|
2016-09-22 19:07:04 +08:00
|
|
|
struct videomode *vm = &sdi.vm;
|
2013-10-31 20:44:23 +08:00
|
|
|
unsigned long fck;
|
2009-08-05 21:18:44 +08:00
|
|
|
struct dispc_clock_info dispc_cinfo;
|
|
|
|
unsigned long pck;
|
|
|
|
int r;
|
|
|
|
|
2015-11-05 15:34:51 +08:00
|
|
|
if (!out->dispc_channel_connected) {
|
2012-09-04 14:19:30 +08:00
|
|
|
DSSERR("failed to enable display: no output/manager\n");
|
2011-06-23 21:38:21 +08:00
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
2010-03-17 20:35:21 +08:00
|
|
|
r = regulator_enable(sdi.vdds_sdi_reg);
|
|
|
|
if (r)
|
2011-05-27 15:52:19 +08:00
|
|
|
goto err_reg_enable;
|
2010-03-17 20:35:21 +08:00
|
|
|
|
2011-05-27 15:52:19 +08:00
|
|
|
r = dispc_runtime_get();
|
|
|
|
if (r)
|
|
|
|
goto err_get_dispc;
|
2009-08-05 21:18:44 +08:00
|
|
|
|
|
|
|
/* 15.5.9.1.2 */
|
2016-09-22 19:07:04 +08:00
|
|
|
vm->flags |= DISPLAY_FLAGS_PIXDATA_POSEDGE | DISPLAY_FLAGS_SYNC_POSEDGE;
|
2012-06-25 14:56:38 +08:00
|
|
|
|
2016-09-22 19:07:04 +08:00
|
|
|
r = sdi_calc_clock_div(vm->pixelclock, &fck, &dispc_cinfo);
|
2009-08-05 21:18:44 +08:00
|
|
|
if (r)
|
2011-05-27 15:52:19 +08:00
|
|
|
goto err_calc_clock_div;
|
2009-08-05 21:18:44 +08:00
|
|
|
|
2012-06-29 17:03:18 +08:00
|
|
|
sdi.mgr_config.clock_info = dispc_cinfo;
|
2009-08-05 21:18:44 +08:00
|
|
|
|
2013-04-10 19:12:14 +08:00
|
|
|
pck = fck / dispc_cinfo.lck_div / dispc_cinfo.pck_div;
|
2009-08-05 21:18:44 +08:00
|
|
|
|
2016-09-22 19:07:04 +08:00
|
|
|
if (pck != vm->pixelclock) {
|
2016-09-22 19:07:02 +08:00
|
|
|
DSSWARN("Could not find exact pixel clock. Requested %lu Hz, got %lu Hz\n",
|
2016-09-22 19:07:04 +08:00
|
|
|
vm->pixelclock, pck);
|
2009-08-05 21:18:44 +08:00
|
|
|
|
2016-09-22 19:07:04 +08:00
|
|
|
vm->pixelclock = pck;
|
2009-08-05 21:18:44 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2016-09-22 19:07:04 +08:00
|
|
|
dss_mgr_set_timings(channel, vm);
|
2009-08-05 21:18:44 +08:00
|
|
|
|
2013-10-31 20:44:23 +08:00
|
|
|
r = dss_set_fck_rate(fck);
|
2009-08-05 21:18:44 +08:00
|
|
|
if (r)
|
2011-05-27 15:52:19 +08:00
|
|
|
goto err_set_dss_clock_div;
|
2009-08-05 21:18:44 +08:00
|
|
|
|
2012-06-29 17:03:18 +08:00
|
|
|
sdi_config_lcd_manager(dssdev);
|
2009-08-05 21:18:44 +08:00
|
|
|
|
2012-08-21 14:09:47 +08:00
|
|
|
/*
|
|
|
|
* LCLK and PCLK divisors are located in shadow registers, and we
|
|
|
|
* normally write them to DISPC registers when enabling the output.
|
|
|
|
* However, SDI uses pck-free as source clock for its PLL, and pck-free
|
|
|
|
* is affected by the divisors. And as we need the PLL before enabling
|
|
|
|
* the output, we need to write the divisors early.
|
|
|
|
*
|
|
|
|
* It seems just writing to the DISPC register is enough, and we don't
|
|
|
|
* need to care about the shadow register mechanism for pck-free. The
|
|
|
|
* exact reason for this is unknown.
|
|
|
|
*/
|
2015-11-05 15:57:04 +08:00
|
|
|
dispc_mgr_set_clock_div(channel, &sdi.mgr_config.clock_info);
|
2012-07-20 19:48:49 +08:00
|
|
|
|
2012-09-11 16:28:59 +08:00
|
|
|
dss_sdi_init(sdi.datapairs);
|
2011-03-02 18:29:27 +08:00
|
|
|
r = dss_sdi_enable();
|
|
|
|
if (r)
|
2011-05-27 15:52:19 +08:00
|
|
|
goto err_sdi_enable;
|
2011-03-02 18:29:27 +08:00
|
|
|
mdelay(2);
|
2009-08-05 21:18:44 +08:00
|
|
|
|
2015-11-05 15:57:04 +08:00
|
|
|
r = dss_mgr_enable(channel);
|
2011-11-21 19:42:58 +08:00
|
|
|
if (r)
|
|
|
|
goto err_mgr_enable;
|
2009-08-05 21:18:44 +08:00
|
|
|
|
|
|
|
return 0;
|
2011-05-27 15:52:19 +08:00
|
|
|
|
2011-11-21 19:42:58 +08:00
|
|
|
err_mgr_enable:
|
|
|
|
dss_sdi_disable();
|
2011-05-27 15:52:19 +08:00
|
|
|
err_sdi_enable:
|
|
|
|
err_set_dss_clock_div:
|
|
|
|
err_calc_clock_div:
|
|
|
|
dispc_runtime_put();
|
|
|
|
err_get_dispc:
|
2010-03-17 20:35:21 +08:00
|
|
|
regulator_disable(sdi.vdds_sdi_reg);
|
2011-05-27 15:52:19 +08:00
|
|
|
err_reg_enable:
|
2009-08-05 21:18:44 +08:00
|
|
|
return r;
|
|
|
|
}
|
|
|
|
|
2013-05-22 18:14:37 +08:00
|
|
|
static void sdi_display_disable(struct omap_dss_device *dssdev)
|
2009-08-05 21:18:44 +08:00
|
|
|
{
|
2015-11-05 15:57:04 +08:00
|
|
|
enum omap_channel channel = dssdev->dispc_channel;
|
2012-09-04 14:19:30 +08:00
|
|
|
|
2015-11-05 15:57:04 +08:00
|
|
|
dss_mgr_disable(channel);
|
2009-08-05 21:18:44 +08:00
|
|
|
|
|
|
|
dss_sdi_disable();
|
|
|
|
|
2011-05-27 15:52:19 +08:00
|
|
|
dispc_runtime_put();
|
2009-08-05 21:18:44 +08:00
|
|
|
|
2010-03-17 20:35:21 +08:00
|
|
|
regulator_disable(sdi.vdds_sdi_reg);
|
2009-08-05 21:18:44 +08:00
|
|
|
}
|
|
|
|
|
2013-05-22 18:14:37 +08:00
|
|
|
static void sdi_set_timings(struct omap_dss_device *dssdev,
|
2016-09-22 19:07:04 +08:00
|
|
|
struct videomode *vm)
|
2012-07-05 19:41:12 +08:00
|
|
|
{
|
2016-09-22 19:07:04 +08:00
|
|
|
sdi.vm = *vm;
|
2012-07-05 19:41:12 +08:00
|
|
|
}
|
|
|
|
|
2013-05-24 18:19:14 +08:00
|
|
|
static void sdi_get_timings(struct omap_dss_device *dssdev,
|
2016-09-22 19:07:04 +08:00
|
|
|
struct videomode *vm)
|
2013-05-24 18:19:14 +08:00
|
|
|
{
|
2016-09-22 19:07:04 +08:00
|
|
|
*vm = sdi.vm;
|
2013-05-24 18:19:14 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static int sdi_check_timings(struct omap_dss_device *dssdev,
|
2016-09-22 19:07:04 +08:00
|
|
|
struct videomode *vm)
|
2013-05-24 18:19:14 +08:00
|
|
|
{
|
2015-11-05 15:57:04 +08:00
|
|
|
enum omap_channel channel = dssdev->dispc_channel;
|
2013-05-24 18:19:14 +08:00
|
|
|
|
2016-09-22 19:07:04 +08:00
|
|
|
if (!dispc_mgr_timings_ok(channel, vm))
|
2013-05-24 18:19:14 +08:00
|
|
|
return -EINVAL;
|
|
|
|
|
2016-09-22 19:07:04 +08:00
|
|
|
if (vm->pixelclock == 0)
|
2013-05-24 18:19:14 +08:00
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-05-22 18:14:37 +08:00
|
|
|
static void sdi_set_datapairs(struct omap_dss_device *dssdev, int datapairs)
|
2012-07-20 19:48:49 +08:00
|
|
|
{
|
|
|
|
sdi.datapairs = datapairs;
|
|
|
|
}
|
|
|
|
|
2013-05-17 16:00:15 +08:00
|
|
|
static int sdi_init_regulator(void)
|
2009-08-05 21:18:44 +08:00
|
|
|
{
|
2013-05-17 16:00:15 +08:00
|
|
|
struct regulator *vdds_sdi;
|
2009-08-05 21:18:44 +08:00
|
|
|
|
2013-05-17 16:00:15 +08:00
|
|
|
if (sdi.vdds_sdi_reg)
|
|
|
|
return 0;
|
2011-02-22 21:53:46 +08:00
|
|
|
|
2013-08-29 15:06:43 +08:00
|
|
|
vdds_sdi = devm_regulator_get(&sdi.pdev->dev, "vdds_sdi");
|
2013-05-17 16:00:15 +08:00
|
|
|
if (IS_ERR(vdds_sdi)) {
|
2013-12-19 22:15:34 +08:00
|
|
|
if (PTR_ERR(vdds_sdi) != -EPROBE_DEFER)
|
|
|
|
DSSERR("can't get VDDS_SDI regulator\n");
|
2013-08-29 15:06:43 +08:00
|
|
|
return PTR_ERR(vdds_sdi);
|
2011-02-22 21:53:46 +08:00
|
|
|
}
|
|
|
|
|
2013-05-17 16:00:15 +08:00
|
|
|
sdi.vdds_sdi_reg = vdds_sdi;
|
|
|
|
|
2009-08-05 21:18:44 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-05-24 18:19:14 +08:00
|
|
|
static int sdi_connect(struct omap_dss_device *dssdev,
|
|
|
|
struct omap_dss_device *dst)
|
|
|
|
{
|
2015-11-05 15:57:04 +08:00
|
|
|
enum omap_channel channel = dssdev->dispc_channel;
|
2013-05-24 18:19:14 +08:00
|
|
|
int r;
|
|
|
|
|
|
|
|
r = sdi_init_regulator();
|
|
|
|
if (r)
|
|
|
|
return r;
|
|
|
|
|
2015-11-05 15:57:04 +08:00
|
|
|
r = dss_mgr_connect(channel, dssdev);
|
2013-05-24 18:19:14 +08:00
|
|
|
if (r)
|
|
|
|
return r;
|
|
|
|
|
|
|
|
r = omapdss_output_set_device(dssdev, dst);
|
|
|
|
if (r) {
|
|
|
|
DSSERR("failed to connect output to new device: %s\n",
|
|
|
|
dst->name);
|
2015-11-05 15:57:04 +08:00
|
|
|
dss_mgr_disconnect(channel, dssdev);
|
2013-05-24 18:19:14 +08:00
|
|
|
return r;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void sdi_disconnect(struct omap_dss_device *dssdev,
|
|
|
|
struct omap_dss_device *dst)
|
|
|
|
{
|
2015-11-05 15:57:04 +08:00
|
|
|
enum omap_channel channel = dssdev->dispc_channel;
|
|
|
|
|
2013-07-24 18:06:54 +08:00
|
|
|
WARN_ON(dst != dssdev->dst);
|
2013-05-24 18:19:14 +08:00
|
|
|
|
2013-07-24 18:06:54 +08:00
|
|
|
if (dst != dssdev->dst)
|
2013-05-24 18:19:14 +08:00
|
|
|
return;
|
|
|
|
|
|
|
|
omapdss_output_unset_device(dssdev);
|
|
|
|
|
2015-11-05 15:57:04 +08:00
|
|
|
dss_mgr_disconnect(channel, dssdev);
|
2013-05-24 18:19:14 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static const struct omapdss_sdi_ops sdi_ops = {
|
|
|
|
.connect = sdi_connect,
|
|
|
|
.disconnect = sdi_disconnect,
|
|
|
|
|
2013-05-22 18:14:37 +08:00
|
|
|
.enable = sdi_display_enable,
|
|
|
|
.disable = sdi_display_disable,
|
2013-05-24 18:19:14 +08:00
|
|
|
|
|
|
|
.check_timings = sdi_check_timings,
|
2013-05-22 18:14:37 +08:00
|
|
|
.set_timings = sdi_set_timings,
|
2013-05-24 18:19:14 +08:00
|
|
|
.get_timings = sdi_get_timings,
|
|
|
|
|
2013-05-22 18:14:37 +08:00
|
|
|
.set_datapairs = sdi_set_datapairs,
|
2013-05-24 18:19:14 +08:00
|
|
|
};
|
|
|
|
|
2013-05-02 16:56:35 +08:00
|
|
|
static void sdi_init_output(struct platform_device *pdev)
|
2012-09-26 19:00:49 +08:00
|
|
|
{
|
OMAPDSS: combine omap_dss_output into omap_dss_device
We currently have omap_dss_device, which represents an external display
device, sometimes an external encoder, sometimes a panel. Then we have
omap_dss_output, which represents DSS's output encoder.
In the future with new display device model, we construct a video
pipeline from the display blocks. To accomplish this, all the blocks
need to be presented by the same entity.
Thus, this patch combines omap_dss_output into omap_dss_device. Some of
the fields in omap_dss_output are already found in omap_dss_device, but
some are not. This means we'll have DSS output specific fields in
omap_dss_device, which is not very nice. However, it is easier to just
keep those output specific fields there for now, and after transition to
new display device model is made, they can be cleaned up easier than
could be done now.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2013-04-19 20:09:34 +08:00
|
|
|
struct omap_dss_device *out = &sdi.output;
|
2012-09-26 19:00:49 +08:00
|
|
|
|
OMAPDSS: combine omap_dss_output into omap_dss_device
We currently have omap_dss_device, which represents an external display
device, sometimes an external encoder, sometimes a panel. Then we have
omap_dss_output, which represents DSS's output encoder.
In the future with new display device model, we construct a video
pipeline from the display blocks. To accomplish this, all the blocks
need to be presented by the same entity.
Thus, this patch combines omap_dss_output into omap_dss_device. Some of
the fields in omap_dss_output are already found in omap_dss_device, but
some are not. This means we'll have DSS output specific fields in
omap_dss_device, which is not very nice. However, it is easier to just
keep those output specific fields there for now, and after transition to
new display device model is made, they can be cleaned up easier than
could be done now.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2013-04-19 20:09:34 +08:00
|
|
|
out->dev = &pdev->dev;
|
2012-09-26 19:00:49 +08:00
|
|
|
out->id = OMAP_DSS_OUTPUT_SDI;
|
OMAPDSS: combine omap_dss_output into omap_dss_device
We currently have omap_dss_device, which represents an external display
device, sometimes an external encoder, sometimes a panel. Then we have
omap_dss_output, which represents DSS's output encoder.
In the future with new display device model, we construct a video
pipeline from the display blocks. To accomplish this, all the blocks
need to be presented by the same entity.
Thus, this patch combines omap_dss_output into omap_dss_device. Some of
the fields in omap_dss_output are already found in omap_dss_device, but
some are not. This means we'll have DSS output specific fields in
omap_dss_device, which is not very nice. However, it is easier to just
keep those output specific fields there for now, and after transition to
new display device model is made, they can be cleaned up easier than
could be done now.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2013-04-19 20:09:34 +08:00
|
|
|
out->output_type = OMAP_DISPLAY_TYPE_SDI;
|
2013-02-18 19:06:01 +08:00
|
|
|
out->name = "sdi.0";
|
2013-02-13 17:23:54 +08:00
|
|
|
out->dispc_channel = OMAP_DSS_CHANNEL_LCD;
|
2014-12-29 15:57:11 +08:00
|
|
|
/* We have SDI only on OMAP3, where it's on port 1 */
|
|
|
|
out->port_num = 1;
|
2013-05-24 18:19:14 +08:00
|
|
|
out->ops.sdi = &sdi_ops;
|
2013-05-03 16:42:18 +08:00
|
|
|
out->owner = THIS_MODULE;
|
2012-09-26 19:00:49 +08:00
|
|
|
|
2013-04-24 18:32:51 +08:00
|
|
|
omapdss_register_output(out);
|
2012-09-26 19:00:49 +08:00
|
|
|
}
|
|
|
|
|
2015-06-04 19:12:16 +08:00
|
|
|
static void sdi_uninit_output(struct platform_device *pdev)
|
2012-09-26 19:00:49 +08:00
|
|
|
{
|
OMAPDSS: combine omap_dss_output into omap_dss_device
We currently have omap_dss_device, which represents an external display
device, sometimes an external encoder, sometimes a panel. Then we have
omap_dss_output, which represents DSS's output encoder.
In the future with new display device model, we construct a video
pipeline from the display blocks. To accomplish this, all the blocks
need to be presented by the same entity.
Thus, this patch combines omap_dss_output into omap_dss_device. Some of
the fields in omap_dss_output are already found in omap_dss_device, but
some are not. This means we'll have DSS output specific fields in
omap_dss_device, which is not very nice. However, it is easier to just
keep those output specific fields there for now, and after transition to
new display device model is made, they can be cleaned up easier than
could be done now.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2013-04-19 20:09:34 +08:00
|
|
|
struct omap_dss_device *out = &sdi.output;
|
2012-09-26 19:00:49 +08:00
|
|
|
|
2013-04-24 18:32:51 +08:00
|
|
|
omapdss_unregister_output(out);
|
2012-09-26 19:00:49 +08:00
|
|
|
}
|
|
|
|
|
OMAPDSS: componentize omapdss
omapdss kernel module contains drivers for multiple devices, one for
each DSS submodule. The probing we have at the moment is a mess, and
doesn't give us proper deferred probing nor ensure that all the devices
are probed before omapfb/omapdrm start using omapdss.
This patch solves the mess by using the component system for DSS
submodules.
The changes to all DSS submodules (dispc, dpi, dsi, hdmi4/5, rfbi, sdi,
venc) are the same: probe & remove functions are changed to bind &
unbind, and new probe & remove functions are added which call
component_add/del.
The dss_core driver (dss.c) acts as a component master. Adding and
matching the components is simple: all dss device's child devices are
added as components.
However, we do have some dependencies between the drivers. The order in
which they should be probed is reflected by the list in core.c
(dss_output_drv_reg_funcs). The drivers are registered in that order,
which causes the components to be added in that order, which makes the
components to be bound in that order. This feels a bit fragile, and we
probably should improve the code to manage binds in random order.
However, for now, this works fine.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
2015-06-04 20:22:23 +08:00
|
|
|
static int sdi_bind(struct device *dev, struct device *master, void *data)
|
2012-05-02 19:55:12 +08:00
|
|
|
{
|
OMAPDSS: componentize omapdss
omapdss kernel module contains drivers for multiple devices, one for
each DSS submodule. The probing we have at the moment is a mess, and
doesn't give us proper deferred probing nor ensure that all the devices
are probed before omapfb/omapdrm start using omapdss.
This patch solves the mess by using the component system for DSS
submodules.
The changes to all DSS submodules (dispc, dpi, dsi, hdmi4/5, rfbi, sdi,
venc) are the same: probe & remove functions are changed to bind &
unbind, and new probe & remove functions are added which call
component_add/del.
The dss_core driver (dss.c) acts as a component master. Adding and
matching the components is simple: all dss device's child devices are
added as components.
However, we do have some dependencies between the drivers. The order in
which they should be probed is reflected by the list in core.c
(dss_output_drv_reg_funcs). The drivers are registered in that order,
which causes the components to be added in that order, which makes the
components to be bound in that order. This feels a bit fragile, and we
probably should improve the code to manage binds in random order.
However, for now, this works fine.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
2015-06-04 20:22:23 +08:00
|
|
|
struct platform_device *pdev = to_platform_device(dev);
|
|
|
|
|
2013-03-19 19:46:40 +08:00
|
|
|
sdi.pdev = pdev;
|
|
|
|
|
2012-09-26 19:00:49 +08:00
|
|
|
sdi_init_output(pdev);
|
|
|
|
|
2009-08-05 21:18:44 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
OMAPDSS: componentize omapdss
omapdss kernel module contains drivers for multiple devices, one for
each DSS submodule. The probing we have at the moment is a mess, and
doesn't give us proper deferred probing nor ensure that all the devices
are probed before omapfb/omapdrm start using omapdss.
This patch solves the mess by using the component system for DSS
submodules.
The changes to all DSS submodules (dispc, dpi, dsi, hdmi4/5, rfbi, sdi,
venc) are the same: probe & remove functions are changed to bind &
unbind, and new probe & remove functions are added which call
component_add/del.
The dss_core driver (dss.c) acts as a component master. Adding and
matching the components is simple: all dss device's child devices are
added as components.
However, we do have some dependencies between the drivers. The order in
which they should be probed is reflected by the list in core.c
(dss_output_drv_reg_funcs). The drivers are registered in that order,
which causes the components to be added in that order, which makes the
components to be bound in that order. This feels a bit fragile, and we
probably should improve the code to manage binds in random order.
However, for now, this works fine.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
2015-06-04 20:22:23 +08:00
|
|
|
static void sdi_unbind(struct device *dev, struct device *master, void *data)
|
2009-08-05 21:18:44 +08:00
|
|
|
{
|
OMAPDSS: componentize omapdss
omapdss kernel module contains drivers for multiple devices, one for
each DSS submodule. The probing we have at the moment is a mess, and
doesn't give us proper deferred probing nor ensure that all the devices
are probed before omapfb/omapdrm start using omapdss.
This patch solves the mess by using the component system for DSS
submodules.
The changes to all DSS submodules (dispc, dpi, dsi, hdmi4/5, rfbi, sdi,
venc) are the same: probe & remove functions are changed to bind &
unbind, and new probe & remove functions are added which call
component_add/del.
The dss_core driver (dss.c) acts as a component master. Adding and
matching the components is simple: all dss device's child devices are
added as components.
However, we do have some dependencies between the drivers. The order in
which they should be probed is reflected by the list in core.c
(dss_output_drv_reg_funcs). The drivers are registered in that order,
which causes the components to be added in that order, which makes the
components to be bound in that order. This feels a bit fragile, and we
probably should improve the code to manage binds in random order.
However, for now, this works fine.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
2015-06-04 20:22:23 +08:00
|
|
|
struct platform_device *pdev = to_platform_device(dev);
|
|
|
|
|
2012-09-26 19:00:49 +08:00
|
|
|
sdi_uninit_output(pdev);
|
OMAPDSS: componentize omapdss
omapdss kernel module contains drivers for multiple devices, one for
each DSS submodule. The probing we have at the moment is a mess, and
doesn't give us proper deferred probing nor ensure that all the devices
are probed before omapfb/omapdrm start using omapdss.
This patch solves the mess by using the component system for DSS
submodules.
The changes to all DSS submodules (dispc, dpi, dsi, hdmi4/5, rfbi, sdi,
venc) are the same: probe & remove functions are changed to bind &
unbind, and new probe & remove functions are added which call
component_add/del.
The dss_core driver (dss.c) acts as a component master. Adding and
matching the components is simple: all dss device's child devices are
added as components.
However, we do have some dependencies between the drivers. The order in
which they should be probed is reflected by the list in core.c
(dss_output_drv_reg_funcs). The drivers are registered in that order,
which causes the components to be added in that order, which makes the
components to be bound in that order. This feels a bit fragile, and we
probably should improve the code to manage binds in random order.
However, for now, this works fine.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
2015-06-04 20:22:23 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static const struct component_ops sdi_component_ops = {
|
|
|
|
.bind = sdi_bind,
|
|
|
|
.unbind = sdi_unbind,
|
|
|
|
};
|
2012-09-26 19:00:49 +08:00
|
|
|
|
OMAPDSS: componentize omapdss
omapdss kernel module contains drivers for multiple devices, one for
each DSS submodule. The probing we have at the moment is a mess, and
doesn't give us proper deferred probing nor ensure that all the devices
are probed before omapfb/omapdrm start using omapdss.
This patch solves the mess by using the component system for DSS
submodules.
The changes to all DSS submodules (dispc, dpi, dsi, hdmi4/5, rfbi, sdi,
venc) are the same: probe & remove functions are changed to bind &
unbind, and new probe & remove functions are added which call
component_add/del.
The dss_core driver (dss.c) acts as a component master. Adding and
matching the components is simple: all dss device's child devices are
added as components.
However, we do have some dependencies between the drivers. The order in
which they should be probed is reflected by the list in core.c
(dss_output_drv_reg_funcs). The drivers are registered in that order,
which causes the components to be added in that order, which makes the
components to be bound in that order. This feels a bit fragile, and we
probably should improve the code to manage binds in random order.
However, for now, this works fine.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
2015-06-04 20:22:23 +08:00
|
|
|
static int sdi_probe(struct platform_device *pdev)
|
|
|
|
{
|
|
|
|
return component_add(&pdev->dev, &sdi_component_ops);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int sdi_remove(struct platform_device *pdev)
|
|
|
|
{
|
|
|
|
component_del(&pdev->dev, &sdi_component_ops);
|
2012-02-20 22:57:37 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct platform_driver omap_sdi_driver = {
|
OMAPDSS: componentize omapdss
omapdss kernel module contains drivers for multiple devices, one for
each DSS submodule. The probing we have at the moment is a mess, and
doesn't give us proper deferred probing nor ensure that all the devices
are probed before omapfb/omapdrm start using omapdss.
This patch solves the mess by using the component system for DSS
submodules.
The changes to all DSS submodules (dispc, dpi, dsi, hdmi4/5, rfbi, sdi,
venc) are the same: probe & remove functions are changed to bind &
unbind, and new probe & remove functions are added which call
component_add/del.
The dss_core driver (dss.c) acts as a component master. Adding and
matching the components is simple: all dss device's child devices are
added as components.
However, we do have some dependencies between the drivers. The order in
which they should be probed is reflected by the list in core.c
(dss_output_drv_reg_funcs). The drivers are registered in that order,
which causes the components to be added in that order, which makes the
components to be bound in that order. This feels a bit fragile, and we
probably should improve the code to manage binds in random order.
However, for now, this works fine.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
2015-06-04 20:22:23 +08:00
|
|
|
.probe = sdi_probe,
|
|
|
|
.remove = sdi_remove,
|
2012-02-20 22:57:37 +08:00
|
|
|
.driver = {
|
|
|
|
.name = "omapdss_sdi",
|
2014-10-16 14:54:25 +08:00
|
|
|
.suppress_bind_attrs = true,
|
2012-02-20 22:57:37 +08:00
|
|
|
},
|
|
|
|
};
|
|
|
|
|
2012-02-17 23:41:13 +08:00
|
|
|
int __init sdi_init_platform_driver(void)
|
2012-02-20 22:57:37 +08:00
|
|
|
{
|
2013-05-02 16:56:35 +08:00
|
|
|
return platform_driver_register(&omap_sdi_driver);
|
2012-02-20 22:57:37 +08:00
|
|
|
}
|
|
|
|
|
2015-06-04 19:12:16 +08:00
|
|
|
void sdi_uninit_platform_driver(void)
|
2012-02-20 22:57:37 +08:00
|
|
|
{
|
|
|
|
platform_driver_unregister(&omap_sdi_driver);
|
2009-08-05 21:18:44 +08:00
|
|
|
}
|
2013-12-16 21:13:24 +08:00
|
|
|
|
2015-06-04 19:12:16 +08:00
|
|
|
int sdi_init_port(struct platform_device *pdev, struct device_node *port)
|
2013-12-16 21:13:24 +08:00
|
|
|
{
|
|
|
|
struct device_node *ep;
|
|
|
|
u32 datapairs;
|
|
|
|
int r;
|
|
|
|
|
|
|
|
ep = omapdss_of_get_next_endpoint(port, NULL);
|
|
|
|
if (!ep)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
r = of_property_read_u32(ep, "datapairs", &datapairs);
|
|
|
|
if (r) {
|
|
|
|
DSSERR("failed to parse datapairs\n");
|
|
|
|
goto err_datapairs;
|
|
|
|
}
|
|
|
|
|
|
|
|
sdi.datapairs = datapairs;
|
|
|
|
|
|
|
|
of_node_put(ep);
|
|
|
|
|
|
|
|
sdi.pdev = pdev;
|
|
|
|
|
|
|
|
sdi_init_output(pdev);
|
|
|
|
|
|
|
|
sdi.port_initialized = true;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
err_datapairs:
|
|
|
|
of_node_put(ep);
|
|
|
|
|
|
|
|
return r;
|
|
|
|
}
|
|
|
|
|
2015-06-04 19:12:16 +08:00
|
|
|
void sdi_uninit_port(struct device_node *port)
|
2013-12-16 21:13:24 +08:00
|
|
|
{
|
|
|
|
if (!sdi.port_initialized)
|
|
|
|
return;
|
|
|
|
|
|
|
|
sdi_uninit_output(sdi.pdev);
|
|
|
|
}
|