mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Egor Vorontsov <sdoregor@sdore.me>
To: Jani Nikula <jani.nikula@linux.intel.com>, linux-kernel@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	 Thomas Zimmermann <tzimmermann@suse.de>,
	Egor Vorontsov <sdoregor@sdore.me>
Subject: Re: [PATCH RESEND] drm/edid: Implement DisplayID Type IX & X timing blocks parsing
Date: Wed, 12 Feb 2025 08:00:00 +0300	[thread overview]
Message-ID: <8968029b9ceb0bf88106e8372f7a2c4a46780f61.camel@sdore.me> (raw)
In-Reply-To: <87o6za3ujp.fsf@intel.com>

On Mon, 2025-02-10 at 13:31 +0200, Jani Nikula wrote:

> I think "Closes:" is what we want.
> Sometimes it's good to follow the surrounding code, but let's not
> duplicate existing mistakes. ;)

Ack!

> Please avoid 0b, it's very rarely used. Just 0x7. Or we could start
> defining macros for these in drm_displayid_internal.h...

I guess I'll leave the macros to future implementation, as clearly the
naming here is subject to seeing the actual DisplayID 2.1 specs PDF,
which is non-public as of now.

> Refresh rate is -1 in the data block, so this needs timings->refresh + 1.

Ack, nice catch! Worked for me, might've not for someone else's case.

> > +	if (timings->flags & 0x80)
> > + mode->type |= DRM_MODE_TYPE_PREFERRED;
> There's no such thing?

Oh, accidentally picked up from `drm_mode_displayid_detailed()'. Ack.

> > +	u8 timing_size = 6 + ((fb->base.rev & 0x70) >> 4);
> I'd go for int timing_size.

I'd actually vote for an unsigned int, as it's a length and can't
possibly be negative. But sticking to the M.O. of the file here.

Thank you for the review! Fixed per all other notes, as well.

Will resubmit soon,
Egor

      reply	other threads:[~2025-02-12  5:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 21:00 Egor Vorontsov
2025-02-10 11:31 ` Jani Nikula
2025-02-12  5:00   ` Egor Vorontsov [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=8968029b9ceb0bf88106e8372f7a2c4a46780f61.camel@sdore.me \
    --to=sdoregor@sdore.me \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /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®