From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Anusha Srivatsa <anusha.srivatsa@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gvt: Add missing macro name changes
Date: Mon, 24 May 2021 13:59:36 +0800 [thread overview]
Message-ID: <20210524055936.GE27293@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <20210521181229.4700-1-anusha.srivatsa@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1759 bytes --]
On 2021.05.21 11:12:29 -0700, Anusha Srivatsa wrote:
> Propagate changes to macros name containing CSR_*
> to DMC_* from display side.
>
> Cc: intel-gvt-dev@lists.freedesktop.org
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
> ---
> drivers/gpu/drm/i915/gvt/handlers.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gvt/handlers.c b/drivers/gpu/drm/i915/gvt/handlers.c
> index dda320749c65..33496397a74f 100644
> --- a/drivers/gpu/drm/i915/gvt/handlers.c
> +++ b/drivers/gpu/drm/i915/gvt/handlers.c
> @@ -3342,9 +3342,9 @@ static int init_skl_mmio_info(struct intel_gvt *gvt)
> MMIO_D(_MMIO(_PLANE_SURF_3_A), D_SKL_PLUS);
> MMIO_D(_MMIO(_PLANE_SURF_3_B), D_SKL_PLUS);
>
> - MMIO_D(CSR_SSP_BASE, D_SKL_PLUS);
> - MMIO_D(CSR_HTP_SKL, D_SKL_PLUS);
> - MMIO_D(CSR_LAST_WRITE, D_SKL_PLUS);
> + MMIO_D(DMC_SSP_BASE, D_SKL_PLUS);
> + MMIO_D(DMC_HTP_SKL, D_SKL_PLUS);
> + MMIO_D(DMC_LAST_WRITE, D_SKL_PLUS);
>
> MMIO_DFH(BDW_SCRATCH1, D_SKL_PLUS, F_CMD_ACCESS, NULL, NULL);
>
> @@ -3655,7 +3655,7 @@ void intel_gvt_clean_mmio_info(struct intel_gvt *gvt)
> * otherwise, need to update cmd_reg_handler in cmd_parser.c
> */
> static struct gvt_mmio_block mmio_blocks[] = {
> - {D_SKL_PLUS, _MMIO(CSR_MMIO_START_RANGE), 0x3000, NULL, NULL},
> + {D_SKL_PLUS, _MMIO(DMC_MMIO_START_RANGE), 0x3000, NULL, NULL},
> {D_ALL, _MMIO(MCHBAR_MIRROR_BASE_SNB), 0x40000, NULL, NULL},
> {D_ALL, _MMIO(VGT_PVINFO_PAGE), VGT_PVINFO_SIZE,
> pvinfo_mmio_read, pvinfo_mmio_write},
> --
Sorry that I missed your fix before sending mine...
Reviewed-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Thanks!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-05-24 6:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 18:12 [Intel-gfx] [PATCH] drm/i915/gvt: Add missing macro name changes Anusha Srivatsa
2021-05-21 18:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gvt: Add missing macro name changes (rev2) Patchwork
2021-05-24 1:28 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-05-24 5:59 ` Zhenyu Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-21 17:40 [Intel-gfx] [PATCH] drm/i915/gvt: Add missing macro name changes Anusha Srivatsa
2021-05-22 6:43 ` Lucas De Marchi
2021-05-23 19:17 ` Dave Airlie
2021-05-24 9:19 ` Jani Nikula
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=20210524055936.GE27293@zhen-hp.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=anusha.srivatsa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
/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