On Thu, Jul 10, 2014 at 10:06:07AM +0900, YoungJun Cho wrote:
> On 07/10/2014 12:22 AM, Thierry Reding wrote:
> >On Tue, Jul 08, 2014 at 09:39:38AM +0900, YoungJun Cho wrote:
> >>To support LCD I80 interface, the DSI host calls this function
> >>to notify the panel tearing effect synchronization signal to
> >>the CRTC device manager to trigger to transfer video image.
> >>
> >>Signed-off-by: YoungJun Cho <yj44.cho@xxxxxxxxxxx>
> >>Acked-by: Inki Dae <inki.dae@xxxxxxxxxxx>
> >>Acked-by: Kyungmin Park <kyungmin.park@xxxxxxxxxxx>
> >>---
> >> drivers/gpu/drm/exynos/exynos_drm_dsi.c | 11 +++++++++++
> >> include/drm/drm_mipi_dsi.h | 7 +++++++
> >> 2 files changed, 18 insertions(+)
> >>
> >>diff --git a/drivers/gpu/drm/exynos/exynos_drm_dsi.c b/drivers/gpu/drm/exynos/exynos_drm_dsi.c
> >>index dad543a..76e34ca 100644
> >>--- a/drivers/gpu/drm/exynos/exynos_drm_dsi.c
> >>+++ b/drivers/gpu/drm/exynos/exynos_drm_dsi.c
> >>@@ -24,6 +24,7 @@
> >> #include <video/mipi_display.h>
> >> #include <video/videomode.h>
> >>
> >>+#include "exynos_drm_crtc.h"
> >> #include "exynos_drm_drv.h"
> >>
> >> /* returns true iff both arguments logically differs */
> >>@@ -1041,10 +1042,20 @@ static ssize_t exynos_dsi_host_transfer(struct mipi_dsi_host *host,
> >> return (ret < 0) ? ret : xfer.rx_done;
> >> }
> >>
> >>+static void exynos_dsi_host_pass_te(struct mipi_dsi_host *host)
> >>+{
> >>+ struct exynos_dsi *dsi = host_to_dsi(host);
> >>+ struct drm_encoder *encoder = dsi->encoder;
> >>+
> >>+ if (dsi->state & DSIM_STATE_ENABLED)
> >>+ exynos_drm_crtc_te_handler(encoder->crtc);
> >>+}
> >>+
> >> static const struct mipi_dsi_host_ops exynos_dsi_ops = {
> >> .attach = exynos_dsi_host_attach,
> >> .detach = exynos_dsi_host_detach,
> >> .transfer = exynos_dsi_host_transfer,
> >>+ .pass_te = exynos_dsi_host_pass_te,
> >> };
> >>
> >> static int exynos_dsi_poweron(struct exynos_dsi *dsi)
> >>diff --git a/include/drm/drm_mipi_dsi.h b/include/drm/drm_mipi_dsi.h
> >>index 944f33f..3f21bea 100644
> >>--- a/include/drm/drm_mipi_dsi.h
> >>+++ b/include/drm/drm_mipi_dsi.h
> >>@@ -49,6 +49,12 @@ struct mipi_dsi_msg {
> >> * @detach: detach DSI device from DSI host
> >> * @transfer: send and/or receive DSI packet, return number of received bytes,
> >> * or error
> >>+ * @pass_te: call the crtc te_handler() callback from DSI host.
> >>+ * The panel generates tearing effect synchronization signal between
> >>+ * MCU and FB to display video images. And the display controller
> >>+ * should trigger to transfer video image at this signal. So the panel
> >>+ * receives the TE IRQ, then calls this function to notify it to the
> >>+ * display controller.
> >> */
> >> struct mipi_dsi_host_ops {
> >> int (*attach)(struct mipi_dsi_host *host,
> >>@@ -57,6 +63,7 @@ struct mipi_dsi_host_ops {
> >> struct mipi_dsi_device *dsi);
> >> ssize_t (*transfer)(struct mipi_dsi_host *host,
> >> struct mipi_dsi_msg *msg);
> >>+ void (*pass_te)(struct mipi_dsi_host *host);
> >
> >I've objected to this particular change before and that objection still
> >stands. I don't see how this is related to DSI. It seems like an
> >implementation detail of this particular setup and I think it should be
> >handled differently (within the Exynos DSI controller implementation
> >possibly).
> >
>
> Okay, I understand what you mean.
> As you know, this function is called by panel TE interrupt handler, so it
> could be accessed by panel.
> Do you have any good idea for panel to access exynos_drm_dsi directly
> without mipi_dis_host_ops?
I've gone through the DSI specification again and the only mention of
the tearing effect is in section 8.12 "TE Signaling in DSI". That says
the following:
A Command Mode display module has its own timing controller and
local frame buffer for display refresh. In some cases the host
processor needs to be notified of timing events on the display
module, e.g. the start of vertical blanking or similar timing
information. In a traditional parallel-bus interface like DBI-2,
a dedicated signal wire labeled TE (Tearing Effect) is provided
to convey such timing information to the host processor. In a
DSI system, the same information, with reasonably low latency,
shall be transmitted from the display module to the host
processor when requested, using the bidirectional Data Lane.
My interpretation of that is that a DSI peripheral doesn't have a
dedicated TE signal. Now the panel that you want to support here seems
to have one, so I'm wondering if maybe it isn't a DSI panel at all but
rather DBI.
The specification goes into further detail about how to perform the TE
reporting in DSI. Essentially it consists of giving the peripheral
control of the bus via a BTA and then waiting for the peripheral to
report back with the TE event.
It would really help if somebody could find a datasheet for the panel so
that we don't have to keep guessing what the actual interface is and how
it's supposed to work.
Thierry
Attachment:
pgpp0Ex2i6gaV.pgp
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
