All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Marek Vasut <marex@denx.de>, Peng Fan <peng.fan@nxp.com>,
	Alexander Stein <alexander.stein@ew.tq-group.com>,
	robert.foss@linaro.org, Martyn Welch <martyn.welch@collabora.com>,
	dri-devel@lists.freedesktop.org, Robby Cai <robby.cai@nxp.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v5 2/2] drm: lcdif: Add support for i.MX8MP LCDIF variant
Date: Fri, 24 Jun 2022 17:20:00 +0200	[thread overview]
Message-ID: <YrXWIP3dRLc/ArOK@ravnborg.org> (raw)
In-Reply-To: <7b3850665f7fd699ff7d0a013e5652159d4b5055.camel@pengutronix.de>

> > +
> > +static int lcdif_rpm_resume(struct device *dev)
> > +{
> > +	struct drm_device *drm = dev_get_drvdata(dev);
> > +	struct lcdif_drm_private *lcdif = drm->dev_private;
> > +
> > +	/* These clock supply the Control Bus, APB, APBH Ctrl Registers */
> > +	clk_prepare_enable(lcdif->clk_axi);
> > +	/* These clock supply the System Bus, AXI, Write Path, LFIFO */
> > +	clk_prepare_enable(lcdif->clk_disp_axi);
> > +	/* These clock supply the DISPLAY CLOCK Domain */
> > +	clk_prepare_enable(lcdif->clk);
> > +
> > +	return 0;
> > +}
> > +
> 
> To avoid unused function warnings, suspend and resume should be under
> #ifdef CONFIG_PM_SLEEP

If SET_RUNTIME_PM_OPS is used then it is good practice to annotate the
functions __maybe_unused and no #ifdef - then they see build coverage also
without PM_SLEEP but they are discarded so do not consume memory if not used.

	Sam

      reply	other threads:[~2022-06-24 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 21:31 [PATCH v5 1/2] dt-bindings: lcdif: Add compatible for i.MX8MP Marek Vasut
2022-06-13 21:31 ` Marek Vasut
2022-06-13 21:31 ` [PATCH v5 2/2] drm: lcdif: Add support for i.MX8MP LCDIF variant Marek Vasut
2022-06-23  9:04   ` (EXT) " Alexander Stein
2022-06-24 13:54   ` Lucas Stach
2022-06-24 15:20     ` Sam Ravnborg [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=YrXWIP3dRLc/ArOK@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=l.stach@pengutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=marex@denx.de \
    --cc=martyn.welch@collabora.com \
    --cc=peng.fan@nxp.com \
    --cc=robby.cai@nxp.com \
    --cc=robert.foss@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.