Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michał Kopeć" <michal@nozomi.space>
To: Shawn.Sung@mediatek.com
Cc: linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 1/1] drm/mediatek: Filter modes according to hardware capability
Date: Wed, 27 Nov 2024 15:28:42 +0100	[thread overview]
Message-ID: <UJ5MNS.Y9SOF1FBB3XG@nozomi.space> (raw)

(Re-sending because Shawn's @google email is inactive)

Hi Shawn,

I'm a new owner of the Chromebook Ciri (MT8188) and have run into an 
issue which I believe is related to this patch.

I'm attempting to use a 3440x1440 144Hz monitor over DisplayPort, but 
the available resolutions are limited to 2560x1440@120Hz. I found this 
patch, then I confirmed with the monitor's EDID that i am indeed 
reaching data rates above 8250 (though minimally) in higher resolution 
modes.

I wanted to ask about this comment:

 > The proposed formula is only one way to estimate whether our SoC
 > supports the mode setting. The basic idea behind it is just to check
 > if the data rate requirement is too high (directly proportional to
 > pixel clock, inversely proportional to vbp). Please adjust the
 > function if it doesn't fit your situation in the future.

- Can you confirm if the reference number 8250 is the hard limit of the 
hardware?
- Could you suggest other formulae that could work for my use case? I'd 
be happy to implement and test on my end but as I don't have access to 
MTK documentation, I don't know the actual limits of the hardware and 
how to deal with them

Regards,
Michał Kopeć





             reply	other threads:[~2024-11-28 10:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 14:28 Michał Kopeć [this message]
2024-11-29  6:17 ` [PATCH v2 1/1] drm/mediatek: Filter modes according to hardware capability CK Hu (胡俊光)
2024-11-29 10:26 ` [SPAM]Re: " Shawn Sung (宋孝謙)
     [not found] <7QZPNS.0SWJEBP013RP1@nozomi.space>
2024-12-02  2:19 ` Shawn Sung (宋孝謙)
2024-12-03  8:16   ` Jason-JH Lin (林睿祥)
  -- strict thread matches above, loose matches on Subject: below --
2024-11-27 14:24 Michał Kopeć
2024-02-07  2:15 [PATCH v2 0/1] " Hsiao Chien Sung
2024-02-07  2:15 ` [PATCH v2 1/1] drm/mediatek: " Hsiao Chien Sung
2024-02-16  9:38   ` CK Hu (胡俊光)
2024-02-20  9:06     ` Shawn Sung (宋孝謙)

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=UJ5MNS.Y9SOF1FBB3XG@nozomi.space \
    --to=michal@nozomi.space \
    --cc=2025e0ddff85a3bfa1f8894587b5e26ba3cfd65b.camel@mediatek.com \
    --cc=Shawn.Sung@mediatek.com \
    --cc=linux-mediatek@lists.infradead.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