From: Jagan Teki <jagan@amarulasolutions.com>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: Marek Vasut <marex@denx.de>,
dri-devel@lists.freedesktop.org,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Michael Walle <michael@walle.cc>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: [PATCH 2/2] drm/bridge: lt9611: Do not generate HFP/HBP/HSA and EOT packet
Date: Wed, 5 Jul 2023 11:00:49 +0530 [thread overview]
Message-ID: <CAMty3ZBNFu=f-FS4YFN4wfmiTuk=48nna-vub1eMYwidDt+msg@mail.gmail.com> (raw)
In-Reply-To: <CAMi1Hd0TD=2z_=bcDrht3H_wiLvAFcv8Z-U_r_KUOoeMc6UMjw@mail.gmail.com>
Hi Amit,
On Wed, Jul 5, 2023 at 10:15 AM Amit Pundir <amit.pundir@linaro.org> wrote:
>
> Hi Marek,
>
> On Wed, 5 Jul 2023 at 01:48, Marek Vasut <marex@denx.de> wrote:
> >
> > Do not generate the HS front and back porch gaps, the HSA gap and
> > EOT packet, as these packets are not required. This makes the bridge
> > work with Samsung DSIM on i.MX8MM and i.MX8MP.
>
> This patch broke display on Dragonboard 845c (SDM845) devboard running
> AOSP. This is what I see
> https://people.linaro.org/~amit.pundir/db845c-userdebug/v6.5-broken-display/PXL_20230704_150156326.jpg.
> Reverting this patch fixes this regression for me.
Might be msm dsi host require proper handling on these updated
mode_flags? did they?
Thanks,
Jagan.
next prev parent reply other threads:[~2023-07-05 5:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230403221233.500485-1-marex@denx.de>
[not found] ` <20230403221233.500485-2-marex@denx.de>
2023-07-05 4:45 ` [PATCH 2/2] drm/bridge: lt9611: Do not generate HFP/HBP/HSA and EOT packet Amit Pundir
2023-07-05 5:30 ` Jagan Teki [this message]
2023-07-05 5:39 ` Dmitry Baryshkov
2023-07-05 5:46 ` Jagan Teki
2023-07-05 7:31 ` Marek Vasut
2023-07-06 9:20 ` Amit Pundir
2023-07-07 7:18 ` Neil Armstrong
2023-07-07 8:47 ` Neil Armstrong
2023-07-08 15:40 ` Marek Vasut
2023-07-08 15:53 ` Dmitry Baryshkov
2023-07-08 19:39 ` Marek Vasut
2023-07-08 19:40 ` Dmitry Baryshkov
2023-07-08 19:47 ` Marek Vasut
2023-07-09 1:03 ` Abhinav Kumar
2023-07-12 17:41 ` Marek Vasut
2023-07-13 18:09 ` Abhinav Kumar
2023-07-13 18:28 ` Marek Vasut
2023-07-13 18:34 ` Abhinav Kumar
2023-07-14 6:11 ` Amit Pundir
2023-07-26 10:09 ` Linux regression tracking (Thorsten Leemhuis)
2023-08-02 8:39 ` neil.armstrong
2023-08-02 12:25 ` Marek Vasut
2023-08-02 13:08 ` neil.armstrong
2023-08-02 17:25 ` Marek Vasut
2023-08-02 17:49 ` Abhinav Kumar
2023-08-02 18:46 ` Marek Vasut
2023-07-13 18:37 ` Jagan Teki
2023-07-08 14:08 ` Linux regression tracking (Thorsten Leemhuis)
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='CAMty3ZBNFu=f-FS4YFN4wfmiTuk=48nna-vub1eMYwidDt+msg@mail.gmail.com' \
--to=jagan@amarulasolutions.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=amit.pundir@linaro.org \
--cc=andrzej.hajda@intel.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marex@denx.de \
--cc=michael@walle.cc \
--cc=neil.armstrong@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=rfoss@kernel.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).