lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 18 Nov 2015 18:42:43 -0800
From:	Stefan Agner <stefan@...er.ch>
To:	airlied@...ux.ie, daniel.vetter@...ll.ch,
	jianwei.wang.chn@...il.com
Cc:	alison.wang@...escale.com, mark.yao@...k-chips.com,
	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	Stefan Agner <stefan@...er.ch>
Subject: [PATCH 0/7] drm/fsl-dcu: fixes and enhancements

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.

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(-)

-- 
2.6.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists