All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jyri Sarha <jsarha@ti.com>
To: "airlied@linux.ie" <airlied@linux.ie>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Cc: "Valkeinen, Tomi" <tomi.valkeinen@ti.com>
Subject: [GIT PULL] drm/tilcdc: Accumulated fixes over the past couple of years
Date: Thu, 25 Feb 2016 18:14:51 +0200	[thread overview]
Message-ID: <56CF287B.8080201@ti.com> (raw)

Hi Dave,
Here is a long list of tilcdc fixes that were reviewed by Tomi Valkeinen 
here:
https://lists.freedesktop.org/archives/dri-devel/2016-February/101649.html

The fixes are on top of commit 0041ee4d3642f9ad80a479fbe51a4bc7f3cd8294: 
Merge branch 'drm/next/du' of git://linuxtv.org/pinchartl/fbdev into 
drm-next

and they are available at:

https://github.com/jsarha/linux.git drm-tilcdc-next-fixes-2015-02-25

The top most commit is d0ec32caef0baa490b419895ef61c8481d49f7cd: 
drm/tilcdc: Use devm_kzalloc() and devm_kcalloc() for private data

Best regards,
Jyri
-----------------------------------------------------------------------

Darren Etheridge (4):
   drm/tilcdc: rewrite pixel clock calculation
   drm/tilcdc: fix kernel panic on suspend when no hdmi monitor connected
   drm/tilcdc: make frame_done interrupt active at all times
   drm/tilcdc: disable the lcd controller/dma engine when suspend invoked

Dave Gerlach (1):
   drm/tilcdc: adopt pinctrl support

Grygorii Strashko (1):
   drm/tilcdc: fix build error when !CONFIG_CPU_FREQ

Jyri Sarha (8):
   drm/tilcdc: Implement dma-buf support for tilcdc
   drm/tilcdc: Allocate register storage based on the actual number
     registers
   drm/tilcdc: Fix interrupt enable/disable code for version 2 tilcdc
   drm/tilcdc: Remove the duplicate LCDC_INT_ENABLE_SET_REG in
     registers[]
   drm/tilcdc: Add prints on sync lost and FIFO underrun interrupts
   drm/tilcdc: Disable sync lost interrupt if it fires on every frame
   drm/tilcdc: Initialize crtc->port
   drm/tilcdc: Use devm_kzalloc() and devm_kcalloc() for private data

Tomi Valkeinen (8):
   drm/tilcdc: verify fb pitch
   drm/tilcdc: cleanup runtime PM handling
   drm/tilcdc: disable crtc on unload
   drm/tilcdc: split reset to a separate function
   drm/tilcdc: remove broken error handling
   drm/tilcdc: cleanup irq handling
   drm/tilcdc: Get rid of complex ping-pong mechanism
   drm/tilcdc: Do not update the next frame buffer close to vertical
     blank

  drivers/gpu/drm/tilcdc/tilcdc_crtc.c   | 313 
++++++++++++++++++++++-----------
  drivers/gpu/drm/tilcdc/tilcdc_drv.c    | 130 ++++++++------
  drivers/gpu/drm/tilcdc/tilcdc_drv.h    |   5 +-
  drivers/gpu/drm/tilcdc/tilcdc_panel.c  |  20 +--
  drivers/gpu/drm/tilcdc/tilcdc_tfp410.c |  24 +--
  5 files changed, 300 insertions(+), 192 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-02-25 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 16:14 Jyri Sarha [this message]
2016-02-25 16:22 ` [GIT PULL] drm/tilcdc: Accumulated fixes over the past couple of years Tomi Valkeinen
2016-03-07 14:52 ` [GIT PULL Resend] tilcdc changes for 4.6 Jyri Sarha

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=56CF287B.8080201@ti.com \
    --to=jsarha@ti.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=tomi.valkeinen@ti.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.