From: Sam Ravnborg <sam@ravnborg.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Vinay Simha B N <simhavcs@gmail.com>
Cc: Vinay Simha B N <simhavcs@gmail.com>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Jonas Karlman <jonas@kwiboo.se>, David Airlie <airlied@linux.ie>,
Neil Armstrong <narmstrong@baylibre.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
Andrzej Hajda <a.hajda@samsung.com>
Subject: Re: [PATCH v8 2/2] display/drm/bridge: TC358775 DSI/LVDS driver
Date: Tue, 11 Aug 2020 21:17:04 +0200 [thread overview]
Message-ID: <20200811191704.GA524675@ravnborg.org> (raw)
In-Reply-To: <20200811101942.GB6054@pendragon.ideasonboard.com>
Hi Vinay.
> >
> > If Laurent or others identify further things to improve we can take
> > it in-tree.
>
> Just one thing, please see below.
>
> > > > >> + d2l_write(tc->i2c, VTIM1, vtime1);
> > > > >> + d2l_write(tc->i2c, HTIM2, htime2);
> > > > >> + d2l_write(tc->i2c, VTIM2, vtime2);
> > > > >> +
> > > > >> + d2l_write(tc->i2c, VFUEN, VFUEN_EN);
> > > > >> + d2l_write(tc->i2c, SYSRST, SYS_RST_LCD);
> > > > >> + d2l_write(tc->i2c, LVPHY0, LV_PHY0_PRBS_ON(4) | LV_PHY0_ND(6));
> > > > >> +
> > > > >> + dev_dbg(tc->dev, "bus_formats %04x bpc %d\n",
> > > > >> + connector->display_info.bus_formats[0],
> > > > >> + tc->bpc);
> > > > >> + /*
> > > > >> + * Default hardware register settings of tc358775 configured
> > > > >> + * with MEDIA_BUS_FMT_RGB888_1X7X4_JEIDA jeida-24 format
> > > > >> + */
> > > > >> + if (connector->display_info.bus_formats[0] ==
> > > > >> + MEDIA_BUS_FMT_RGB888_1X7X4_SPWG) {
>
> This shouldn't come from the connector, but from the
> drm_bridge_state.output_bus_cfg.format. The drm_bridge_funcs
> .atomic_get_input_bus_fmts() operation likely needs to be implemented.
I trust you will look into this and submit a patch on top of
drm-misc-next.
Please add a proper "Fixes:" tag identifying the commit that introduced
this bug - in this case the commit introducing the driver.
Do not hesitate to reply to all if you have any questions.
We will help you if we can.
Sam
next prev parent reply other threads:[~2020-08-11 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 13:41 [PATCH v8 1/2] dt-binding: Add DSI/LVDS TC358775 bridge bindings Vinay Simha BN
2020-07-10 13:41 ` [PATCH v8 2/2] display/drm/bridge: TC358775 DSI/LVDS driver Vinay Simha BN
[not found] ` <CAGWqDJ4P9dKzGngkiEtL_X1HRjjtU17WqNFM-qiv16tXwQNZTg@mail.gmail.com>
[not found] ` <CAGWqDJ4s3x5M7dGMTxYMpDbM4NBS7kfTb6-+7Fdx8Pe=CE58fA@mail.gmail.com>
2020-08-08 21:30 ` Laurent Pinchart
2020-08-10 17:54 ` Sam Ravnborg
2020-08-11 10:19 ` Laurent Pinchart
2020-08-11 19:17 ` Sam Ravnborg [this message]
[not found] ` <CAGWqDJ7bAjDyEr03UT-mfyOuD+xkbo9BG4GyWxbiK_c74eESYw@mail.gmail.com>
2020-08-12 7:36 ` Vinay Simha B N
[not found] ` <CAGWqDJ74bveHPKXqdPhwbZjb=cXPPQLTEng4oi+dkZa-1fRz_Q@mail.gmail.com>
2020-08-10 17:38 ` [PATCH v8 1/2] dt-binding: Add DSI/LVDS TC358775 bridge bindings Sam Ravnborg
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=20200811191704.GA524675@ravnborg.org \
--to=sam@ravnborg.org \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=simhavcs@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