From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Robin van der Gracht <robin@protonic.nl>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v1 2/3] drm: panel-simple: Add support for the Innolux G070Y2-T02 panel
Date: Mon, 11 Oct 2021 11:01:48 +0200 [thread overview]
Message-ID: <20211011090148.GA28262@pengutronix.de> (raw)
In-Reply-To: <YWGxbKm/5r/J1Vi6@ravnborg.org>
On Sat, Oct 09, 2021 at 05:12:44PM +0200, Sam Ravnborg wrote:
> Hi Oleksij, Robin,
>
> On Thu, Sep 30, 2021 at 12:05:00PM +0200, Oleksij Rempel wrote:
> > Add compatible and timings for the Innolux G070Y2-T02 panel. It is 7"
> > WVGA (800x480) TFT LCD panel with TTL interface and a backlight unit.
> >
> > Co-Developed-by: Robin van der Gracht <robin@protonic.nl>
> > Signed-off-by: Robin van der Gracht <robin@protonic.nl>
> > Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> > ---
> > drivers/gpu/drm/panel/panel-simple.c | 16 ++++++++++++++++
> > 1 file changed, 16 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c
> > index 9b6c4e6c38a1..a03b60f6fa99 100644
> > --- a/drivers/gpu/drm/panel/panel-simple.c
> > +++ b/drivers/gpu/drm/panel/panel-simple.c
> > @@ -2524,6 +2524,19 @@ static const struct panel_desc innolux_g070y2_l01 = {
> > .connector_type = DRM_MODE_CONNECTOR_LVDS,
> > };
> >
> > +static const struct panel_desc innolux_g070y2_t02 = {
> > + .modes = &innolux_at070tn92_mode,
>
> It is suprising to see that the innolux_g070y2_t02 uses the mode
> innolux_at070tn92_mode.
> Is it on purpose?
yes.
> If yes then I would expect the changelog to say so.
>
> In most (all?) other cases the panel provide their own mode.
It works with same timing values. What is the preferred way, add own
mode or extend the changelog?
Regards,
Oleksij
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2021-10-11 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 10:04 [PATCH v1 1/3] dt-bindings: display: simple: add Innolux G070Y2-T02 panel Oleksij Rempel
2021-09-30 10:05 ` [PATCH v1 2/3] drm: panel-simple: Add support for the " Oleksij Rempel
[not found] ` <YWGxbKm/5r/J1Vi6@ravnborg.org>
2021-10-11 9:01 ` Oleksij Rempel [this message]
2021-09-30 10:05 ` [PATCH v1 3/3] panel-simple: add LOGIC Technologies LTTD800480070-L2RT panel Oleksij Rempel
2021-10-06 21:11 ` [PATCH v1 1/3] dt-bindings: display: simple: add Innolux G070Y2-T02 panel Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2021-05-18 7:15 [PATCH v1 0/3] add innolux,g070y2-t02 support for the Protonic VT7 board Oleksij Rempel
2021-05-18 7:15 ` [PATCH v1 2/3] drm: panel-simple: Add support for the Innolux G070Y2-T02 panel Oleksij Rempel
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=20211011090148.GA28262@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robin@protonic.nl \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).