From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
dri-devel@lists.freedesktop.org,
Sebastian Reichel <sre@kernel.org>
Subject: Re: [PATCH] drm/omap: dsi: Fix PM for display blank with paired dss_pll calls
Date: Wed, 6 Feb 2019 08:29:20 -0800 [thread overview]
Message-ID: <20190206162920.GZ5720@atomide.com> (raw)
In-Reply-To: <b5cdb1ba-6c2f-d626-4bfa-4c0ca287ea97@ti.com>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [190206 16:09]:
> On 06/02/2019 18:00, Tony Lindgren wrote:
>
> > OK I'll give it a try. Based on a quick glance, we need to still
> > check for enabled regulator to avoid unpaired calls.
> >
> >> static int dsi_dump_dsi_clocks(struct seq_file *s, void *p)
> >> @@ -4108,6 +4094,10 @@ static int dsi_display_init_dsi(struct dsi_data *dsi)
> >>
> >> DSSDBG("PLL OK\n");
> >>
> >> + // XXX enable the regulator for the lanes
> >> + regulator_enable(dsi->vdds_dsi_reg);
> >> + dsi->vdds_dsi_enabled = true;
> >> +
> >
> > So the above should only be done if !dsi->vdds_dsi_enabled?
Actually the conditional handling is only needed above. And
the regulator_enable needs error handling added that causes
some renumbering of the exit path.
> >> r = dsi_cio_init(dsi);
> >> if (r)
> >> goto err2;
> >> @@ -4136,6 +4126,10 @@ static int dsi_display_init_dsi(struct dsi_data *dsi)
> >> err3:
> >> dsi_cio_uninit(dsi);
> >> err2:
> >> + // XXX disable the regulator for the lanes
> >> + regulator_disable(dsi->vdds_dsi_reg);
> >> + dsi->vdds_dsi_enabled = false;
> >> +
> >
> > And here only if dsi->vdds_dsi_enabled?
On errors here we should just shut it down.
> >> @@ -4158,7 +4152,12 @@ static void dsi_display_uninit_dsi(struct dsi_data *dsi, bool disconnect_lanes,
> >>
> >> dss_select_dsi_clk_source(dsi->dss, dsi->module_id, DSS_CLK_SRC_FCK);
> >> dsi_cio_uninit(dsi);
> >> - dsi_pll_uninit(dsi, disconnect_lanes);
> >> + dss_pll_disable(&dsi->pll);
> >> +
> >> + if (disconnect_lanes) {
> >> + regulator_disable(dsi->vdds_dsi_reg);
> >> + dsi->vdds_dsi_enabled = false;
> >> + }
> >> }
> >
> > Since they would be paired with the conditional handling
> > here?
>
> Hmm, yes, I think you're right. And there's already one in dsi_remove(),
> which handles the final disable at unload time.
OK. Looks good to me otherwise.
So I guess we should fix. Do you want me to post it all
as a single patch after some testing?
It seems that we'll be breaking things one way or another
trying to do it in two patches :)
Regards,
Tony
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-02-06 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 3:32 [PATCH] drm/omap: dsi: Fix PM for display blank with paired dss_pll calls Tony Lindgren
2019-02-04 9:57 ` Tomi Valkeinen
2019-02-04 15:42 ` Tony Lindgren
2019-02-05 11:06 ` Tomi Valkeinen
2019-02-05 17:58 ` Tony Lindgren
2019-02-06 9:13 ` Tomi Valkeinen
2019-02-06 16:00 ` Tony Lindgren
2019-02-06 16:09 ` Tomi Valkeinen
2019-02-06 16:29 ` Tony Lindgren [this message]
2019-02-07 9:07 ` Tomi Valkeinen
2019-02-07 15:46 ` Tony Lindgren
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=20190206162920.GZ5720@atomide.com \
--to=tony@atomide.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-omap@vger.kernel.org \
--cc=sre@kernel.org \
--cc=tomi.valkeinen@ti.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).