On Wed 12 Apr 14:15 PDT 2017, 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.

Keeping patches in a series separate makes sense when they show the
individual steps of a transition and thereby acting as documentation for
future readers of the git log.

But there's little value in documenting the steps that development took,
so please squash the code into commits that will look meaningful in the
git log.

(And then the DT binding patch should be kept separate, for process


> 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(-)
> -- 
> 1.9.1
Freedreno mailing list

Reply via email to