From: Marek Belisko <marek@goldelico.com>
To: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
bcousson@baylibre.com, tony@atomide.com, linux@arm.linux.org.uk,
tomi.valkeinen@ti.com, plagnioj@jcrosoft.com,
grant.likely@linaro.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-fbdev@vger.kernel.org, hns@goldelico.com,
gta04-owner@goldelico.com, Marek Belisko <marek@goldelico.com>
Subject: [PATCH v2 0/5] omapdss: Add video output support for gta04 board
Date: Wed, 12 Nov 2014 23:10:42 +0100 [thread overview]
Message-ID: <1415830247-31633-1-git-send-email-marek@goldelico.com> (raw)
This patch series adds support for video output on gta04 board. It consist
of opa362 video amplifier driver + DT bindings, adding venc -> opa362 -> svideo-connecor
setup in DT and finally static setup for tvbypass anc acbias in devconf1 register
via pinctrl subsystem.
Changes from v1:
- fix opa362 compilation error
- fix opa362 DT documentation
- move devconf1 definition to omap3.dtsi
Marek Belisko (5):
video: omapdss: Add opa362 driver
Documentation: DT: Add documentation for ti,opa362 bindings
arm: dts: omap3-gta04: Add handling for tv output
arm: dts: omap3: Add definition for devconf1 register
arm: dts: omap3-gta04: Add static configuration for devconf1 register
.../devicetree/bindings/video/ti,opa362.txt | 38 +++
arch/arm/boot/dts/omap3-gta04.dtsi | 59 ++++
arch/arm/boot/dts/omap3.dtsi | 13 +
arch/arm/boot/dts/omap34xx.dtsi | 4 +
arch/arm/boot/dts/omap36xx.dtsi | 4 +
drivers/video/fbdev/omap2/displays-new/Kconfig | 6 +
drivers/video/fbdev/omap2/displays-new/Makefile | 1 +
.../fbdev/omap2/displays-new/amplifier-opa362.c | 343 +++++++++++++++++++++
include/video/omap-panel-data.h | 12 +
9 files changed, 480 insertions(+)
create mode 100644 Documentation/devicetree/bindings/video/ti,opa362.txt
create mode 100644 drivers/video/fbdev/omap2/displays-new/amplifier-opa362.c
--
1.9.1
next reply other threads:[~2014-11-12 22:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 22:10 Marek Belisko [this message]
2014-11-12 22:10 ` [PATCH v2 1/5] video: omapdss: Add opa362 driver Marek Belisko
2014-11-13 11:51 ` Tomi Valkeinen
2014-11-13 16:25 ` Dr. H. Nikolaus Schaller
2014-11-13 16:41 ` Tomi Valkeinen
2014-11-19 15:10 ` Dr. H. Nikolaus Schaller
2014-11-24 11:47 ` Tomi Valkeinen
2014-11-12 22:10 ` [PATCH v2 2/5] Documentation: DT: Add documentation for ti,opa362 bindings Marek Belisko
2014-11-12 22:10 ` [PATCH v2 3/5] arm: dts: omap3-gta04: Add handling for tv output Marek Belisko
2014-11-12 22:10 ` [PATCH v2 4/5] arm: dts: omap3: Add definition for devconf1 register Marek Belisko
2014-11-12 22:10 ` [PATCH v2 5/5] arm: dts: omap3-gta04: Add static configuration " Marek Belisko
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=1415830247-31633-1-git-send-email-marek@goldelico.com \
--to=marek@goldelico.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gta04-owner@goldelico.com \
--cc=hns@goldelico.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=plagnioj@jcrosoft.com \
--cc=robh+dt@kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).