From: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
To: linux-renesas-soc@vger.kernel.org, niklas.soderlund@ragnatech.se
Cc: linux-media@vger.kernel.org, magnus.damm@gmail.com,
laurent.pinchart@ideasonboard.com, hans.verkuil@cisco.com,
ian.molton@codethink.co.uk, lars@metafoo.de,
william.towle@codethink.co.uk,
Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
Subject: [PATCH/RFC 0/9] Lager board HDMI input support
Date: Wed, 17 Feb 2016 16:48:36 +0100 [thread overview]
Message-ID: <1455724125-13004-1-git-send-email-ulrich.hecht+renesas@gmail.com> (raw)
Hi!
This series implements Lager HDMI input support on top of Niklas's herculean
rewrite of the rcar-vin driver ("[media] rcar-vin: add Renesas R-Car VIN IP
core").
A couple of the included patches are pushed or have been picked up elsewhere
already and are included here for ease of testing.
The EDID initialization blob has been lifted wholesale from the cobalt
driver, with only the vendor ID adjusted to "REN".
(Note for testing: To get up-to-date DV timings, you have to use a client
that does QUERY_DV_TIMINGS/S_DV_TIMINGS. Few do.)
CU
Uli
Ian Molton (1):
ARM: shmobile: lager dts: specify default-input for ADV7612
Laurent Pinchart (1):
v4l: subdev: Add pad config allocator and init
Ulrich Hecht (5):
adv7604: fix SPA register location for ADV7612
media: rcar_vin: Use correct pad number in try_fmt
media: rcar-vin: pad-aware driver initialisation
media: rcar-vin: add DV timings support
media: rcar-vin: initialize EDID data
William Towle (2):
media: adv7604: automatic "default-input" selection
ARM: shmobile: lager dts: Add entries for VIN HDMI input support
arch/arm/boot/dts/r8a7790-lager.dts | 41 +++++++-
drivers/media/i2c/adv7604.c | 27 ++++--
drivers/media/platform/rcar-vin/rcar-dma.c | 145 ++++++++++++++++++++++++++++-
drivers/media/platform/rcar-vin/rcar-vin.h | 1 +
drivers/media/v4l2-core/v4l2-subdev.c | 19 +++-
include/media/v4l2-subdev.h | 10 ++
6 files changed, 229 insertions(+), 14 deletions(-)
--
2.6.4
next reply other threads:[~2016-02-17 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 15:48 Ulrich Hecht [this message]
2016-02-17 15:48 ` [PATCH/RFC 1/9] v4l: subdev: Add pad config allocator and init Ulrich Hecht
2016-02-17 15:48 ` [PATCH/RFC 2/9] media: adv7604: automatic "default-input" selection Ulrich Hecht
2016-02-17 15:48 ` [PATCH/RFC 3/9] adv7604: fix SPA register location for ADV7612 Ulrich Hecht
2016-02-17 15:48 ` [PATCH/RFC 4/9] media: rcar_vin: Use correct pad number in try_fmt Ulrich Hecht
2016-02-17 15:48 ` [PATCH/RFC 5/9] media: rcar-vin: pad-aware driver initialisation Ulrich Hecht
2016-02-17 15:48 ` [PATCH/RFC 6/9] media: rcar-vin: add DV timings support Ulrich Hecht
2016-02-17 15:48 ` [PATCH/RFC 7/9] media: rcar-vin: initialize EDID data Ulrich Hecht
2016-02-17 15:48 ` [PATCH/RFC 8/9] ARM: shmobile: lager dts: Add entries for VIN HDMI input support Ulrich Hecht
2016-02-17 15:48 ` [PATCH/RFC 9/9] ARM: shmobile: lager dts: specify default-input for ADV7612 Ulrich Hecht
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=1455724125-13004-1-git-send-email-ulrich.hecht+renesas@gmail.com \
--to=ulrich.hecht+renesas@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=ian.molton@codethink.co.uk \
--cc=lars@metafoo.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=william.towle@codethink.co.uk \
/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).