* Re: [PATCH 1/1] drm/panel: st7703: Fix vertical refresh rate of XBD599
@ 2023-02-19 12:35 ` Ondřej Jirman
0 siblings, 0 replies; 14+ messages in thread
From: Ondřej Jirman @ 2023-02-19 12:35 UTC (permalink / raw)
To: Frank Oltmanns
Cc: Guido Günther, Purism Kernel Team, Thierry Reding,
Sam Ravnborg, David Airlie, Daniel Vetter,
open list:DRM PANEL DRIVERS, open list
On Sun, Feb 19, 2023 at 12:45:53PM +0100, Frank Oltmanns wrote:
> Fix the XBD599 panel's slight visual stutter by correcting the pixel
> clock speed so that the panel's 60Hz vertical refresh rate is met.
>
> Set the clock speed using the underlying formula instead of a magic
> number. To have a consistent procedure for both panels, set the JH057N
> panel's clock also as a formula.
>
> ---
> drivers/gpu/drm/panel/panel-sitronix-st7703.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/panel/panel-sitronix-st7703.c b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
> index 6747ca237ced..cd7d631f7573 100644
> --- a/drivers/gpu/drm/panel/panel-sitronix-st7703.c
> +++ b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
> @@ -139,7 +139,7 @@ static const struct drm_display_mode jh057n00900_mode = {
> .vsync_start = 1440 + 20,
> .vsync_end = 1440 + 20 + 4,
> .vtotal = 1440 + 20 + 4 + 12,
> - .clock = 75276,
> + .clock = (720 + 90 + 20 + 20) * (1440 + 20 + 4 + 12) * 60 / 1000,
> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
> .width_mm = 65,
> .height_mm = 130,
> @@ -324,7 +324,7 @@ static const struct drm_display_mode xbd599_mode = {
> .vsync_start = 1440 + 18,
> .vsync_end = 1440 + 18 + 10,
> .vtotal = 1440 + 18 + 10 + 17,
> - .clock = 69000,
> + .clock = (720 + 40 + 40 + 40) * (1440 + 18 + 10 + 17) * 60 / 1000,
As for pinephone, A64 can't produce 74.844 MHz precisely, so this will not work.
Better fix is to alter the mode so that clock can be something the only SoC this
panel is used with can actually produce.
See eg. https://github.com/megous/linux/commit/dd070679d717e7f34af7558563698240a43981a6
which is tested to actually produce 60Hz by measuring the vsync events against
the CPU timer.
Your patch will not produce the intended effect.
kind regards,
o.
> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
> .width_mm = 68,
> .height_mm = 136,
> --
> 2.39.1
>
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [PATCH 1/1] drm/panel: st7703: Fix vertical refresh rate of XBD599
2023-02-19 12:35 ` Ondřej Jirman
@ 2023-02-20 7:40 ` Frank Oltmanns
-1 siblings, 0 replies; 14+ messages in thread
From: Frank Oltmanns @ 2023-02-20 7:40 UTC (permalink / raw)
To: Ondřej Jirman
Cc: Guido Günther, Purism Kernel Team, Thierry Reding,
Sam Ravnborg, David Airlie, Daniel Vetter,
open list:DRM PANEL DRIVERS, open list
[-- Attachment #1: Type: text/plain, Size: 4763 bytes --]
Hi Ondřej,
hi all,
Ondřej Jirman <megous@megous.com> writes:
> On Sun, Feb 19, 2023 at 12:45:53PM +0100, Frank Oltmanns wrote:
>> Fix the XBD599 panel’s slight visual stutter by correcting the pixel
>> clock speed so that the panel’s 60Hz vertical refresh rate is met.
>>
>> Set the clock speed using the underlying formula instead of a magic
>> number. To have a consistent procedure for both panels, set the JH057N
>> panel’s clock also as a formula.
>>
>> —
>> drivers/gpu/drm/panel/panel-sitronix-st7703.c | 4 ++–
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff –git a/drivers/gpu/drm/panel/panel-sitronix-st7703.c b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
>> index 6747ca237ced..cd7d631f7573 100644
>> — a/drivers/gpu/drm/panel/panel-sitronix-st7703.c
>> +++ b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
>> @@ -139,7 +139,7 @@ static const struct drm_display_mode jh057n00900_mode = {
>> .vsync_start = 1440 + 20,
>> .vsync_end = 1440 + 20 + 4,
>> .vtotal = 1440 + 20 + 4 + 12,
>> - .clock = 75276,
>> + .clock = (720 + 90 + 20 + 20) * (1440 + 20 + 4 + 12) * 60 / 1000,
>> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
>> .width_mm = 65,
>> .height_mm = 130,
>> @@ -324,7 +324,7 @@ static const struct drm_display_mode xbd599_mode = {
>> .vsync_start = 1440 + 18,
>> .vsync_end = 1440 + 18 + 10,
>> .vtotal = 1440 + 18 + 10 + 17,
>> - .clock = 69000,
>> + .clock = (720 + 40 + 40 + 40) * (1440 + 18 + 10 + 17) * 60 / 1000,
>
> As for pinephone, A64 can’t produce 74.844 MHz precisely, so this will not work.
>
> Better fix is to alter the mode so that clock can be something the only SoC this
> panel is used with can actually produce.
>
> See eg. <https://github.com/megous/linux/commit/dd070679d717e7f34af7558563698240a43981a6>
> which is tested to actually produce 60Hz by measuring the vsync events against
> the CPU timer.
>
> Your patch will not produce the intended effect.
>
> kind regards,
> o.
>
The TL;DR of my upcoming musings are: Thank you very much for your feedback! Any
recommendations for an informative read about the topic that you or anybody else
has, is greatly appreciated.
How did you measure the vsync events? Were you using vblank interrupts [1]?
I have to admit that I tested only visually and couldn’t spot a difference
between your patch and mine. I’ll need to put more thinking into this, and maybe
you or anyone reading this can help me with that.
My interpretation of the `struct drm_display_mode` documentation [2] was, that
these are logical dimensions/clocks that somewhere down the stack are converted
to their physical/hardware representation.
But now I’ve read the description of the struct’s “crtc_clock” member more
carefully. It says:
“Actual pixel or dot clock in the hardware. This differs from the
logical @clock when e.g. using interlacing, double-clocking, stereo
modes or other fancy stuff that changes the timings and signals
actually sent over the wire.”
So, can I say that if we don’t use “interlacing, double-clocking, stereo modes
or other fancy stuff” that `crtc_clock` will be equal to `clock` and therefore
we have to choose `clock` according to the SoC’s capabilities?
Also, I haven’t found a source about which values to use for the front and back
porch part of the panel and why can you just “arbitrarily” change those. My
assumption is, that those are just extra pixels we can add to make the
dimensions match the ratio of clock and vertical refresh rate. At least that
seems to be, what you did in your patch. But again, no source to back my
assumption about the range the porches can have.
I’ve put the following docs on my “to read and understand” list:
• Allwinner A64 User Manual (to learn more about the SoC’s TCON0 and what
clock’s the SoC can produce)
• drm-internals.rst
• “Rendering PinePhone’s display” [3], to learn why it produces 69 MHz.
• Your commit message for the PinePhone Pro panel [4] (found on your blog:
<https://xnux.eu/log/>)
Is there anything else I should add?
Thank you again and best regards,
Frank
[1] <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/drm_vblank.c>
[2] <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/drm/drm_modes.h#n198>
[3] <https://lupyuen.github.io/articles/de>
[4] <https://github.com/megous/linux/commit/a173b114c9323c718530280b3a918d0925edaa6a>
>> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
>> .width_mm = 68,
>> .height_mm = 136,
>> –
>> 2.39.1
>>
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [PATCH 1/1] drm/panel: st7703: Fix vertical refresh rate of XBD599
@ 2023-02-20 7:40 ` Frank Oltmanns
0 siblings, 0 replies; 14+ messages in thread
From: Frank Oltmanns @ 2023-02-20 7:40 UTC (permalink / raw)
To: Ondřej Jirman
Cc: Purism Kernel Team, Sam Ravnborg, Guido Günther, open list,
open list:DRM PANEL DRIVERS, Thierry Reding
[-- Attachment #1: Type: text/plain, Size: 4763 bytes --]
Hi Ondřej,
hi all,
Ondřej Jirman <megous@megous.com> writes:
> On Sun, Feb 19, 2023 at 12:45:53PM +0100, Frank Oltmanns wrote:
>> Fix the XBD599 panel’s slight visual stutter by correcting the pixel
>> clock speed so that the panel’s 60Hz vertical refresh rate is met.
>>
>> Set the clock speed using the underlying formula instead of a magic
>> number. To have a consistent procedure for both panels, set the JH057N
>> panel’s clock also as a formula.
>>
>> —
>> drivers/gpu/drm/panel/panel-sitronix-st7703.c | 4 ++–
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff –git a/drivers/gpu/drm/panel/panel-sitronix-st7703.c b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
>> index 6747ca237ced..cd7d631f7573 100644
>> — a/drivers/gpu/drm/panel/panel-sitronix-st7703.c
>> +++ b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
>> @@ -139,7 +139,7 @@ static const struct drm_display_mode jh057n00900_mode = {
>> .vsync_start = 1440 + 20,
>> .vsync_end = 1440 + 20 + 4,
>> .vtotal = 1440 + 20 + 4 + 12,
>> - .clock = 75276,
>> + .clock = (720 + 90 + 20 + 20) * (1440 + 20 + 4 + 12) * 60 / 1000,
>> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
>> .width_mm = 65,
>> .height_mm = 130,
>> @@ -324,7 +324,7 @@ static const struct drm_display_mode xbd599_mode = {
>> .vsync_start = 1440 + 18,
>> .vsync_end = 1440 + 18 + 10,
>> .vtotal = 1440 + 18 + 10 + 17,
>> - .clock = 69000,
>> + .clock = (720 + 40 + 40 + 40) * (1440 + 18 + 10 + 17) * 60 / 1000,
>
> As for pinephone, A64 can’t produce 74.844 MHz precisely, so this will not work.
>
> Better fix is to alter the mode so that clock can be something the only SoC this
> panel is used with can actually produce.
>
> See eg. <https://github.com/megous/linux/commit/dd070679d717e7f34af7558563698240a43981a6>
> which is tested to actually produce 60Hz by measuring the vsync events against
> the CPU timer.
>
> Your patch will not produce the intended effect.
>
> kind regards,
> o.
>
The TL;DR of my upcoming musings are: Thank you very much for your feedback! Any
recommendations for an informative read about the topic that you or anybody else
has, is greatly appreciated.
How did you measure the vsync events? Were you using vblank interrupts [1]?
I have to admit that I tested only visually and couldn’t spot a difference
between your patch and mine. I’ll need to put more thinking into this, and maybe
you or anyone reading this can help me with that.
My interpretation of the `struct drm_display_mode` documentation [2] was, that
these are logical dimensions/clocks that somewhere down the stack are converted
to their physical/hardware representation.
But now I’ve read the description of the struct’s “crtc_clock” member more
carefully. It says:
“Actual pixel or dot clock in the hardware. This differs from the
logical @clock when e.g. using interlacing, double-clocking, stereo
modes or other fancy stuff that changes the timings and signals
actually sent over the wire.”
So, can I say that if we don’t use “interlacing, double-clocking, stereo modes
or other fancy stuff” that `crtc_clock` will be equal to `clock` and therefore
we have to choose `clock` according to the SoC’s capabilities?
Also, I haven’t found a source about which values to use for the front and back
porch part of the panel and why can you just “arbitrarily” change those. My
assumption is, that those are just extra pixels we can add to make the
dimensions match the ratio of clock and vertical refresh rate. At least that
seems to be, what you did in your patch. But again, no source to back my
assumption about the range the porches can have.
I’ve put the following docs on my “to read and understand” list:
• Allwinner A64 User Manual (to learn more about the SoC’s TCON0 and what
clock’s the SoC can produce)
• drm-internals.rst
• “Rendering PinePhone’s display” [3], to learn why it produces 69 MHz.
• Your commit message for the PinePhone Pro panel [4] (found on your blog:
<https://xnux.eu/log/>)
Is there anything else I should add?
Thank you again and best regards,
Frank
[1] <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/drm_vblank.c>
[2] <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/drm/drm_modes.h#n198>
[3] <https://lupyuen.github.io/articles/de>
[4] <https://github.com/megous/linux/commit/a173b114c9323c718530280b3a918d0925edaa6a>
>> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
>> .width_mm = 68,
>> .height_mm = 136,
>> –
>> 2.39.1
>>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 1/1] drm/panel: st7703: Fix vertical refresh rate of XBD599
2023-02-19 12:35 ` Ondřej Jirman
@ 2023-02-26 15:17 ` Frank Oltmanns
-1 siblings, 0 replies; 14+ messages in thread
From: Frank Oltmanns @ 2023-02-26 15:17 UTC (permalink / raw)
To: Guido Günther, Ondřej Jirman
Cc: Purism Kernel Team, Sam Ravnborg, open list,
open list:DRM PANEL DRIVERS, Thierry Reding
[-- Attachment #1: Type: text/plain, Size: 3169 bytes --]
Hi Ondřej,
hi Guido,
On 2023-02-19 at 13:35:42 +0100, Ondřej Jirman <megous@megous.com> wrote:
> On Sun, Feb 19, 2023 at 12:45:53PM +0100, Frank Oltmanns wrote:
>> Fix the XBD599 panel’s slight visual stutter by correcting the pixel
>> clock speed so that the panel’s 60Hz vertical refresh rate is met.
>>
>> Set the clock speed using the underlying formula instead of a magic
>> number. To have a consistent procedure for both panels, set the JH057N
>> panel’s clock also as a formula.
>>
>> —
>> drivers/gpu/drm/panel/panel-sitronix-st7703.c | 4 ++–
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff –git a/drivers/gpu/drm/panel/panel-sitronix-st7703.c b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
>> index 6747ca237ced..cd7d631f7573 100644
>> — a/drivers/gpu/drm/panel/panel-sitronix-st7703.c
>> +++ b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
>> @@ -139,7 +139,7 @@ static const struct drm_display_mode jh057n00900_mode = {
>> .vsync_start = 1440 + 20,
>> .vsync_end = 1440 + 20 + 4,
>> .vtotal = 1440 + 20 + 4 + 12,
>> - .clock = 75276,
>> + .clock = (720 + 90 + 20 + 20) * (1440 + 20 + 4 + 12) * 60 / 1000,
>> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
>> .width_mm = 65,
>> .height_mm = 130,
>> @@ -324,7 +324,7 @@ static const struct drm_display_mode xbd599_mode = {
>> .vsync_start = 1440 + 18,
>> .vsync_end = 1440 + 18 + 10,
>> .vtotal = 1440 + 18 + 10 + 17,
>> - .clock = 69000,
>> + .clock = (720 + 40 + 40 + 40) * (1440 + 18 + 10 + 17) * 60 / 1000,
>
> As for pinephone, A64 can’t produce 74.844 MHz precisely, so this will not work.
>
> Better fix is to alter the mode so that clock can be something the only SoC this
> panel is used with can actually produce.
>
> See eg. <https://github.com/megous/linux/commit/dd070679d717e7f34af7558563698240a43981a6>
> which is tested to actually produce 60Hz by measuring the vsync events against
> the CPU timer.
I did some testing using a 60fps video I produced using the following command:
ffmpeg -f lavfi -i testsrc=duration=10:size=80x50:rate=60 -vf “drawtext=text=%{n}:fontsize=36:r=60:x=(w-tw)/2: y=h-(1*lh):fontcolor=white:box=1:boxcolor=0x00000099” test_80x50.mp4
This 10-second video shows an increasing number on every frame, which makes it easy to spot dropped frames by recording the playback with a camera that can record more than 60fps (I used a 240fps camera).
When playing back that video with your current drm-6.2 branch I get a steady 60fps. But applying either your or my patch to mainline, only helps very little. Frames are being skipped more often than not in both cases.
Therefore, I need to investigate more and retract the patch for now.
The other two patches I sent earlier, however, are far more important for making the pinephone usable on mainline.
Best regards,
Frank
>
> Your patch will not produce the intended effect.
>
> kind regards,
> o.
>
>> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
>> .width_mm = 68,
>> .height_mm = 136,
>> –
>> 2.39.1
>>
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [PATCH 1/1] drm/panel: st7703: Fix vertical refresh rate of XBD599
@ 2023-02-26 15:17 ` Frank Oltmanns
0 siblings, 0 replies; 14+ messages in thread
From: Frank Oltmanns @ 2023-02-26 15:17 UTC (permalink / raw)
To: Guido Günther, Ondřej Jirman
Cc: Purism Kernel Team, Thierry Reding, Sam Ravnborg, David Airlie,
Daniel Vetter, open list:DRM PANEL DRIVERS, open list
[-- Attachment #1: Type: text/plain, Size: 3169 bytes --]
Hi Ondřej,
hi Guido,
On 2023-02-19 at 13:35:42 +0100, Ondřej Jirman <megous@megous.com> wrote:
> On Sun, Feb 19, 2023 at 12:45:53PM +0100, Frank Oltmanns wrote:
>> Fix the XBD599 panel’s slight visual stutter by correcting the pixel
>> clock speed so that the panel’s 60Hz vertical refresh rate is met.
>>
>> Set the clock speed using the underlying formula instead of a magic
>> number. To have a consistent procedure for both panels, set the JH057N
>> panel’s clock also as a formula.
>>
>> —
>> drivers/gpu/drm/panel/panel-sitronix-st7703.c | 4 ++–
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff –git a/drivers/gpu/drm/panel/panel-sitronix-st7703.c b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
>> index 6747ca237ced..cd7d631f7573 100644
>> — a/drivers/gpu/drm/panel/panel-sitronix-st7703.c
>> +++ b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
>> @@ -139,7 +139,7 @@ static const struct drm_display_mode jh057n00900_mode = {
>> .vsync_start = 1440 + 20,
>> .vsync_end = 1440 + 20 + 4,
>> .vtotal = 1440 + 20 + 4 + 12,
>> - .clock = 75276,
>> + .clock = (720 + 90 + 20 + 20) * (1440 + 20 + 4 + 12) * 60 / 1000,
>> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
>> .width_mm = 65,
>> .height_mm = 130,
>> @@ -324,7 +324,7 @@ static const struct drm_display_mode xbd599_mode = {
>> .vsync_start = 1440 + 18,
>> .vsync_end = 1440 + 18 + 10,
>> .vtotal = 1440 + 18 + 10 + 17,
>> - .clock = 69000,
>> + .clock = (720 + 40 + 40 + 40) * (1440 + 18 + 10 + 17) * 60 / 1000,
>
> As for pinephone, A64 can’t produce 74.844 MHz precisely, so this will not work.
>
> Better fix is to alter the mode so that clock can be something the only SoC this
> panel is used with can actually produce.
>
> See eg. <https://github.com/megous/linux/commit/dd070679d717e7f34af7558563698240a43981a6>
> which is tested to actually produce 60Hz by measuring the vsync events against
> the CPU timer.
I did some testing using a 60fps video I produced using the following command:
ffmpeg -f lavfi -i testsrc=duration=10:size=80x50:rate=60 -vf “drawtext=text=%{n}:fontsize=36:r=60:x=(w-tw)/2: y=h-(1*lh):fontcolor=white:box=1:boxcolor=0x00000099” test_80x50.mp4
This 10-second video shows an increasing number on every frame, which makes it easy to spot dropped frames by recording the playback with a camera that can record more than 60fps (I used a 240fps camera).
When playing back that video with your current drm-6.2 branch I get a steady 60fps. But applying either your or my patch to mainline, only helps very little. Frames are being skipped more often than not in both cases.
Therefore, I need to investigate more and retract the patch for now.
The other two patches I sent earlier, however, are far more important for making the pinephone usable on mainline.
Best regards,
Frank
>
> Your patch will not produce the intended effect.
>
> kind regards,
> o.
>
>> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
>> .width_mm = 68,
>> .height_mm = 136,
>> –
>> 2.39.1
>>
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [PATCH 1/1] drm/panel: st7703: Fix vertical refresh rate of XBD599
2023-02-26 15:17 ` Frank Oltmanns
@ 2023-02-26 17:17 ` Ondřej Jirman
-1 siblings, 0 replies; 14+ messages in thread
From: Ondřej Jirman @ 2023-02-26 17:17 UTC (permalink / raw)
To: Frank Oltmanns
Cc: Guido Günther, Purism Kernel Team, Thierry Reding,
Sam Ravnborg, David Airlie, Daniel Vetter,
open list:DRM PANEL DRIVERS, open list
Hi,
On Sun, Feb 26, 2023 at 04:17:32PM +0100, Frank Oltmanns wrote:
> Hi Ondřej,
> hi Guido,
>
> On 2023-02-19 at 13:35:42 +0100, Ondřej Jirman <megous@megous.com> wrote:
>
> > On Sun, Feb 19, 2023 at 12:45:53PM +0100, Frank Oltmanns wrote:
> >> Fix the XBD599 panel’s slight visual stutter by correcting the pixel
> >> clock speed so that the panel’s 60Hz vertical refresh rate is met.
> >>
> >> Set the clock speed using the underlying formula instead of a magic
> >> number. To have a consistent procedure for both panels, set the JH057N
> >> panel’s clock also as a formula.
> >>
> >> —
> >> drivers/gpu/drm/panel/panel-sitronix-st7703.c | 4 ++–
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff –git a/drivers/gpu/drm/panel/panel-sitronix-st7703.c b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
> >> index 6747ca237ced..cd7d631f7573 100644
> >> — a/drivers/gpu/drm/panel/panel-sitronix-st7703.c
> >> +++ b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
> >> @@ -139,7 +139,7 @@ static const struct drm_display_mode jh057n00900_mode = {
> >> .vsync_start = 1440 + 20,
> >> .vsync_end = 1440 + 20 + 4,
> >> .vtotal = 1440 + 20 + 4 + 12,
> >> - .clock = 75276,
> >> + .clock = (720 + 90 + 20 + 20) * (1440 + 20 + 4 + 12) * 60 / 1000,
> >> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
> >> .width_mm = 65,
> >> .height_mm = 130,
> >> @@ -324,7 +324,7 @@ static const struct drm_display_mode xbd599_mode = {
> >> .vsync_start = 1440 + 18,
> >> .vsync_end = 1440 + 18 + 10,
> >> .vtotal = 1440 + 18 + 10 + 17,
> >> - .clock = 69000,
> >> + .clock = (720 + 40 + 40 + 40) * (1440 + 18 + 10 + 17) * 60 / 1000,
> >
> > As for pinephone, A64 can’t produce 74.844 MHz precisely, so this will not work.
> >
> > Better fix is to alter the mode so that clock can be something the only SoC this
> > panel is used with can actually produce.
> >
> > See eg. <https://github.com/megous/linux/commit/dd070679d717e7f34af7558563698240a43981a6>
> > which is tested to actually produce 60Hz by measuring the vsync events against
> > the CPU timer.
>
> I did some testing using a 60fps video I produced using the following command:
> ffmpeg -f lavfi -i testsrc=duration=10:size=80x50:rate=60 -vf
> “drawtext=text=%{n}:fontsize=36:r=60:x=(w-tw)/2:
> y=h-(1*lh):fontcolor=white:box=1:boxcolor=0x00000099” test_80x50.mp4
>
> This 10-second video shows an increasing number on every frame, which makes it
> easy to spot dropped frames by recording the playback with a camera that can
> record more than 60fps (I used a 240fps camera).
>
> When playing back that video with your current drm-6.2 branch I get a steady
> 60fps. But applying either your or my patch to mainline, only helps very
> little. Frames are being skipped more often than not in both cases.
>
> Therefore, I need to investigate more and retract the patch for now.
>
> The other two patches I sent earlier, however, are far more important for
> making the pinephone usable on mainline.
Mainline sunxi DE2 DRM driver has a bug where it doesn't respect the requirement
to use the 50% higher clock for MIPI DSI output. So real refresh rate will be
2/3 the expected one, even if everything else is set correctly.
This is not documented in A64 datasheet, but it is documented in one of other
Allwinner SoC datasheets that reuse DE2 engine and MIPI DSI interface.
So, you need this first: https://github.com/megous/linux/commit/cc3ce397408b597f5cab2c987cd88cce3a8509d3
When this is fixed, it's possible to finetune the panel refresh rate/mode to
the actual clock. The values I have sent you the link to are tuned to
60.006 Hz Maybe you'll find some values that will produce 60Hz exactly,
but the above is the closest I was able to get to 60Hz.
kind regards,
o.
> Best regards,
> Frank
>
> >
> > Your patch will not produce the intended effect.
> >
> > kind regards,
> > o.
> >
> >> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
> >> .width_mm = 68,
> >> .height_mm = 136,
> >> –
> >> 2.39.1
> >>
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [PATCH 1/1] drm/panel: st7703: Fix vertical refresh rate of XBD599
@ 2023-02-26 17:17 ` Ondřej Jirman
0 siblings, 0 replies; 14+ messages in thread
From: Ondřej Jirman @ 2023-02-26 17:17 UTC (permalink / raw)
To: Frank Oltmanns
Cc: Purism Kernel Team, Sam Ravnborg, Guido Günther, open list,
open list:DRM PANEL DRIVERS, Thierry Reding
Hi,
On Sun, Feb 26, 2023 at 04:17:32PM +0100, Frank Oltmanns wrote:
> Hi Ondřej,
> hi Guido,
>
> On 2023-02-19 at 13:35:42 +0100, Ondřej Jirman <megous@megous.com> wrote:
>
> > On Sun, Feb 19, 2023 at 12:45:53PM +0100, Frank Oltmanns wrote:
> >> Fix the XBD599 panel’s slight visual stutter by correcting the pixel
> >> clock speed so that the panel’s 60Hz vertical refresh rate is met.
> >>
> >> Set the clock speed using the underlying formula instead of a magic
> >> number. To have a consistent procedure for both panels, set the JH057N
> >> panel’s clock also as a formula.
> >>
> >> —
> >> drivers/gpu/drm/panel/panel-sitronix-st7703.c | 4 ++–
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff –git a/drivers/gpu/drm/panel/panel-sitronix-st7703.c b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
> >> index 6747ca237ced..cd7d631f7573 100644
> >> — a/drivers/gpu/drm/panel/panel-sitronix-st7703.c
> >> +++ b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
> >> @@ -139,7 +139,7 @@ static const struct drm_display_mode jh057n00900_mode = {
> >> .vsync_start = 1440 + 20,
> >> .vsync_end = 1440 + 20 + 4,
> >> .vtotal = 1440 + 20 + 4 + 12,
> >> - .clock = 75276,
> >> + .clock = (720 + 90 + 20 + 20) * (1440 + 20 + 4 + 12) * 60 / 1000,
> >> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
> >> .width_mm = 65,
> >> .height_mm = 130,
> >> @@ -324,7 +324,7 @@ static const struct drm_display_mode xbd599_mode = {
> >> .vsync_start = 1440 + 18,
> >> .vsync_end = 1440 + 18 + 10,
> >> .vtotal = 1440 + 18 + 10 + 17,
> >> - .clock = 69000,
> >> + .clock = (720 + 40 + 40 + 40) * (1440 + 18 + 10 + 17) * 60 / 1000,
> >
> > As for pinephone, A64 can’t produce 74.844 MHz precisely, so this will not work.
> >
> > Better fix is to alter the mode so that clock can be something the only SoC this
> > panel is used with can actually produce.
> >
> > See eg. <https://github.com/megous/linux/commit/dd070679d717e7f34af7558563698240a43981a6>
> > which is tested to actually produce 60Hz by measuring the vsync events against
> > the CPU timer.
>
> I did some testing using a 60fps video I produced using the following command:
> ffmpeg -f lavfi -i testsrc=duration=10:size=80x50:rate=60 -vf
> “drawtext=text=%{n}:fontsize=36:r=60:x=(w-tw)/2:
> y=h-(1*lh):fontcolor=white:box=1:boxcolor=0x00000099” test_80x50.mp4
>
> This 10-second video shows an increasing number on every frame, which makes it
> easy to spot dropped frames by recording the playback with a camera that can
> record more than 60fps (I used a 240fps camera).
>
> When playing back that video with your current drm-6.2 branch I get a steady
> 60fps. But applying either your or my patch to mainline, only helps very
> little. Frames are being skipped more often than not in both cases.
>
> Therefore, I need to investigate more and retract the patch for now.
>
> The other two patches I sent earlier, however, are far more important for
> making the pinephone usable on mainline.
Mainline sunxi DE2 DRM driver has a bug where it doesn't respect the requirement
to use the 50% higher clock for MIPI DSI output. So real refresh rate will be
2/3 the expected one, even if everything else is set correctly.
This is not documented in A64 datasheet, but it is documented in one of other
Allwinner SoC datasheets that reuse DE2 engine and MIPI DSI interface.
So, you need this first: https://github.com/megous/linux/commit/cc3ce397408b597f5cab2c987cd88cce3a8509d3
When this is fixed, it's possible to finetune the panel refresh rate/mode to
the actual clock. The values I have sent you the link to are tuned to
60.006 Hz Maybe you'll find some values that will produce 60Hz exactly,
but the above is the closest I was able to get to 60Hz.
kind regards,
o.
> Best regards,
> Frank
>
> >
> > Your patch will not produce the intended effect.
> >
> > kind regards,
> > o.
> >
> >> .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC,
> >> .width_mm = 68,
> >> .height_mm = 136,
> >> –
> >> 2.39.1
> >>
^ permalink raw reply [flat|nested] 14+ messages in thread