From: "Heiko Stübner" <heiko@sntech.de>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
dianders@chromium.org, linux-rockchip@lists.infradead.org,
dri-devel@lists.freedesktop.org, Yakir Yang <ykk@rock-chips.com>,
Andy Yan <andy.yan@rock-chips.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/2] drm/bridge: dw-hdmi: support optional supply regulators
Date: Fri, 12 Jun 2015 09:27:07 +0200 [thread overview]
Message-ID: <4099644.agHN3RgGum@diego> (raw)
In-Reply-To: <20150609233618.GK7557@n2100.arm.linux.org.uk>
Am Mittwoch, 10. Juni 2015, 00:36:18 schrieb Russell King - ARM Linux:
> On Wed, Jun 10, 2015 at 01:29:43AM +0200, Heiko Stübner wrote:
> > Allthough from the discussion and explanations I've now also got the
> > "don't
> > make it worse" feeling, so am somehow reluctant to add supplies that also
> > might describe this inadequately.
> >
> > The Rockchip-specific documentation only lists the two supplies as
> > AVDD_1V0, AVDD_1V8 with a description of "DC supply voltage for Analog
> > part of HDMI". The supplies aren't mentioned otherwise at all, so I guess
> > I'll ponder this a bit more at first.
>
> Are they controllable from software at all? If they aren't, then
> I'd suggest leaving them out until we have a distinction between
> the Tx and Phy - much as we do for iMX6.
they are supplied by the pmic the system uses (named vdd10_lcd and vdd18_lcd
in the soc manuals/schematics) and supply the individual output encoder
analog parts (hdmi, edp, lvds, etc). So if there is no output at all, they
should be able to be turned off.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-06-12 7:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 20:45 [PATCH v3 1/2] drm/bridge: dw-hdmi: support optional supply regulators Heiko Stuebner
2015-03-12 20:46 ` [PATCH v3 2/2] ARM: dts: rockchip: add hdmi analog power supplies to rk3288 boards Heiko Stuebner
2015-03-23 18:17 ` [PATCH v3 1/2] drm/bridge: dw-hdmi: support optional supply regulators Heiko Stuebner
2015-03-25 16:51 ` Philipp Zabel
2015-06-05 11:02 ` Thierry Reding
2015-06-05 12:16 ` Heiko Stübner
2015-06-05 12:23 ` Thierry Reding
[not found] ` <20150605122311.GA759-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2015-06-05 23:03 ` Heiko Stübner
2015-06-05 23:10 ` Russell King - ARM Linux
2015-06-08 14:02 ` Thierry Reding
2015-06-08 14:29 ` Russell King - ARM Linux
2015-06-08 15:44 ` Thierry Reding
2015-06-08 16:34 ` Russell King - ARM Linux
2015-06-09 7:53 ` Thierry Reding
2015-06-09 23:29 ` Heiko Stübner
2015-06-09 23:36 ` Russell King - ARM Linux
2015-06-12 7:27 ` Heiko Stübner [this message]
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=4099644.agHN3RgGum@diego \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=ykk@rock-chips.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).