From: "Michel Dänzer" <michel@daenzer.net>
To: Oded Gabbay <oded.gabbay@amd.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/radeon: Changing number of compute pipe lines
Date: Thu, 12 Mar 2015 18:04:50 +0900 [thread overview]
Message-ID: <550156B2.4090002@daenzer.net> (raw)
In-Reply-To: <1426150125-16509-1-git-send-email-oded.gabbay@amd.com>
On 12.03.2015 17:48, Oded Gabbay wrote:
> From: Ben Goz <ben.goz@amd.com>
>
> The current CP firmware can handle Usermode Queues only on MEC1.
> To reflect this firmware change, this commit reduces number of compute pipelines
> to 4 - 1, from 8 - 1 (the first pipeline is allocated for kgd).
>
> Signed-off-by: Ben Goz <ben.goz@amd.com>
> Signed-off-by: Oded Gabbay <oded.gabbay@amd.com>
> ---
> drivers/gpu/drm/radeon/radeon_kfd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_kfd.c b/drivers/gpu/drm/radeon/radeon_kfd.c
> index 061eaa9..122eb56 100644
> --- a/drivers/gpu/drm/radeon/radeon_kfd.c
> +++ b/drivers/gpu/drm/radeon/radeon_kfd.c
> @@ -153,7 +153,7 @@ void radeon_kfd_device_init(struct radeon_device *rdev)
> .compute_vmid_bitmap = 0xFF00,
>
> .first_compute_pipe = 1,
> - .compute_pipe_count = 8 - 1,
> + .compute_pipe_count = 4 - 1,
> };
>
> radeon_doorbell_get_kfd_info(rdev,
>
Does this need to be backported to 3.19? (Does the current CP microcode
work with 3.19?)
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-03-12 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 8:48 [PATCH] drm/radeon: Changing number of compute pipe lines Oded Gabbay
2015-03-12 9:04 ` Michel Dänzer [this message]
2015-03-12 9:08 ` Oded Gabbay
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=550156B2.4090002@daenzer.net \
--to=michel@daenzer.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=oded.gabbay@amd.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 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.