From: Anatolij Gustschin <agust@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: linux-rockchip@lists.infradead.org, u-boot@lists.denx.de,
linux-amarula@amarulasolutions.com
Subject: Re: [PATCH 4/4] rockchip: Enable HDMI output on rk3399 board w/ HDMI
Date: Fri, 24 Jan 2020 18:03:44 +0100 [thread overview]
Message-ID: <20200124180344.375e3af4@crub> (raw)
In-Reply-To: <20200124152735.GR26536@bill-the-cat>
On Fri, 24 Jan 2020 10:27:35 -0500
Tom Rini trini@konsulko.com wrote:
> This seems like another commit (along with the question I saw about
> i.MX FB not showing the right colors) 2cc393f32fd9 needs to be reworked
> so that we default to enabling everything still but let boards opt out
> rather than forcing everyone to opt-in as it seems like there's a lot of
> cases where people need to opt-in and didn't know.
yes, I'll rework this.
--
Anatolij
next prev parent reply other threads:[~2020-01-24 17:03 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 [this message]
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=20200124180344.375e3af4@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