From: Anatolij Gustschin <agust@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: "open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
U-Boot-Denx <u-boot@lists.denx.de>,
linux-amarula <linux-amarula@amarulasolutions.com>
Subject: Re: [PATCH 4/4] rockchip: Enable HDMI output on rk3399 board w/ HDMI
Date: Mon, 3 Feb 2020 23:10:55 +0100 [thread overview]
Message-ID: <20200203231055.0a3732b6@crub> (raw)
In-Reply-To: <20200203144708.GK13379@bill-the-cat>
On Mon, 3 Feb 2020 09:47:08 -0500
Tom Rini trini@konsulko.com wrote:
...
> > yes, this evb board config is common across most of the rk3399
> > defconfig boards. this patch enable hdmi on few rk3399 boards all use
> > same config file, evb_rk3399.h
>
> Yes, the ROCKCHIP_DEVICE_SETTINGS part makes sense, but the rest looks
> very much like part of we need to rework the commit I mentioned. I
> don't object to this going in as-is. Anatolij, how goes the rework of
> things however? I do want to see that get in sooner rather than later
> so we can sort out other regressions from just a lack of CONFIG options
> being enabled. Thanks!
A patch [1] for this is under build testing.
[1] http://patchwork.ozlabs.org/patch/1233033
--
Anatolij
next prev parent reply other threads:[~2020-02-03 22:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 16:28 [PATCH 0/4] rockchip: rk3399: Fix HDMI out Jagan Teki
[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 [this message]
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=20200203231055.0a3732b6@crub \
--to=agust@denx.de \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=trini@konsulko.com \
--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