From: Lucas Stach <l.stach@pengutronix.de>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
Andrzej Hajda <a.hajda@samsung.com>,
Archit Taneja <architt@codeaurora.org>,
dri-devel@lists.freedesktop.org,
Andrey Gusakov <andrey.gusakov@cogentembedded.com>
Cc: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCHv2 0/7] drm/bridge: tc358767: small fixes
Date: Wed, 09 Jan 2019 10:51:57 +0100 [thread overview]
Message-ID: <1547027517.3580.31.camel@pengutronix.de> (raw)
In-Reply-To: <73bf8df1-99ae-b8a3-76af-44563e4239b1@ti.com>
Am Mittwoch, den 09.01.2019, 11:12 +0200 schrieb Tomi Valkeinen:
> Hi Andrzej,
>
> On 09/01/19 10:22, Andrzej Hajda wrote:
> > Hi Tomi,
> >
> > On 03.01.2019 12:59, Tomi Valkeinen wrote:
> > > Hi,
> > >
> > > We have TC358867 on our board, which I believe is almost identical to
> > > TC358767. We're using it with a DP connector instead of eDP with a fixed
> > > panel.
> > >
> > > I have tested these patches only on TI's 4.14 based kernel, as
> > > unfortunately we don't have all the necessary support in mainline yet.
> > > These patches fix various bugs, but I'm still seeing at least two
> > > issues:
> > >
> > > * Sync with some videomodes is not correct, resulting in a jumping and
> > > skewed display
> > > * Link training fails sometimes
> > >
> > > I would appreciate if someone is able to verify these patches with
> > > TC358767.
> >
> >
> > Do you want to wait for testers or shall I queue this patchset?
>
> I haven't heard from anyone, so I'm ok with pushing these.
For the series:
Tested-by: Lucas Stach <l.stach@pengutronix.de>
on a device with TC358767 and a 4.20 based kernel.
Regards,
Lucas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-01-09 9:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190103120053epcas2p2901389967dc032aa2587c2a291d44c9f@epcas2p2.samsung.com>
2019-01-03 11:59 ` [PATCHv2 0/7] drm/bridge: tc358767: small fixes Tomi Valkeinen
2019-01-03 11:59 ` [PATCHv2 1/7] drm/bridge: tc358767: add bus flags Tomi Valkeinen
2019-01-03 11:59 ` [PATCHv2 2/7] drm/bridge: tc358767: add defines for DP1_SRCCTRL & PHY_2LANE Tomi Valkeinen
2019-01-03 11:59 ` [PATCHv2 3/7] drm/bridge: tc358767: fix single lane configuration Tomi Valkeinen
2019-01-03 11:59 ` [PATCHv2 4/7] drm/bridge: tc358767: fix initial DP0/1_SRCCTRL value Tomi Valkeinen
2019-01-03 11:59 ` [PATCHv2 5/7] drm/bridge: tc358767: reject modes which require too much BW Tomi Valkeinen
2019-01-03 11:59 ` [PATCHv2 6/7] drm/bridge: tc358767: fix output H/V syncs Tomi Valkeinen
2019-01-03 11:59 ` [PATCHv2 7/7] drm/bridge: tc358767: use DP connector if no panel set Tomi Valkeinen
2019-01-09 8:22 ` [PATCHv2 0/7] drm/bridge: tc358767: small fixes Andrzej Hajda
2019-01-09 9:12 ` Tomi Valkeinen
2019-01-09 9:51 ` Lucas Stach [this message]
2019-01-09 10:12 ` Andrzej Hajda
2019-01-23 12:52 ` Tomi Valkeinen
2019-01-23 14:39 ` A H
2019-01-09 14:55 ` Tomi Valkeinen
2019-01-09 14:58 ` Lucas Stach
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=1547027517.3580.31.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=andrey.gusakov@cogentembedded.com \
--cc=architt@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=tomi.valkeinen@ti.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