linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
	Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH 2/4] arm: dts: rockchip: enable the first hdmi output
Date: Sat, 21 Oct 2017 22:06:56 +0200	[thread overview]
Message-ID: <2074014.EmavDXF96e@phil> (raw)
In-Reply-To: <20171020100734.17064-3-hverkuil@xs4all.nl>

Am Freitag, 20. Oktober 2017, 12:07:32 CEST schrieb Hans Verkuil:
> From: Hans Verkuil <hans.verkuil@cisco.com>
> 
> The vdd10_lcd and vcc18_lcd regulators need to be enabled for HDMI output
> to work, so add 'regulator-always-on', just as is done in rk3288-firefly.dtsi.
> 
> Also enable i2c5 and the hdmi block.
> 
> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>

applied for 4.15, after adapting the subject and moving it
to position 3 in the series.


Heiko

  reply	other threads:[~2017-10-21 20:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 10:07 [PATCH 0/4] arm: dts: rockchip: enable HDMI+CEC on Firefly Reload Hans Verkuil
2017-10-20 10:07 ` [PATCH 1/4] arm: dts: rockchip: add the cec clk for dw-hdmi on rk3288 Hans Verkuil
2017-10-21 19:29   ` Heiko Stuebner
2017-10-20 10:07 ` [PATCH 2/4] arm: dts: rockchip: enable the first hdmi output Hans Verkuil
2017-10-21 20:06   ` Heiko Stuebner [this message]
2017-10-20 10:07 ` [PATCH 3/4] arm: dts: rockchip: define the two possible CEC pins Hans Verkuil
2017-10-21 19:36   ` Heiko Stuebner
2017-10-20 10:07 ` [PATCH 4/4] arm: dts: rockchip: select which CEC pin is used for the Firefly Reload Hans Verkuil
2017-10-21 20:07   ` Heiko Stuebner
2017-10-22  7:40 ` [PATCH 0/4] arm: dts: rockchip: enable HDMI+CEC on " Hans Verkuil

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=2074014.EmavDXF96e@phil \
    --to=heiko@sntech.de \
    --cc=hans.verkuil@cisco.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    /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).