Devicetree
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [RFC PATCH] arm64: dts: qcom: add device tree for DB845c working in dual DSI mode
Date: Sun, 14 May 2023 18:44:57 -0700	[thread overview]
Message-ID: <20230515014457.gqbvyyr75bnvi724@ripper> (raw)
In-Reply-To: <da2d90cf-1f36-7c59-7b29-ee98ab85f960@linaro.org>

On Fri, Apr 07, 2023 at 08:09:23PM +0300, Dmitry Baryshkov wrote:
> On 07/04/2023 19:48, Bjorn Andersson wrote:
> > On Wed, Jan 18, 2023 at 08:47:53PM +0200, Dmitry Baryshkov wrote:
> > > 18 января 2023 г. 19:32:42 GMT+02:00, Bjorn Andersson <andersson@kernel.org> пишет:
> > > > On Wed, Jan 18, 2023 at 10:20:48AM +0200, Dmitry Baryshkov wrote:
> > > > > While we are testing the DB845c working in dual DSI mode (which is
> > > > > required for the 4k support), create a separate device tree using this
> > > > > configuration.
> > > > > 
> > > > 
> > > > I don't think it's right to change the DTB on your device depending on
> > > > your TV's ability to do 4k or not...
> > > > 
> > > > I ran into this problem when playing around with 4k-support on the RB3
> > > > as well a while back. I was not able to figure out a way to run the
> > > > lt9611 off two inputs for the lower resolutions and ended never posted
> > > > anything because I couldn't come up with any good solution.
> > > 
> > > 
> > > This is implemented with the latest lt9611 patchset, referenced in the patch annotation.
> > > 
> > > I posted this as an RFC with the separate dts to let people test dual DSI, DPU wide planes, etc. and to compare that with plain old single link DSI/lt9611.
> > > 
> > > > 
> > > > 
> > > > Would it be possible somehow to describe the two ports in DT, but have
> > > > the display driver use one or both depending on the number of inputs
> > > > needed by the lt9611?
> > > 
> > > This would be very problemsome. Even switching the number of lanes
> > > goes against the standard and is not supported by Linux kernel.
> > > Supporting switching the host off and on would be a real troublle.
> > > 
> > 
> > Does this imply that switching resolution in runtime is not possible for
> > any of these DSI->HDMI/DP/eDP bridges?
> > 
> > The immediate worry is that we need 4k and non-4k variants of every
> > mezzanine (unless we start doing overlays). But beyond that I still
> > don't like the fact that you need to change firmware depending on which
> > monitor/TV you're going to connect the board to. (And with the current
> > boot.img-based design, this is overly cumbersome)
> No. With the latest lt9611 driver and with the current msm/msm-next it
> should not be necessary to have a separate dtsi. I submitted this patch as
> an RFC to let people compare 2xDSI vs single-link cases. Currently I'm happy
> with the way it works, so I can probably send this as a patch to main
> sdm845-db845c.dtb.
> 
> As a background info:
> - lt9611 driver can utilize either one or two DSI links
> - drm/msm can output 4k over two DSI links in bonded mode.
> - drm/msm will still utilize two DSI links for smaller resolutions
> (switching between single and bonded DSI modes doesn't seem practical).
> - If just one DSI link is supplied, 1080p is the maximum resolution that can
> be supported.
> 

Sorry, I missed your reply earlier. If we can run the lower resolutions
off two bonded DSI I think we should make that the default
configuration - it's just that when I tried it a few years ago I had
problems getting a working output... But much has changed since then.

There is a dip switch to allow one of the DSI links to be passed onto
one of the HS-connectors, but for anyone to use that they would need a
mezzaine dts anyways, so they can unbond the DSIs there.

Regards,
Bjorn

      reply	other threads:[~2023-05-15  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18  8:20 [RFC PATCH] arm64: dts: qcom: add device tree for DB845c working in dual DSI mode Dmitry Baryshkov
2023-01-18 17:32 ` Bjorn Andersson
2023-01-18 18:47   ` Dmitry Baryshkov
2023-04-07 16:48     ` Bjorn Andersson
2023-04-07 17:09       ` Dmitry Baryshkov
2023-05-15  1:44         ` Bjorn Andersson [this message]

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=20230515014457.gqbvyyr75bnvi724@ripper \
    --to=andersson@kernel.org \
    --cc=agross@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robh+dt@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