mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Armstrong <neil.armstrong@linaro.org>
To: Marek Vasut <marex@denx.de>, Rob Clark <robdclark@gmail.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Amit Pundir <amit.pundir@linaro.org>,
	Robert Foss <rfoss@kernel.org>, Jonas Karlman <jonas@kwiboo.se>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Andrzej Hajda <andrzej.hajda@intel.com>,
	Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [PATCH] Revert "drm/bridge: lt9611: Do not generate HFP/HBP/HSA and EOT packet"
Date: Fri, 4 Aug 2023 10:30:39 +0200	[thread overview]
Message-ID: <cc854764-805c-a46a-0210-edf7dafde0d1@linaro.org> (raw)
In-Reply-To: <25f3026f-3d97-a5ac-862a-da6dc5f8d830@denx.de>

Hi Marek,

On 03/08/2023 20:10, Marek Vasut wrote:
> On 8/2/23 20:49, Rob Clark wrote:
>> On Wed, Aug 2, 2023 at 11:16 AM Dmitry Baryshkov
>> <dmitry.baryshkov@linaro.org> wrote:
>>>

<snip>

>>>
>>> Can we please end the argument, land the fix (this revert) for 6.5 and
>>> work on the solution for 6.6 or 6.7?
>>>
>>
>> Even if they were in-tree, breaking existing hw means revert and
>> try-again.  Especially as we get into later -rc's
> 
> Then just apply the revert, I don't have time to debug this right this moment, and it is anyway meaningless until I can look at the bus with DSI bus analyzer.

I'm applying it, then I'll like to find an explanation when you'll be able to run the DSI bus analyzer.

I'll be able to test for regressions on the db845c board if you require, just ping me on irc.

We should clearly define those flags actions and probably add new flags to reflect the way the qcom
dsi controller acts.

Thanks,
Neil

  reply	other threads:[~2023-08-04  8:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02  8:52 Neil Armstrong
2023-08-02  9:08 ` Dmitry Baryshkov
2023-08-04  8:27   ` Neil Armstrong
2023-08-02  9:15 ` Amit Pundir
2023-08-02 12:07 ` Marek Vasut
2023-08-02 12:28   ` Marek Vasut
2023-08-02 12:37     ` Neil Armstrong
2023-08-02 17:31       ` Marek Vasut
2023-08-02 18:12         ` Dmitry Baryshkov
2023-08-02 12:38   ` Dmitry Baryshkov
2023-08-02 17:26     ` Marek Vasut
2023-08-02 13:16   ` Dmitry Baryshkov
2023-08-02 17:29     ` Marek Vasut
2023-08-02 13:38 ` Dmitry Baryshkov
2023-08-02 17:30   ` Marek Vasut
2023-08-02 18:16     ` Dmitry Baryshkov
2023-08-02 18:45       ` Marek Vasut
2023-08-02 18:49         ` Dmitry Baryshkov
2023-08-02 19:12           ` Laurent Pinchart
2023-08-02 18:49       ` Rob Clark
2023-08-03 18:10         ` Marek Vasut
2023-08-04  8:30           ` Neil Armstrong [this message]
2023-08-04  8:30 ` Neil Armstrong

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=cc854764-805c-a46a-0210-edf7dafde0d1@linaro.org \
    --to=neil.armstrong@linaro.org \
    --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=jagan@amarulasolutions.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=quic_abhinavk@quicinc.com \
    --cc=rfoss@kernel.org \
    --cc=robdclark@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
all inboxes | Powered by JetHome®