From: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
To: horms@verge.net.au
Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
magnus.damm@gmail.com, laurent.pinchart@ideasonboard.com,
hans.verkuil@cisco.com, william.towle@codethink.co.uk,
niklas.soderlund@ragnatech.se, geert@linux-m68k.org,
sergei.shtylyov@cogentembedded.com,
Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
Subject: [PATCH v2 0/2] Renesas Lager/Koelsch HDMI input
Date: Tue, 18 Oct 2016 17:01:32 +0200 [thread overview]
Message-ID: <1476802894-5105-1-git-send-email-ulrich.hecht+renesas@gmail.com> (raw)
Hi!
This series enables HDMI input on the Lager and Koelsch boards.
It sits on renesas-next-20161017-v4.9-rc1.
I have tried to address all concerns raised by reviewers (correctly, I hope),
see below for details.
CU
Uli
Changes since v1:
- modeled decoder inputs/outputs and connectors
- removed unnecessary "remote" nodes
- r8a7790-lager.dts: "ok" -> "okay"
- r8a7791-koelsch.dts: set ADV7612 interrupt to GP4_2
Hans Verkuil (1):
ARM: dts: koelsch: add HDMI input
William Towle (1):
ARM: dts: lager: Add entries for VIN HDMI input support
arch/arm/boot/dts/r8a7790-lager.dts | 66 ++++++++++++++++++++++++++++++++--
arch/arm/boot/dts/r8a7791-koelsch.dts | 68 +++++++++++++++++++++++++++++++++--
2 files changed, 130 insertions(+), 4 deletions(-)
--
2.7.4
next reply other threads:[~2016-10-18 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 15:01 Ulrich Hecht [this message]
2016-10-18 15:01 ` [PATCH v2 1/2] ARM: dts: lager: Add entries for VIN HDMI input support Ulrich Hecht
2016-10-18 15:01 ` [PATCH v2 2/2] ARM: dts: koelsch: add HDMI input Ulrich Hecht
2016-10-19 7:33 ` Geert Uytterhoeven
2016-10-20 8:46 ` Simon Horman
2016-10-18 15:17 ` [PATCH v2 0/2] Renesas Lager/Koelsch " Laurent Pinchart
2016-10-20 8:46 ` Simon Horman
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=1476802894-5105-1-git-send-email-ulrich.hecht+renesas@gmail.com \
--to=ulrich.hecht+renesas@gmail.com \
--cc=geert@linux-m68k.org \
--cc=hans.verkuil@cisco.com \
--cc=horms@verge.net.au \
--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=sergei.shtylyov@cogentembedded.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.