dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Tomeu Vizoso
	<tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
Subject: [GIT PULL] drm/tegra: Fixes for v3.20-rc1
Date: Thu, 19 Feb 2015 14:33:18 +0100	[thread overview]
Message-ID: <1424352798-6809-1-git-send-email-thierry.reding@gmail.com> (raw)

Hi Dave,

The following changes since commit 45ee2dbc65cbf6910892c480e6f428be342fa733:

  Merge branch 'drm-next-3.20' of git://people.freedesktop.org/~agd5f/linux into drm-next (2015-02-16 13:55:49 +1000)

are available in the git repository at:

  git://anongit.freedesktop.org/tegra/linux tags/drm/tegra/for-3.20-rc1-fixes

for you to fetch changes up to 07d05cbf60ed8f06c61484d3d85c06c1aa7edf38:

  drm/tegra: dc: Move more code into ->init() (2015-02-19 14:21:51 +0100)

Thanks,
Thierry

----------------------------------------------------------------
drm/tegra: Fixes for v3.20-rc1

This fixes a bit of fallout that was caused by the atomic modesetting
driver conversion and some last-minute changes in the DRM atomic core.
It also fixes a bug exposed by recent changes in the clock framework
which results in non-working HDMI.

----------------------------------------------------------------
Thierry Reding (4):
      drm/tegra: hdmi: Explicitly set clock rate
      drm/tegra: dc: Reset state's active_changed field
      drm/tegra: dc: Wire up CRTC parent of atomic state
      drm/tegra: dc: Move more code into ->init()

 drivers/gpu/drm/tegra/dc.c   | 79 ++++++++++++++++++++++----------------------
 drivers/gpu/drm/tegra/hdmi.c |  8 +++++
 2 files changed, 48 insertions(+), 39 deletions(-)

                 reply	other threads:[~2015-02-19 13:33 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=1424352798-6809-1-git-send-email-thierry.reding@gmail.com \
    --to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
    /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