devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Chen-Yu Tsai <wens@csie.org>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Daniel Vetter <daniel.vetter@intel.com>,
	David Airlie <airlied@linux.ie>,
	devicetree <devicetree@vger.kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/4] drm/sun4i: tcon: Refactor the LVDS and panel probing
Date: Mon, 5 Oct 2020 16:18:17 +0200	[thread overview]
Message-ID: <20201005141817.rsj7d6wwnsgdrydo@gilmour.lan> (raw)
In-Reply-To: <CAGb2v64dsqavVYL4UvjWw=DzpbE-Egwso1Ma8xH3qYgS2Te9zg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]

Hi Chen-Yu,

Sorry for the delay

On Sat, Aug 29, 2020 at 02:43:53PM +0800, Chen-Yu Tsai wrote:
> > +static int sun4i_tcon_register_panel(struct drm_device *drm,
> > +                                    struct sun4i_tcon *tcon)
> > +{
> > +       struct device_node *companion;
> > +       struct device_node *remote;
> > +       struct device *dev = tcon->dev;
> > +       bool has_lvds_alt;
> > +       bool has_lvds_rst;
> > +       int ret;
> > +
> > +       /*
> > +        * If we have an LVDS panel connected to the TCON, we should
> > +        * just probe the LVDS connector. Otherwise, let's just register
> > +        * an RGB panel.
> > +        */
> > +       remote = of_graph_get_remote_node(dev->of_node, 1, 0);
> > +       if (!tcon->quirks->supports_lvds ||
> > +           !of_device_is_compatible(remote, "panel-lvds"))
> > +               return sun4i_rgb_init(drm, tcon);
> 
> Slightly related: IIRC there are a few LVDS panels supported in panel-simple
> so they don't use the panel-lvds compatible. Any idea how to deal with those?

I agree that this is an issue, I'm not entirely sure how to fix it. The
proper fix would be to have multiple output ports, one for each output
type, but given how our current binding looks like I'm not sure how we
could retro-fit that without some horror-looking code.

Maybe we can add a property on the endpoint?

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2020-10-05 14:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30  9:35 [PATCH v2 0/4] drm/sun4i: Add support for dual-link LVDS on the A20 Maxime Ripard
2020-07-30  9:35 ` [PATCH v2 1/4] drm/of: Change the prototype of drm_of_lvds_get_dual_link_pixel_order Maxime Ripard
2020-08-31 20:28   ` Laurent Pinchart
2020-09-01 13:23     ` Maxime Ripard
2020-09-02  0:10       ` Laurent Pinchart
2020-07-30  9:35 ` [PATCH v2 2/4] drm/sun4i: tcon: Refactor the LVDS and panel probing Maxime Ripard
2020-08-29  6:43   ` Chen-Yu Tsai
2020-10-05 14:18     ` Maxime Ripard [this message]
2020-10-05 14:28       ` Chen-Yu Tsai
2020-08-31 20:38   ` Laurent Pinchart
2020-07-30  9:35 ` [PATCH v2 3/4] drm/sun4i: tcon: Support the LVDS Dual-Link on the A20 Maxime Ripard
2020-08-29  6:55   ` Chen-Yu Tsai
2020-08-31 20:43   ` Laurent Pinchart
2020-07-30  9:35 ` [PATCH v2 4/4] [DO NOT MERGE] ARM: dts: sun7i: Enable LVDS Dual-Link on the Cubieboard Maxime Ripard

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=20201005141817.rsj7d6wwnsgdrydo@gilmour.lan \
    --to=maxime@cerno.tech \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=frowand.list@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=tzimmermann@suse.de \
    --cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).