dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: airlied@linux.ie
Cc: dri-devel@lists.freedesktop.org
Subject: [GIT PULL] TDA998x I2C driver fixes
Date: Fri, 7 Feb 2014 20:38:23 +0000	[thread overview]
Message-ID: <20140207203823.GA5681@rmk-PC.arm.linux.org.uk> (raw)

David,

Please incorporate the latest TDA998x I2C driver fixes, which can be found at:

  git://ftp.arm.linux.org.uk/~rmk/linux-cubox.git tda998x-fixes

with SHA1 2e9a3fc3a360ac180f5b4c3c4416a0d0dec60dd8, based on v3.13.

These are a number of fixes from the patch set which Jean-Francois has
been working on which I think are important to be merged during -rc, and
have been tested independently here.  I've been in discussion with Rob,
who is happy that I send these directly to you.

Test merging this with v3.14-rc1 shows no conflicts.

This will update the following files:

 drivers/gpu/drm/i2c/tda998x_drv.c | 17 +++++++++++++----
 1 file changed, 13 insertions(+), 4 deletions(-)

through these changes:

Jean-Francois Moine (6):
      drm/i2c: tda998x: fix bad value in the AIF
      drm/i2c: tda998x: check the CEC device creation
      drm/i2c: tda998x: free the CEC device on encoder_destroy
      drm/i2c: tda998x: force the page register at startup time
      drm/i2c: tda998x: set the PLL division factor in range 0..3
      drm/i2c: tda998x: fix the ENABLE_SPACE register

Thanks.

             reply	other threads:[~2014-02-07 20:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07 20:38 Russell King [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-21 14:54 [GIT PULL] TDA998x I2C driver fixes Russell King
2015-08-05 22:14 Russell King
2015-08-06 14:16 ` Daniel Vetter
2015-08-06 14:31   ` Russell King
2015-08-06 14:44     ` Alex Deucher
2015-08-06 14:52       ` Daniel Vetter

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=20140207203823.GA5681@rmk-PC.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.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