From: "Roman Beranek" <romanberanek@icloud.com>
To: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
"Maxime Ripard" <maxime@cerno.tech>
Cc: "Frank Oltmanns" <frank@oltmanns.dev>,
"Chen-Yu Tsai" <wens@csie.org>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Samuel Holland" <samuel@sholland.org>,
<dri-devel@lists.freedesktop.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-sunxi@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<icenowy@aosc.io>
Subject: Re: [PATCH] drm/sun4i: uncouple DSI dotclock divider from TCON0_DCLK_REG
Date: Wed, 12 Apr 2023 03:22:59 +0200 [thread overview]
Message-ID: <CRUDUEL17ER4.1R8WRNNB5CJ35@void.crly.cz> (raw)
In-Reply-To: <2219295.iZASKD2KPV@jernej-laptop>
On Sat Apr 8, 2023 at 9:07 AM CEST, Jernej Škrabec wrote:
> Dne sreda, 05. april 2023 ob 14:34:11 CEST je Roman Beranek napisal(a):
> > While simply forbidding the video0-2x mux option seems
> > to me as the right way to go because there's not much use for it with
> > non-DSI interfaces either besides the opportunity to power pll-mipi
> > down, I'd like to run by you first.
>
> It's been a long time since I looked at A64 HDMI clocks, but IIRC, pll-video0
> is the only useful source for HDMI PHY (as opposed to HDMI controller.)
> So question remains how to properly support both displays at the same time.
>
Correct.
> Have you ever tried to make HDMI and DSI work at the same time? This is one of
> issues of the PinePhone IIUC.
>
Yes, I have. Prusa3D's SL1 printer, on which I previously worked on,
uses both outputs simultaneously. I had encountered the same reparenting
problem back then but since I hadn't been able to identify it,
I resorted to fiddling with the DSI pixelclock until it worked.
DSI & HDMI co-existence is yet another reasoni though for forbidding
the pll-video-2x parent. megi's kernel includes Mr. Zheng's commit which
does the same.
<https://github.com/megous/linux/commit/7374d57>
Best wishes
Roman Beranek
WARNING: multiple messages have this Message-ID (diff)
From: "Roman Beranek" <romanberanek@icloud.com>
To: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
"Maxime Ripard" <maxime@cerno.tech>
Cc: "Frank Oltmanns" <frank@oltmanns.dev>,
"Chen-Yu Tsai" <wens@csie.org>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Samuel Holland" <samuel@sholland.org>,
<dri-devel@lists.freedesktop.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-sunxi@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<icenowy@aosc.io>
Subject: Re: [PATCH] drm/sun4i: uncouple DSI dotclock divider from TCON0_DCLK_REG
Date: Wed, 12 Apr 2023 03:22:59 +0200 [thread overview]
Message-ID: <CRUDUEL17ER4.1R8WRNNB5CJ35@void.crly.cz> (raw)
In-Reply-To: <2219295.iZASKD2KPV@jernej-laptop>
On Sat Apr 8, 2023 at 9:07 AM CEST, Jernej Škrabec wrote:
> Dne sreda, 05. april 2023 ob 14:34:11 CEST je Roman Beranek napisal(a):
> > While simply forbidding the video0-2x mux option seems
> > to me as the right way to go because there's not much use for it with
> > non-DSI interfaces either besides the opportunity to power pll-mipi
> > down, I'd like to run by you first.
>
> It's been a long time since I looked at A64 HDMI clocks, but IIRC, pll-video0
> is the only useful source for HDMI PHY (as opposed to HDMI controller.)
> So question remains how to properly support both displays at the same time.
>
Correct.
> Have you ever tried to make HDMI and DSI work at the same time? This is one of
> issues of the PinePhone IIUC.
>
Yes, I have. Prusa3D's SL1 printer, on which I previously worked on,
uses both outputs simultaneously. I had encountered the same reparenting
problem back then but since I hadn't been able to identify it,
I resorted to fiddling with the DSI pixelclock until it worked.
DSI & HDMI co-existence is yet another reasoni though for forbidding
the pll-video-2x parent. megi's kernel includes Mr. Zheng's commit which
does the same.
<https://github.com/megous/linux/commit/7374d57>
Best wishes
Roman Beranek
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Roman Beranek" <romanberanek@icloud.com>
To: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
"Maxime Ripard" <maxime@cerno.tech>
Cc: Samuel Holland <samuel@sholland.org>,
Frank Oltmanns <frank@oltmanns.dev>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Chen-Yu Tsai <wens@csie.org>,
linux-sunxi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, icenowy@aosc.io
Subject: Re: [PATCH] drm/sun4i: uncouple DSI dotclock divider from TCON0_DCLK_REG
Date: Wed, 12 Apr 2023 03:22:59 +0200 [thread overview]
Message-ID: <CRUDUEL17ER4.1R8WRNNB5CJ35@void.crly.cz> (raw)
In-Reply-To: <2219295.iZASKD2KPV@jernej-laptop>
On Sat Apr 8, 2023 at 9:07 AM CEST, Jernej Škrabec wrote:
> Dne sreda, 05. april 2023 ob 14:34:11 CEST je Roman Beranek napisal(a):
> > While simply forbidding the video0-2x mux option seems
> > to me as the right way to go because there's not much use for it with
> > non-DSI interfaces either besides the opportunity to power pll-mipi
> > down, I'd like to run by you first.
>
> It's been a long time since I looked at A64 HDMI clocks, but IIRC, pll-video0
> is the only useful source for HDMI PHY (as opposed to HDMI controller.)
> So question remains how to properly support both displays at the same time.
>
Correct.
> Have you ever tried to make HDMI and DSI work at the same time? This is one of
> issues of the PinePhone IIUC.
>
Yes, I have. Prusa3D's SL1 printer, on which I previously worked on,
uses both outputs simultaneously. I had encountered the same reparenting
problem back then but since I hadn't been able to identify it,
I resorted to fiddling with the DSI pixelclock until it worked.
DSI & HDMI co-existence is yet another reasoni though for forbidding
the pll-video-2x parent. megi's kernel includes Mr. Zheng's commit which
does the same.
<https://github.com/megous/linux/commit/7374d57>
Best wishes
Roman Beranek
next prev parent reply other threads:[~2023-04-12 1:23 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 16:16 [PATCH] drm/sun4i: uncouple DSI dotclock divider from TCON0_DCLK_REG Roman Beranek
2023-03-20 16:16 ` Roman Beranek
2023-03-20 16:16 ` Roman Beranek
2023-03-21 14:56 ` Maxime Ripard
2023-03-21 14:56 ` Maxime Ripard
2023-03-21 14:56 ` Maxime Ripard
2023-03-21 16:50 ` Roman Beranek
2023-03-21 16:50 ` Roman Beranek
2023-03-21 16:50 ` Roman Beranek
2023-03-21 20:53 ` Roman Beranek
2023-03-21 20:53 ` Roman Beranek
2023-03-21 20:53 ` Roman Beranek
2023-03-27 20:21 ` Maxime Ripard
2023-03-27 20:21 ` Maxime Ripard
2023-03-27 20:21 ` Maxime Ripard
2023-03-25 11:40 ` Frank Oltmanns
2023-03-25 11:40 ` Frank Oltmanns
2023-03-25 11:40 ` Frank Oltmanns
2023-03-27 20:20 ` Maxime Ripard
2023-03-27 20:20 ` Maxime Ripard
2023-03-27 20:20 ` Maxime Ripard
2023-03-27 23:48 ` Roman Beranek
2023-03-27 23:48 ` Roman Beranek
2023-03-27 23:48 ` Roman Beranek
2023-03-29 19:58 ` Maxime Ripard
2023-03-29 19:58 ` Maxime Ripard
2023-03-29 19:58 ` Maxime Ripard
2023-03-30 4:45 ` Frank Oltmanns
2023-03-30 4:45 ` Frank Oltmanns
2023-03-30 4:45 ` Frank Oltmanns
2023-03-31 5:36 ` Roman Beranek
2023-03-31 5:36 ` Roman Beranek
2023-03-31 5:36 ` Roman Beranek
2023-04-05 12:34 ` Roman Beranek
2023-04-05 12:34 ` Roman Beranek
2023-04-05 12:34 ` Roman Beranek
2023-04-05 15:03 ` Maxime Ripard
2023-04-05 15:03 ` Maxime Ripard
2023-04-05 15:03 ` Maxime Ripard
2023-04-12 7:14 ` Roman Beranek
2023-04-12 7:14 ` Roman Beranek
2023-04-12 7:14 ` Roman Beranek
2023-04-12 14:09 ` Maxime Ripard
2023-04-12 14:09 ` Maxime Ripard
2023-04-12 14:09 ` Maxime Ripard
2023-04-08 7:07 ` Jernej Škrabec
2023-04-08 7:07 ` Jernej Škrabec
2023-04-08 7:07 ` Jernej Škrabec
2023-04-12 1:22 ` Roman Beranek [this message]
2023-04-12 1:22 ` Roman Beranek
2023-04-12 1:22 ` Roman Beranek
2023-03-28 19:28 ` Frank Oltmanns
2023-03-28 19:28 ` Frank Oltmanns
2023-03-28 19:28 ` Frank Oltmanns
2023-03-29 19:56 ` Maxime Ripard
2023-03-29 19:56 ` Maxime Ripard
2023-03-29 19:56 ` Maxime Ripard
2023-03-30 4:41 ` Frank Oltmanns
2023-03-30 4:41 ` Frank Oltmanns
2023-03-30 4:41 ` Frank Oltmanns
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=CRUDUEL17ER4.1R8WRNNB5CJ35@void.crly.cz \
--to=romanberanek@icloud.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank@oltmanns.dev \
--cc=icenowy@aosc.io \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=maxime@cerno.tech \
--cc=samuel@sholland.org \
--cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.