public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: airlied@linux.ie, daniel.vetter@ffwll.ch, jianwei.wang.chn@gmail.com
Cc: alison.wang@freescale.com, mark.yao@rock-chips.com,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] drm/fsl-dcu: fixes and enhancements
Date: Thu, 25 Feb 2016 15:36:03 -0800	[thread overview]
Message-ID: <663a114ac495a84109fb9baad005252a@agner.ch> (raw)
In-Reply-To: <1447900970-15936-1-git-send-email-stefan@agner.ch>

On 2015-11-18 18:42, Stefan Agner wrote:
> During testing the DCU DRM driver on the Freescale Vybrid platform
> I came across some (platform independent) bugs and problems which
> this patchset addresses.
> 
> Note: To use the driver on Vybrid some platform/device-tree
> enhancements are needed which are not part of this patchset.
> I still need to clean those up.

Applied 1-6 to my tree:
http://git.agner.ch/gitweb/?p=linux-drm-fsl-dcu.git;a=shortlog;h=refs/heads/for-next

Will send out a pull request for that tree soonish.

> 
> Stefan Agner (7):
>   drm/fsl-dcu: specify volatile registers
>   drm/fsl-dcu: remove regmap return value checks
>   drm/fsl-dcu: avoid memory leak on errors
>   drm/fsl-dcu: handle initialization errors properly
>   drm/fsl-dcu: mask all interrupts on initialization
>   drm/fsl-dcu: fix alpha blending
>   drm/fsl-dcu: use mode flags for hsync/vsync pixelclk polarity
> 
>  drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c  | 143 +++++++++++-----------------
>  drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c   |  65 ++++++-------
>  drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.h   |   8 +-
>  drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_kms.c   |  24 ++++-
>  drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_plane.c | 137 ++++++++++++--------------
>  drivers/gpu/drm/panel/panel-simple.c        |   2 +
>  6 files changed, 171 insertions(+), 208 deletions(-)

      parent reply	other threads:[~2016-02-25 23:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19  2:42 [PATCH 0/7] drm/fsl-dcu: fixes and enhancements Stefan Agner
2015-11-19  2:42 ` [PATCH 1/7] drm/fsl-dcu: specify volatile registers Stefan Agner
2015-11-19  2:42 ` [PATCH 2/7] drm/fsl-dcu: remove regmap return value checks Stefan Agner
2015-11-19  2:42 ` [PATCH 3/7] drm/fsl-dcu: avoid memory leak on errors Stefan Agner
2015-11-19  2:42 ` [PATCH 4/7] drm/fsl-dcu: handle initialization errors properly Stefan Agner
2015-11-19  2:42 ` [PATCH 5/7] drm/fsl-dcu: mask all interrupts on initialization Stefan Agner
2015-11-19  2:42 ` [PATCH 6/7] drm/fsl-dcu: fix alpha blending Stefan Agner
2015-11-19  2:42 ` [PATCH 7/7] drm/fsl-dcu: use mode flags for hsync/vsync pixelclk polarity Stefan Agner
2016-01-28  2:46   ` Stefan Agner
2016-02-03 14:00     ` Thierry Reding
2016-02-03 23:18       ` Stefan Agner
2016-02-04 20:31         ` Stefan Agner
2016-02-03 14:04     ` Thierry Reding
2016-02-03 23:30       ` Stefan Agner
2016-02-25 23:36 ` Stefan Agner [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=663a114ac495a84109fb9baad005252a@agner.ch \
    --to=stefan@agner.ch \
    --cc=airlied@linux.ie \
    --cc=alison.wang@freescale.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jianwei.wang.chn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.yao@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox