mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Guttzeit <t.guttzeit@tuxedocomputers.com>
To: Werner Sembach <wse@tuxedocomputers.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [RFC PATCH 0/1] drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device
Date: Tue, 15 Jul 2025 17:45:53 +0200	[thread overview]
Message-ID: <95fd3ab0-7fe9-4abe-a57d-bf261064c097@tuxedocomputers.com> (raw)
In-Reply-To: <881d51a5-bed3-430e-a3cd-aca5f17e16bf@tuxedocomputers.com>

Hi all,

added intel-gfx@lists.freedesktop.org and 
intel-xe@lists.freedesktop.org, as requested in the ticket.

Best regards,
Tim Guttzeit

Am 09.07.25 um 15:32 schrieb Tim Guttzeit:
> Hi all,
>
> > Tim can you follow up with this? Reducing the communication chain to 
> avoid dropping information.
>
> Yes, here is the Ticket: 
> https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14616
>
> Best regards,
> Tim Guttzeit
>
> Am 09.07.25 um 13:49 schrieb Werner Sembach:
>> Hi all,
>>
>> Am 08.07.25 um 23:05 schrieb Rodrigo Vivi:
>>> On Fri, Jul 04, 2025 at 09:03:45PM +0200, Werner Sembach wrote:
>>>> RFC because I'm not sure if this is the right approach.
>>> Could you please file a gitlab issue for us so we can get someone 
>>> from our
>>> display team to take a look and see if there's anything else that 
>>> could be done
>>> before we take the quirk route?
>>>
>>> https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html
>>
>> Tim can you follow up with this? Reducing the communication chain to 
>> avoid dropping information.
>>
>> Best regards,
>>
>> Werner Sembach
>>
>>>
>>> Thanks for the investigation and the quirk,
>>> Rodrigo.
>>>
>>>> The flicker manifests ever few seconds 1-3 black frames in quick
>>>> succession.
>>>>
>>>> On windows 300Hz can not be selected for the iGPU, but the panel 
>>>> advertises
>>>> it.
>>>>
>>>> A cleaner solution would probably to go over the pixel clock, but 
>>>> for this
>>>> device there is only one 300Hz mode in the panels edid and that is 
>>>> at the
>>>> nativ resolution. Chroma subsampling was not tested as linux afaik 
>>>> offers
>>>> no way to easily enforce it for intel gpus.
>>>>
>>>> Tim Guttzeit (1):
>>>>    drm/i915/display: Avoid unsupported output mode with 300Hz on 
>>>> TUXEDO
>>>>      device
>>>>
>>>>   drivers/gpu/drm/i915/display/intel_dp.c     |  5 ++++
>>>>   drivers/gpu/drm/i915/display/intel_quirks.c | 30 
>>>> +++++++++++++++++++++
>>>>   drivers/gpu/drm/i915/display/intel_quirks.h |  1 +
>>>>   3 files changed, 36 insertions(+)
>>>>
>>>> -- 
>>>> 2.43.0
>>>>
>

-- 
Tim Guttzeit
Development
--
TUXEDO Computers GmbH
Alter Postweg 101
D-86159 Augsburg
--
www.tuxedocomputers.com
Fon: +49 (0) 821 / 8998 2992
--
Amtsgericht Augsburg: HRB 27755
CEO: Herbert Feiler
VAT-ID: DE815420876



      reply	other threads:[~2025-07-15 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-04 19:03 Werner Sembach
2025-07-04 19:03 ` [RFC PATCH 1/1] " Werner Sembach
2025-07-17  7:30   ` Murthy, Arun R
2025-07-17  8:29     ` Tim Guttzeit
2025-07-04 19:22 ` [RFC PATCH 0/1] " Werner Sembach
2025-07-08 21:05 ` Rodrigo Vivi
2025-07-09 11:49   ` Werner Sembach
2025-07-09 13:32     ` Tim Guttzeit
2025-07-15 15:45       ` Tim Guttzeit [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=95fd3ab0-7fe9-4abe-a57d-bf261064c097@tuxedocomputers.com \
    --to=t.guttzeit@tuxedocomputers.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=tursulin@ursulin.net \
    --cc=wse@tuxedocomputers.com \
    /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®