From: Boris Brezillon <boris.brezillon@collabora.com>
To: Nicolas.Ferre@microchip.com
Cc: alexandre.belloni@bootlin.com, narmstrong@baylibre.com,
agx@sigxcpu.org, dri-devel@lists.freedesktop.org,
paul@crapouillou.net, thierry.reding@gmail.com,
laurent.pinchart@ideasonboard.com, sam@ravnborg.org,
stefan@olimex.com, Tudor.Ambarus@microchip.com,
Ludovic.Desroches@microchip.com, tomi.valkeinen@ti.com,
jagan@amarulasolutions.com, robert.chiras@nxp.com,
alexandre.torgue@st.com, jonas@kwiboo.se, jsarha@ti.com,
vincent.abriou@st.com, jernej.skrabec@siol.net, kernel@puri.sm,
philippe.cornu@st.com, yannick.fertre@st.com,
kieran.bingham+renesas@ideasonboard.com,
mcoquelin.stm32@gmail.com, Claudiu.Beznea@microchip.com
Subject: Re: [PATCH 1/2] drm/panel: Add and fill drm_panel type field
Date: Fri, 23 Aug 2019 13:26:18 +0200 [thread overview]
Message-ID: <20190823132618.18523da8@collabora.com> (raw)
In-Reply-To: <01887051-7cf7-cf52-65d1-85d60c3dd02c@microchip.com>
On Fri, 23 Aug 2019 07:30:07 +0000
<Nicolas.Ferre@microchip.com> wrote:
> Hi Laurent,
>
> On 23/08/2019 at 03:40, Laurent Pinchart wrote:
> > Add a type field to the drm_panel structure to report the panel type,
> > using DRM_MODE_CONNECTOR_* macros (the values that make sense are LVDS,
> > eDP, DSI and DPI). This will be used to initialise the corresponding
> > connector type.
>
> With Microchip/Atmel driver, we mainly (only) use the "Unknown" type of
> connector because our hardware simply uses RGB wires in parallel.
>
> Should we move to another connector type (maybe now that it's created
> and it was not, back when we chose the "Unknown" one)?
I confirm, DRM_MODE_ENCODER_DPI was not defined when I switched from
_LVDS (which was wrong) to _Unknown.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-08-23 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 1:40 [PATCH 1/2] drm/panel: Add and fill drm_panel type field Laurent Pinchart
2019-08-23 1:40 ` [PATCH 2/2] drm/bridge: panel: Use drm_panel.type instead of explicit connector_type Laurent Pinchart
2019-08-23 10:04 ` Linus Walleij
2019-08-23 4:49 ` [PATCH 1/2] drm/panel: Add and fill drm_panel type field Sam Ravnborg
2019-08-23 11:28 ` Laurent Pinchart
2019-08-23 7:30 ` Nicolas.Ferre
2019-08-23 11:10 ` Laurent Pinchart
2019-08-23 11:26 ` Boris Brezillon [this message]
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=20190823132618.18523da8@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=agx@sigxcpu.org \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@st.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=jsarha@ti.com \
--cc=kernel@puri.sm \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=narmstrong@baylibre.com \
--cc=paul@crapouillou.net \
--cc=philippe.cornu@st.com \
--cc=robert.chiras@nxp.com \
--cc=sam@ravnborg.org \
--cc=stefan@olimex.com \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ti.com \
--cc=vincent.abriou@st.com \
--cc=yannick.fertre@st.com \
/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