From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Eric Engestrom <eric.engestrom@intel.com>
Cc: Devarsh Thakkar <devarsh.thakkar@xilinx.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH libdrm v4] modetest: Use floating vrefresh while dumping mode
Date: Thu, 5 Dec 2019 16:18:39 +0200 [thread overview]
Message-ID: <20191205141839.GG1208@intel.com> (raw)
In-Reply-To: <20191205131632.sozkmb4kechung7o@intel.com>
On Thu, Dec 05, 2019 at 01:16:32PM +0000, Eric Engestrom wrote:
> On Tuesday, 2019-12-03 06:37:36 -0800, Devarsh Thakkar wrote:
> > Add function to derive floating value of vertical
> > refresh rate from drm mode using pixel clock,
> > horizontal total size and vertical total size.
> >
> > Use this function to find suitable mode having vrefresh
> > value which is matching with user provided vrefresh value.
> >
> > If user doesn't provide any vrefresh value in args then
> > update vertical refresh rate value in pipe args using this
> > function.
> >
> > Also use this function for printing floating vrefresh while
> > dumping all available modes.
> >
> > This will give more accurate picture to user for available modes
> > differentiated by floating vertical refresh rate and help user
> > select more appropriate mode using suitable refresh rate value.
>
> Any chance you could use the merge requests infra instead of patches on
> the mailing list? :)
> https://gitlab.freedesktop.org/mesa/drm/merge_requests
Yuck. I'll not use that at least.
--
Ville Syrjälä
Intel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-12-05 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 14:37 [PATCH libdrm v4] modetest: Use floating vrefresh while dumping mode Devarsh Thakkar
2019-12-05 13:16 ` Eric Engestrom
2019-12-05 14:18 ` Ville Syrjälä [this message]
2019-12-09 12:56 ` Devarsh Thakkar
2019-12-11 15:49 ` Ville Syrjälä
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=20191205141839.GG1208@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=devarsh.thakkar@xilinx.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.engestrom@intel.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