From: Alex Deucher <alexdeucher@gmail.com>
To: Emily Deng <Emily.Deng@amd.com>
Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/4] SWDEV-227605 - Virtual display need to support multiple ctrcs
Date: Wed, 25 Mar 2020 10:22:44 -0400 [thread overview]
Message-ID: <CADnq5_OMPSue71RZAB1wnbYGUNdHdPByAR_tJTGoQNKmnL1MgQ@mail.gmail.com> (raw)
In-Reply-To: <1585124676-14143-1-git-send-email-Emily.Deng@amd.com>
Please fix the subject to be "drm/amdgpu: " rather than SWDEV-....
Alex
On Wed, Mar 25, 2020 at 4:24 AM Emily Deng <Emily.Deng@amd.com> wrote:
>
> The crtc num is determined by virtual_display parameter.
>
> Signed-off-by: Emily Deng <Emily.Deng@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c
> index 43a1ee3..d791bfe 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c
> @@ -38,7 +38,8 @@ bool amdgpu_virt_mmio_blocked(struct amdgpu_device *adev)
> void amdgpu_virt_init_setting(struct amdgpu_device *adev)
> {
> /* enable virtual display */
> - adev->mode_info.num_crtc = 1;
> + if (adev->mode_info.num_crtc == 0)
> + adev->mode_info.num_crtc = 1;
> adev->enable_virtual_display = true;
> adev->ddev->driver->driver_features &= ~DRIVER_ATOMIC;
> adev->cg_flags = 0;
> --
> 2.7.4
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2020-03-25 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 8:24 [PATCH 1/4] SWDEV-227605 - Virtual display need to support multiple ctrcs Emily Deng
2020-03-25 10:48 ` Liu, Monk
2020-03-25 14:22 ` Alex Deucher [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=CADnq5_OMPSue71RZAB1wnbYGUNdHdPByAR_tJTGoQNKmnL1MgQ@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=Emily.Deng@amd.com \
--cc=amd-gfx@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;
as well as URLs for NNTP newsgroup(s).