From: Heiko Stuebner <heiko@sntech.de>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: David Airlie <airlied@linux.ie>,
djkurtz@chromium.org, Yakir Yang <ykk@rock-chips.com>,
Fabio Estevam <fabio.estevam@freescale.com>,
dianders@chromium.org, Andy Yan <andy.yan@rock-chips.com>,
Mark Yao <mark.yao@rock-chips.com>,
linux-rockchip@lists.infradead.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
broonie@kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] drm/bridge: dw-hdmi: support optional supply regulators
Date: Tue, 10 Mar 2015 10:43:37 +0100 [thread overview]
Message-ID: <79223422.KFbmI1BzE4@phil> (raw)
In-Reply-To: <1425979013.3141.17.camel@pengutronix.de>
Hi Philipp,
Am Dienstag, 10. März 2015, 10:16:53 schrieb Philipp Zabel:
[cut the obvious stuff I need to fix]
> Am Dienstag, den 10.03.2015, 00:22 +0100 schrieb Heiko Stuebner:
> > @@ -879,6 +883,12 @@ static int dw_hdmi_phy_init(struct dw_hdmi *hdmi)
> >
> > int i, ret;
> > bool cscon = false;
> >
> > + if (hdmi->nsupplies > 0) {
> > + ret = regulator_bulk_enable(hdmi->nsupplies, hdmi->supplies);
> > + if (ret)
> > + return ret;
> > + }
> > +
>
> Are these really supplies to the PHY or is this just a convenient place
> to enable them? Looking at the i.MX6 docs, I suppose yes.
According to the TRM, the supplies are "DC supply voltage for Analog part of
HDMI", so I'd think phy supplies.
>
> > /*check csc whether needed activated in HDMI mode */
> > cscon = (is_color_space_conversion(hdmi) &&
> >
> > !hdmi->hdmi_data.video_mode.mdvi);
> >
> > @@ -1105,6 +1115,9 @@ static void dw_hdmi_phy_disable(struct dw_hdmi
> > *hdmi)
> >
> > dw_hdmi_phy_enable_tmds(hdmi, 0);
> > dw_hdmi_phy_enable_power(hdmi, 0);
> >
> > + if (hdmi->nsupplies > 0)
> > + regulator_bulk_disable(hdmi->nsupplies, hdmi->supplies);
> > +
> >
> > hdmi->phy_enabled = false;
> >
> > }
> >
> > @@ -1549,7 +1562,8 @@ static int dw_hdmi_register(struct drm_device *drm,
> > struct dw_hdmi *hdmi)>
> > int dw_hdmi_bind(struct device *dev, struct device *master,
> >
> > void *data, struct drm_encoder *encoder,
> > struct resource *iores, int irq,
> >
> > - const struct dw_hdmi_plat_data *plat_data)
> > + const struct dw_hdmi_plat_data *plat_data,
> > + struct regulator_bulk_data *supplies, int nsupplies)
>
> I'm not sure I like this function sprouting so many parameters. Is there
> a good reason not to add this to struct dw_hdmi_plat_data?
Nope, moving this to platdata sound sensible and I'll give this a try :-)
Heiko
next prev parent reply other threads:[~2015-03-10 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 23:21 [PATCH 0/3] add power-supply support to dw_hdmi Heiko Stuebner
2015-03-09 23:22 ` [PATCH 1/3] regulator: don't emit errors in {devm_}regulator_bulk_get when defering Heiko Stuebner
2015-03-10 12:07 ` Mark Brown
2015-03-10 12:33 ` Heiko Stuebner
2015-03-09 23:22 ` [PATCH 2/3] drm/bridge: dw-hdmi: support optional supply regulators Heiko Stuebner
2015-03-10 9:16 ` Philipp Zabel
2015-03-10 9:43 ` Heiko Stuebner [this message]
2015-03-09 23:23 ` [PATCH 3/3] ARM: dts: rockchip: add hdmi analog power supplies to rk3288 boards Heiko Stuebner
2015-03-10 9:08 ` [PATCH 0/3] add power-supply support to dw_hdmi Philipp Zabel
2015-03-10 9:58 ` Russell King - ARM Linux
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=79223422.KFbmI1BzE4@phil \
--to=heiko@sntech.de \
--cc=airlied@linux.ie \
--cc=andy.yan@rock-chips.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=djkurtz@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabio.estevam@freescale.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mark.yao@rock-chips.com \
--cc=p.zabel@pengutronix.de \
--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).