From: Russell King <rmk@armlinux.org.uk>
To: David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.freedesktop.org, Jyri Sarha <jsarha@ti.com>
Subject: [RESEND][GIT PULL] TDA998x I2C driver development updates
Date: Wed, 19 Oct 2016 17:37:18 +0100 [thread overview]
Message-ID: <20161019163718.GA27432@rmk-PC.arm.linux.org.uk> (raw)
David,
Please incorporate the latest TDA998x I2C driver development updates,
which can be found at:
git://git.armlinux.org.uk/~rmk/linux-arm.git drm-tda998x-devel
with SHA1 df0bd1e8f3c508bf4c3445f94b12e38289b65f13.
This was sent on the 9th September, and I was hoping that it was going
to make 4.9-rc1 as TI want it in, but it appears that it was never
picked up. What's going on? Should I queue this (and my other DRM
changes) for Linus myself?
This will update the following files:
.../devicetree/bindings/display/bridge/tda998x.txt | 18 ++
arch/arm/boot/dts/am335x-boneblack.dts | 71 ++++-
drivers/gpu/drm/i2c/Kconfig | 1 +
drivers/gpu/drm/i2c/tda998x_drv.c | 297 ++++++++++++++++++---
include/drm/i2c/tda998x.h | 29 +-
include/dt-bindings/display/tda998x.h | 7 +
6 files changed, 368 insertions(+), 55 deletions(-)
create mode 100644 include/dt-bindings/display/tda998x.h
through these changes:
Jyri Sarha (3):
drm/i2c: tda998x: Improve tda998x_configure_audio() audio related pdata
drm/i2c: tda998x: Register ASoC hdmi-codec and add audio DT binding
ARM: dts: am335x-boneblack: Add HDMI audio support
Russell King (1):
Merge commit 'efc9194bcff84' ("ASoC: hdmi-codec: callback function will be called with private data") into drm-tda998x-devel
Many thanks.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-10-19 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 16:37 Russell King [this message]
2016-10-19 18:24 ` [RESEND][GIT PULL] TDA998x I2C driver development updates Russell King
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=20161019163718.GA27432@rmk-PC.arm.linux.org.uk \
--to=rmk@armlinux.org.uk \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@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