From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>
Cc: <intel-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <ankit.k.nautiyal@intel.com>,
<suraj.kandpal@intel.com>, <jani.nikula@linux.intel.com>,
<sfr@canb.auug.org.au>, <lucas.demarchi@intel.com>
Subject: Re: [PATCH v2 1/2] drm/dp: Describe target_rr_divider in struct drm_dp_as_sdp
Date: Fri, 14 Jun 2024 15:53:04 -0400 [thread overview]
Message-ID: <ZmyfoMYRfKJv16KD@intel.com> (raw)
In-Reply-To: <20240614042558.376983-2-mitulkumar.ajitkumar.golani@intel.com>
On Fri, Jun 14, 2024 at 09:55:57AM +0530, Mitul Golani wrote:
> Describe newly added parameter target_rr_divider in struct
> drm_dp_as_sdp.
>
> -v2:
> Remove extra line from commit message.(Lucas)
>
> Fixes: a20c6d954d75 ("drm/dp: Add refresh rate divider to struct representing AS SDP")
> Cc: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
> Cc: Arun R Murthy <arun.r.murthy@intel.com>
> Cc: Suraj Kandpal <suraj.kandpal@intel.com>
> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
> Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> include/drm/display/drm_dp_helper.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/drm/display/drm_dp_helper.h b/include/drm/display/drm_dp_helper.h
> index ea03e1dd26ba..7f2567fa230d 100644
> --- a/include/drm/display/drm_dp_helper.h
> +++ b/include/drm/display/drm_dp_helper.h
> @@ -112,6 +112,7 @@ struct drm_dp_vsc_sdp {
> * @target_rr: Target Refresh
> * @duration_incr_ms: Successive frame duration increase
> * @duration_decr_ms: Successive frame duration decrease
> + * @target_rr_divider: Target refresh rate divider
Maarten, Maxime, or Thomas,
the patch introducing this target_rr_divider is in drm-intel-next.
Ack on adding this through drm-intel-next as well?
> * @mode: Adaptive Sync Operation Mode
> */
> struct drm_dp_as_sdp {
> --
> 2.45.2
>
next prev parent reply other threads:[~2024-06-14 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 4:25 [PATCH v2 0/2] CMRR patch fixes Mitul Golani
2024-06-14 4:25 ` [PATCH v2 1/2] drm/dp: Describe target_rr_divider in struct drm_dp_as_sdp Mitul Golani
2024-06-14 19:53 ` Rodrigo Vivi [this message]
2024-06-18 20:10 ` Rodrigo Vivi
2024-06-14 4:25 ` [PATCH v2 2/2] drm/i915/display: Update calculation to avoid overflow Mitul Golani
2024-06-14 4:31 ` ✓ CI.Patch_applied: success for CMRR patch fixes Patchwork
2024-06-14 4:31 ` ✓ CI.checkpatch: " Patchwork
2024-06-14 4:32 ` ✓ CI.KUnit: " Patchwork
2024-06-14 4:44 ` ✓ CI.Build: " Patchwork
2024-06-14 4:46 ` ✗ CI.Hooks: failure " Patchwork
2024-06-14 4:47 ` ✗ CI.checksparse: warning " Patchwork
2024-06-14 5:09 ` ✓ CI.BAT: success " Patchwork
2024-06-14 8:58 ` ✗ CI.FULL: failure " Patchwork
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=ZmyfoMYRfKJv16KD@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=ankit.k.nautiyal@intel.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=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--cc=mripard@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=suraj.kandpal@intel.com \
--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