From: Jagan Teki <jagan@amarulasolutions.com>
To: Kever Yang <kever.yang@rock-chips.com>,
Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
Cc: u-boot@lists.denx.de, linux-amarula@amarulasolutions.com,
linux-rockchip@lists.infradead.org
Subject: [PATCH 0/4] rockchip: rk3399: Fix HDMI out
Date: Thu, 23 Jan 2020 21:58:41 +0530 [thread overview]
Message-ID: <20200123162845.10651-1-jagan@amarulasolutions.com> (raw)
Due to recent Linux dts(i) sync for rk3399. the existing
vop driver is not working with HDMI out on RK3399.
These patches fixing the same and enabled HDMI out new boards.
Any inputs?
Jagan.
Jagan Teki (4):
arm64: dts: rk3399-u-boot: Delete vop assigned-clocks/rates
video: rockchip: Fix vop modes for rk3399
rockchip: Enable pre console for rk3399
rockchip: Enable HDMI output on rk3399 board w/ HDMI
arch/arm/dts/rk3399-u-boot.dtsi | 4 ++++
arch/arm/include/asm/arch-rockchip/vop_rk3288.h | 11 +++++++++++
arch/arm/mach-rockchip/Kconfig | 1 +
common/Kconfig | 1 +
configs/nanopc-t4-rk3399_defconfig | 6 ++++++
configs/nanopi-m4-rk3399_defconfig | 6 ++++++
configs/nanopi-neo4-rk3399_defconfig | 6 ++++++
configs/roc-pc-rk3399_defconfig | 6 ++++++
drivers/video/rockchip/rk3399_vop.c | 2 --
drivers/video/rockchip/rk_vop.c | 4 ++++
include/configs/evb_rk3399.h | 5 +++++
11 files changed, 50 insertions(+), 2 deletions(-)
--
2.18.0.321.gffc6fa0e3
next reply other threads:[~2020-01-23 16:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 16:28 Jagan Teki [this message]
[not found] ` <20200123162845.10651-1-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2020-01-23 16:28 ` [PATCH 1/4] arm64: dts: rk3399-u-boot: Delete vop assigned-clocks/rates Jagan Teki
2020-01-23 16:28 ` [PATCH 2/4] video: rockchip: Fix vop modes for rk3399 Jagan Teki
2020-01-23 16:28 ` [PATCH 3/4] rockchip: Enable pre console " Jagan Teki
2020-01-23 16:28 ` [PATCH 4/4] rockchip: Enable HDMI output on rk3399 board w/ HDMI Jagan Teki
2020-01-24 15:27 ` Tom Rini
2020-01-24 17:03 ` Anatolij Gustschin
2020-02-03 11:25 ` Jagan Teki
2020-02-03 14:47 ` Tom Rini
2020-02-03 22:10 ` Anatolij Gustschin
2020-03-02 13:01 ` Peter Robinson
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=20200123162845.10651-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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