From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ian Forbes <ian.forbes@broadcom.com>,
Hamza Mahfooz <hamza.mahfooz@amd.com>
Cc: dri-devel@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona.vetter@ffwll.ch>,
Alex Deucher <alexander.deucher@amd.com>,
Rodrigo Siqueira <rodrigo.siqueira@amd.com>,
Harry Wentland <harry.wentland@amd.com>,
Karol Herbst <kherbst@redhat.com>
Subject: Re: [PATCH v4] drm/edid: add CTA Video Format Data Block support
Date: Mon, 04 Nov 2024 11:53:38 +0200 [thread overview]
Message-ID: <87wmhjiau5.fsf@intel.com> (raw)
In-Reply-To: <CAO6MGtg-+btwUk9ZkJj7Zreyk_VfyDtsc_4k05rCv+vFJRSJVQ@mail.gmail.com>
On Fri, 01 Nov 2024, Ian Forbes <ian.forbes@broadcom.com> wrote:
> We'd like to use the OVT modes for vmwgfx. Can you export the main OVT
> function so it matches the CVT one? Something like this:
>
> struct drm_display_mode *drm_ovt_mode(struct drm_device *dev, int rid,
> int vrefresh);
>
> On Mon, Sep 9, 2024 at 12:17 PM Hamza Mahfooz <hamza.mahfooz@amd.com> wrote:
>>
>> +
>> +/* OVT Algorthim as specified in CTA-861-I */
>> +static struct drm_display_mode *
>> +calculate_ovt_mode(struct drm_connector *connector, const struct cta_rid *rid,
>> + u16 vrate)
>
> Also all instances of CEA should probably be replaced with CTA, not
> necessarily in this series, but they changed their name ~10 years ago.
Yeah. I've gradually done some renames, but it would be good for
consistency for someone to finish the job.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-04 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 17:12 [PATCH v4] drm/edid: add CTA Video Format Data Block support Hamza Mahfooz
2024-09-10 12:05 ` Jani Nikula
2024-11-05 22:48 ` Hamza Mahfooz
2024-11-01 14:13 ` Ian Forbes
2024-11-04 9:53 ` Jani Nikula [this message]
2024-11-05 22:42 ` Hamza Mahfooz
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=87wmhjiau5.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamza.mahfooz@amd.com \
--cc=harry.wentland@amd.com \
--cc=ian.forbes@broadcom.com \
--cc=kherbst@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rodrigo.siqueira@amd.com \
--cc=simona.vetter@ffwll.ch \
--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 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.