All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
To: Rob Herring <robh@kernel.org>
Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Steven Price <steven.price@arm.com>
Subject: Re: [PATCH] drm/panfrost: Add "compute shader only" hint
Date: Tue, 6 Aug 2019 13:25:46 -0700	[thread overview]
Message-ID: <20190806202546.GA4872@kevin> (raw)
In-Reply-To: <CAL_JsqLfiYScsBGe4C=n=WVTP+bNwig7HruO7FvrSsHqD5mEkg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 573 bytes --]

> > It's not obvious to me when it actually needs to be enabled. Besides the
> > errata, it's only when... device_nr=1 for a compute-only job in kbase?
> >
> > I'm afraid I don't know nearly enough about how kbase plumbs CL to grok
> > the signifiance...
> 
> Figuring out the nr_core_groups was the complicated part of this as I
> recall. Seems like we should at least figure out if we (or will need)
> PANFROST_JD_REQ_CORE_GRP_MASK added to the UAPI as well.

I suspect this is something OpenCL/Vulkan specific. Hopefully Stephen
can shine some light here :)

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-08-06 20:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 19:52 [PATCH] drm/panfrost: Add "compute shader only" hint Alyssa Rosenzweig
2019-08-06 20:01 ` Rob Herring
2019-08-06 20:11   ` Alyssa Rosenzweig
2019-08-06 20:21     ` Rob Herring
2019-08-06 20:25       ` Alyssa Rosenzweig [this message]
2019-08-07 11:11         ` Steven Price
2019-08-07 14:19           ` Alyssa Rosenzweig

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=20190806202546.GA4872@kevin \
    --to=alyssa.rosenzweig@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robh@kernel.org \
    --cc=steven.price@arm.com \
    --cc=tomeu.vizoso@collabora.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.