From: Marek Vasut <marex@denx.de>
To: Stefano Radaelli <stefano.radaelli21@gmail.com>,
"Rob Herring (Arm)" <robh@kernel.org>
Cc: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
David Airlie <airlied@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Ripard <mripard@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel@ffwll.ch>,
"Noah J . Rosa" <noahj.rosa@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: display: bridge: ti,sn65dsi83: add burst-mode-disabled
Date: Tue, 9 Jul 2024 15:24:05 +0200 [thread overview]
Message-ID: <944ecc41-9ef7-4d9e-9d96-3c5c0cdb71b5@denx.de> (raw)
In-Reply-To: <CAK+owohBrewYFpDKjsE5iWC5OQ3p6S_9fwj7DWa1Ux2h8CXcAw@mail.gmail.com>
On 7/9/24 2:45 PM, Stefano Radaelli wrote:
> Hello everyone,
Hi,
> Thank you a lot for your prompt feedbacks.
> I'm really sorry for all the mistakes, it is the first time that I try to
> submit a patch and i thought I followed the guideline but clearly that was
> not the case.
>
> @Marek Vasut <marex@denx.de> About your question to why disabling
> burst-mode:
> - I agree with you that Burst Mode is the preferred way to send data. For
> that reason I created the new flag in a way that, if not used in dts, burst
> mode remains active by default.
> However, I decide to introduced this property because I have noticed that
> some dual-channel panels work better in non-burst mode (even if less
> efficient), and since the sn65dsi84 datasheet allows this setting, I
> thought to give this opportunity to users.
> What do you think about it?
Are there any further details, which panels behave this way ? Does your
DSI host generate correct HS clock, ones which the DSI84 expects to
receive on the DSI side ?
Such link mode properties would have to be generic properties placed in
some dsi-client.yaml file in any case, such properties are not specific
to this DSI8x bridge.
next prev parent reply other threads:[~2024-07-09 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 15:18 stefano.radaelli21
2024-07-08 15:53 ` Marek Vasut
2024-07-08 16:04 ` Krzysztof Kozlowski
2024-07-08 16:47 ` Rob Herring (Arm)
[not found] ` <CAK+owohBrewYFpDKjsE5iWC5OQ3p6S_9fwj7DWa1Ux2h8CXcAw@mail.gmail.com>
2024-07-09 13:24 ` Marek Vasut [this message]
[not found] ` <CAK+owoiQY8OYiZofyq4jj2S3Mg6ub88DF5V52JcppxhWbUsWgg@mail.gmail.com>
2024-07-09 15:00 ` Marek Vasut
[not found] ` <CAK+owogLctqu17cFEQH+258wrpfMJ4iE6iJABRu5dwxDtR21EA@mail.gmail.com>
2024-07-09 20:25 ` Marek Vasut
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=944ecc41-9ef7-4d9e-9d96-3c5c0cdb71b5@denx.de \
--to=marex@denx.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=noahj.rosa@gmail.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=stefano.radaelli21@gmail.com \
--cc=tzimmermann@suse.de \
/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®