dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Archit Taneja <architt@codeaurora.org>
To: Jordan Crouse <jcrouse@codeaurora.org>,
	freedreno@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	bjorn.andersson@linaro.org
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/6] drm: msm: A5XX zap shader
Date: Thu, 20 Apr 2017 09:16:19 +0530	[thread overview]
Message-ID: <7255aa27-33c2-d4ee-2c5f-73241849b89b@codeaurora.org> (raw)
In-Reply-To: <1492031718-28477-1-git-send-email-jcrouse@codeaurora.org>



On 04/13/2017 02:45 AM, Jordan Crouse wrote:
> Hey Rob -
>
> Here is the stack of stuff to add the zap shader for msm-next. I left
> the code broken out as the first two changes are merged into the device
> specific tree and the third one has been seen before so this should
> hopefully cut down on confusion.
>
> The following patches are basically the changes that Bjorn requested and a bit
> more clean up to rely on the device tree less as is our current plan of action.
>
> I am not at all oppposed to squashing these into one big change or two moderate
> changes if it makes life easier.

For the series:

Tested-by: Archit Taneja <architt@codeaurora.org>

Thanks,
Archit

>
> Jordan Crouse (6):
>   drm/msm: Add a quick and dirty PIL loader
>   drm/msm: gpu: Use the zap shader on 5XX if we can
>   drm/msm: Improve the zap shader
>   drm/msm: Create a child device for the zap shader
>   drm/msm: Move zap shader firmware name to the device table
>   drm/msm: Document the zap-shader subnode for the GPU
>
>  .../devicetree/bindings/display/msm/gpu.txt        |  13 ++
>  drivers/gpu/drm/msm/adreno/a5xx_gpu.c              | 249 ++++++++++++++++++++-
>  drivers/gpu/drm/msm/adreno/a5xx_gpu.h              |   2 +
>  drivers/gpu/drm/msm/adreno/adreno_device.c         |   1 +
>  drivers/gpu/drm/msm/adreno/adreno_gpu.h            |   1 +
>  5 files changed, 264 insertions(+), 2 deletions(-)
>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

      parent reply	other threads:[~2017-04-20  3:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 21:15 [PATCH 0/6] drm: msm: A5XX zap shader Jordan Crouse
2017-04-12 21:15 ` [PATCH 1/6] drm/msm: Add a quick and dirty PIL loader Jordan Crouse
     [not found]   ` <1492031718-28477-2-git-send-email-jcrouse-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-17 19:57     ` Bjorn Andersson
     [not found] ` <1492031718-28477-1-git-send-email-jcrouse-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-12 21:15   ` [PATCH 2/6] drm/msm: gpu: Use the zap shader on 5XX if we can Jordan Crouse
     [not found]     ` <1492031718-28477-3-git-send-email-jcrouse-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-17 19:58       ` Bjorn Andersson
     [not found]         ` <20170417195807.GB12022-iTMlPVAvTYNoL7IsjepNBwq4bfNCki47rNQQ6b5fDX0@public.gmane.org>
2017-04-17 21:51           ` Jordan Crouse
     [not found]             ` <20170417215124.GA415-9PYrDHPZ2Orvke4nUoYGnHL1okKdlPRT@public.gmane.org>
2017-04-17 23:53               ` Bjorn Andersson
2017-04-12 21:15   ` [PATCH 6/6] drm/msm: Document the zap-shader subnode for the GPU Jordan Crouse
2017-04-17 19:57     ` Bjorn Andersson
2017-04-12 21:15 ` [PATCH 3/6] drm/msm: Improve the zap shader Jordan Crouse
2017-04-17 19:58   ` Bjorn Andersson
2017-04-12 21:15 ` [PATCH 4/6] drm/msm: Create a child device for " Jordan Crouse
2017-04-12 21:15 ` [PATCH 5/6] drm/msm: Move zap shader firmware name to the device table Jordan Crouse
2017-04-17 19:58   ` Bjorn Andersson
2017-04-17 19:57 ` [PATCH 0/6] drm: msm: A5XX zap shader Bjorn Andersson
2017-04-20  3:46 ` Archit Taneja [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=7255aa27-33c2-d4ee-2c5f-73241849b89b@codeaurora.org \
    --to=architt@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=jcrouse@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.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