dri-devel.lists.freedesktop.org archive mirror
 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: Kevin Hilman <khilman@baylibre.com>,
	"Valkeinen, Tomi" <tomi.valkeinen@ti.com>
Subject: [GIT PULL] tilcdc fixes 2 for 4.9
Date: Wed, 7 Sep 2016 16:07:09 +0300	[thread overview]
Message-ID: <5f8dba57-6b69-06a2-1f10-3dd1b76b6698@ti.com> (raw)

Hi Dave,

Please pull these collected fixes and cleanups from various sources.

This pull request contains my earlier pull request on with tag
tilcdc-4.9-fixes, so pulling this alone is enough. They both have the
same base and commit ids so it does not matter if you pulled the other
one already earlier.

Thanks,

Jyri

The following changes since commit 2b2fd56d7e92f134ecaae5c89e20f64dd0f95aa2:

  Revert "drm: make DRI1 drivers depend on BROKEN" (2016-09-01 06:16:12
+1000)

are available in the git repository at:

  https://github.com/jsarha/linux tags/tilcdc-4.9-fixes-2

for you to fetch changes up to 2e0965b06d90b9dba76198d026c4c2ee04443aca:

  drm/tilcdc: WARN if CRTC is touched without CRTC lock (2016-09-07
15:54:43 +0300)

----------------------------------------------------------------
Fixes and cleanups for v4.9

----------------------------------------------------------------
Jyri Sarha (10):
      drm/tilcdc: Remove drm_helper_disable_unused_functions() call
      drm/tilcdc: Write DMA base and ceiling address with single instruction
      drm/tilcdc: Add blue-and-red-crossed devicetree property
      drm/tilcdc: Choose console BPP that supports RGB
      drm/tilcdc: Take crtc modeset lock while updating the crtc clock rate
      drm/tilcdc: Clean up LCDC functional clock rate setting code
      drm/tilcdc: Flush flip-work workqueue before drm_flip_work_cleanup()
      drm/tilcdc: Remove unnecessary tilcdc_crtc_disable() from
tilcdc_unload()
      drm/tilcdc: Take CRTC lock when calling tilcdc_crtc_disable()
      drm/tilcdc: WARN if CRTC is touched without CRTC lock

Karl Beldan (2):
      drm/tilcdc: Adjust the FB_CEILING address
      drm/tilcdc: Enable EOF interrupts for v1 LCDC

Teresa Remmet (1):
      drm/tilcdc: Fix check for remote port parent

 .../devicetree/bindings/display/tilcdc/tilcdc.txt  |  22 +++++
 drivers/gpu/drm/tilcdc/tilcdc_crtc.c               | 103
++++++++++++++-------
 drivers/gpu/drm/tilcdc/tilcdc_drv.c                |  69 ++++++++++----
 drivers/gpu/drm/tilcdc/tilcdc_drv.h                |   6 +-
 drivers/gpu/drm/tilcdc/tilcdc_external.c           |   9 +-
 drivers/gpu/drm/tilcdc/tilcdc_external.h           |   2 +-
 drivers/gpu/drm/tilcdc/tilcdc_panel.c              |   2 -
 drivers/gpu/drm/tilcdc/tilcdc_plane.c              |   9 +-
 drivers/gpu/drm/tilcdc/tilcdc_regs.h               |  14 +++
 drivers/gpu/drm/tilcdc/tilcdc_tfp410.c             |   2 -
 10 files changed, 166 insertions(+), 72 deletions(-)


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

                 reply	other threads:[~2016-09-07 13:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5f8dba57-6b69-06a2-1f10-3dd1b76b6698@ti.com \
    --to=jsarha@ti.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=khilman@baylibre.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).