All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Cc: linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH 3/8] drm: bridge: lvds-encoder: Add thine,thc63lvdm83d compatible string
Date: Wed, 19 Oct 2016 17:25:38 +0300	[thread overview]
Message-ID: <1476887143-24831-4-git-send-email-laurent.pinchart+renesas@ideasonboard.com> (raw)
In-Reply-To: <1476887143-24831-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

The THC63LVDM83D is a transparent LVDS encoder. Unlike dumb LVDS
encoders it can be controlled through a few pins (power down, LVDS
swing, clock edge selection) and requires power supplies. However, on
several boards where the device is used neither the control pins nor the
power supply are controllable.

To avoid developing a separate device-specific driver add a
"thine,thc63lvdm83d" compatible entry to the lvds-encoder driver. This
will allow supporting many THC63LVDM83D-based boards easily, while
allowing future development of an thc63lvdm83d driver when needed
without breaking backward compatibility.

Cc: devicetree@vger.kernel.org
Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
---
 drivers/gpu/drm/bridge/lvds-encoder.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/bridge/lvds-encoder.c b/drivers/gpu/drm/bridge/lvds-encoder.c
index 33e8025c8a6d..f3026ad82fe1 100644
--- a/drivers/gpu/drm/bridge/lvds-encoder.c
+++ b/drivers/gpu/drm/bridge/lvds-encoder.c
@@ -184,6 +184,7 @@ static int lvds_encoder_remove(struct platform_device *pdev)
 
 static const struct of_device_id lvds_encoder_match[] = {
 	{ .compatible = "lvds-encoder" },
+	{ .compatible = "thine,thc63lvdm83d" },
 	{},
 };
 MODULE_DEVICE_TABLE(of, lvds_encoder_match);
-- 
Regards,

Laurent Pinchart

  parent reply	other threads:[~2016-10-19 14:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 14:25 [PATCH 0/8] R-Car DU: Use drm bridge API Laurent Pinchart
2016-10-19 14:25 ` Laurent Pinchart
2016-10-19 14:25 ` [PATCH 1/8] drm: bridge: Add LVDS encoder driver Laurent Pinchart
2016-10-21  5:21   ` Archit Taneja
2016-10-21 10:21     ` Laurent Pinchart
2016-10-21 10:21       ` Laurent Pinchart
2016-10-26 21:32   ` Rob Herring
2016-10-26 21:32     ` Rob Herring
2016-10-19 14:25 ` [PATCH 2/8] drm: bridge: vga-dac: Add adi,adv7123 compatible string Laurent Pinchart
2016-10-21  5:13   ` Archit Taneja
2016-10-21  5:13     ` Archit Taneja
2016-10-21 10:22     ` Laurent Pinchart
2016-10-21 10:43       ` Archit Taneja
2016-10-21 10:43         ` Archit Taneja
2016-10-19 14:25 ` Laurent Pinchart [this message]
2016-10-19 14:25 ` [PATCH 4/8] drm: Add encoder_type field to the drm_bridge structure Laurent Pinchart
2016-10-20 12:15   ` Archit Taneja
2016-10-20 12:15     ` Archit Taneja
2016-10-19 14:25 ` [PATCH 5/8] drm: bridge: Set bridges' encoder type Laurent Pinchart
2016-10-19 14:25 ` [PATCH 6/8] drm: Set on-chip " Laurent Pinchart
2016-10-19 14:25   ` Laurent Pinchart
2016-10-19 14:25 ` [PATCH 7/8] drm: rcar-du: Replace manual VGA DAC implementation with DRM bridge Laurent Pinchart
2016-10-19 14:25   ` Laurent Pinchart
2016-10-19 14:25 ` [PATCH 8/8] drm: rcar-du: Initialize encoder's type based on the bridge's type Laurent Pinchart
2016-10-19 14:25   ` Laurent Pinchart
  -- strict thread matches above, loose matches on Subject: below --
2016-10-19 14:07 [PATCH 0/8] R-Car DU: Use drm bridge API Laurent Pinchart
2016-10-19 14:07 ` [PATCH 3/8] drm: bridge: lvds-encoder: Add thine,thc63lvdm83d compatible string Laurent Pinchart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1476887143-24831-4-git-send-email-laurent.pinchart+renesas@ideasonboard.com \
    --to=laurent.pinchart+renesas@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.