All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anson Huang <anson.huang@nxp.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
	"jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Cc: dl-linux-imx <linux-imx@nxp.com>
Subject: RE: [PATCH] mailbox: imx: Support runtime PM
Date: Mon, 13 Apr 2020 13:13:28 +0000	[thread overview]
Message-ID: <DB3PR0402MB3916D05B44D776E5242434B1F5DD0@DB3PR0402MB3916.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <eb0eae78-35e9-1496-0869-94b48270f544@pengutronix.de>

Hi, Marc

> Subject: Re: [PATCH] mailbox: imx: Support runtime PM
> 
> On 4/13/20 2:25 PM, Anson Huang wrote:
> > Some power hungry sub-systems like VPU has its own MUs which also use
> > mailbox driver, current mailbox driver uses platform driver model and
> > MU's power will be ON after driver probed and left ON there, it may
> > cause the whole sub-system can NOT enter lower power mode, take VPU
> > driver for example, it has runtime PM support, but due to its MU
> > always ON, the VPU sub-system will be always ON and consume many power
> > during kernel idle.
> >
> > To save power in kernel idle, mailbox driver needs to support runtime
> > PM in order to power off MU when it is unused. However, the runtime
> > suspend/resume can ONLY be implemented in mailbox's .shutdown/.startup
> > callback, so its consumer needs to call
> > mbox_request_channel()/mbox_free_channel() in consumer driver's
> > runtime PM callback, then the MU's power will be ON/OFF along with
> > consumer's runtime PM status.
> >
> > Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> > ---
> >  drivers/mailbox/imx-mailbox.c | 27 ++++++++++++++++++++++++++-
> >  1 file changed, 26 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/mailbox/imx-mailbox.c
> > b/drivers/mailbox/imx-mailbox.c index 7906624..97bf0ac 100644
> > --- a/drivers/mailbox/imx-mailbox.c
> > +++ b/drivers/mailbox/imx-mailbox.c
> > @@ -12,6 +12,7 @@
> >  #include <linux/mailbox_controller.h>  #include <linux/module.h>
> > #include <linux/of_device.h>
> > +#include <linux/pm_runtime.h>
> >  #include <linux/slab.h>
> >
> >  #define IMX_MU_xSR_GIPn(x)	BIT(28 + (3 - (x)))
> > @@ -287,6 +288,7 @@ static int imx_mu_startup(struct mbox_chan *chan)
> >  	struct imx_mu_con_priv *cp = chan->con_priv;
> >  	int ret;
> >
> > +	pm_runtime_get_sync(priv->dev);
> >  	if (cp->type == IMX_MU_TYPE_TXDB) {
> >  		/* Tx doorbell don't have ACK support */
> >  		tasklet_init(&cp->txdb_tasklet, imx_mu_txdb_tasklet, @@ -323,6
> > +325,7 @@ static void imx_mu_shutdown(struct mbox_chan *chan)
> >
> >  	if (cp->type == IMX_MU_TYPE_TXDB) {
> >  		tasklet_kill(&cp->txdb_tasklet);
> > +		pm_runtime_put_sync(priv->dev);
> >  		return;
> >  	}
> >
> > @@ -341,6 +344,7 @@ static void imx_mu_shutdown(struct mbox_chan
> *chan)
> >  	}
> >
> >  	free_irq(priv->irq, chan);
> > +	pm_runtime_put_sync(priv->dev);
> >  }
> >
> >  static const struct mbox_chan_ops imx_mu_ops = { @@ -508,7 +512,27
> @@
> > static int imx_mu_probe(struct platform_device *pdev)
> >
> >  	platform_set_drvdata(pdev, priv);
> >
> > -	return devm_mbox_controller_register(dev, &priv->mbox);
> > +	ret = devm_mbox_controller_register(dev, &priv->mbox);
> > +	if (ret)
> > +		return ret;
> > +
> > +	pm_runtime_enable(dev);
> > +
> 
> First registering at the system and then setting up the power management
> looks racy. Don't know if this is serialized by some other means.

Don't have other means, just refer to
drivers/mailbox/omap-mailbox.c, it has same sequence, NOT sure if there is
special requirement about this sequence.

Thanks,
Anson

WARNING: multiple messages have this Message-ID (diff)
From: Anson Huang <anson.huang@nxp.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
	"jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Cc: dl-linux-imx <linux-imx@nxp.com>
Subject: RE: [PATCH] mailbox: imx: Support runtime PM
Date: Mon, 13 Apr 2020 13:13:28 +0000	[thread overview]
Message-ID: <DB3PR0402MB3916D05B44D776E5242434B1F5DD0@DB3PR0402MB3916.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <eb0eae78-35e9-1496-0869-94b48270f544@pengutronix.de>

Hi, Marc

> Subject: Re: [PATCH] mailbox: imx: Support runtime PM
> 
> On 4/13/20 2:25 PM, Anson Huang wrote:
> > Some power hungry sub-systems like VPU has its own MUs which also use
> > mailbox driver, current mailbox driver uses platform driver model and
> > MU's power will be ON after driver probed and left ON there, it may
> > cause the whole sub-system can NOT enter lower power mode, take VPU
> > driver for example, it has runtime PM support, but due to its MU
> > always ON, the VPU sub-system will be always ON and consume many power
> > during kernel idle.
> >
> > To save power in kernel idle, mailbox driver needs to support runtime
> > PM in order to power off MU when it is unused. However, the runtime
> > suspend/resume can ONLY be implemented in mailbox's .shutdown/.startup
> > callback, so its consumer needs to call
> > mbox_request_channel()/mbox_free_channel() in consumer driver's
> > runtime PM callback, then the MU's power will be ON/OFF along with
> > consumer's runtime PM status.
> >
> > Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> > ---
> >  drivers/mailbox/imx-mailbox.c | 27 ++++++++++++++++++++++++++-
> >  1 file changed, 26 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/mailbox/imx-mailbox.c
> > b/drivers/mailbox/imx-mailbox.c index 7906624..97bf0ac 100644
> > --- a/drivers/mailbox/imx-mailbox.c
> > +++ b/drivers/mailbox/imx-mailbox.c
> > @@ -12,6 +12,7 @@
> >  #include <linux/mailbox_controller.h>  #include <linux/module.h>
> > #include <linux/of_device.h>
> > +#include <linux/pm_runtime.h>
> >  #include <linux/slab.h>
> >
> >  #define IMX_MU_xSR_GIPn(x)	BIT(28 + (3 - (x)))
> > @@ -287,6 +288,7 @@ static int imx_mu_startup(struct mbox_chan *chan)
> >  	struct imx_mu_con_priv *cp = chan->con_priv;
> >  	int ret;
> >
> > +	pm_runtime_get_sync(priv->dev);
> >  	if (cp->type == IMX_MU_TYPE_TXDB) {
> >  		/* Tx doorbell don't have ACK support */
> >  		tasklet_init(&cp->txdb_tasklet, imx_mu_txdb_tasklet, @@ -323,6
> > +325,7 @@ static void imx_mu_shutdown(struct mbox_chan *chan)
> >
> >  	if (cp->type == IMX_MU_TYPE_TXDB) {
> >  		tasklet_kill(&cp->txdb_tasklet);
> > +		pm_runtime_put_sync(priv->dev);
> >  		return;
> >  	}
> >
> > @@ -341,6 +344,7 @@ static void imx_mu_shutdown(struct mbox_chan
> *chan)
> >  	}
> >
> >  	free_irq(priv->irq, chan);
> > +	pm_runtime_put_sync(priv->dev);
> >  }
> >
> >  static const struct mbox_chan_ops imx_mu_ops = { @@ -508,7 +512,27
> @@
> > static int imx_mu_probe(struct platform_device *pdev)
> >
> >  	platform_set_drvdata(pdev, priv);
> >
> > -	return devm_mbox_controller_register(dev, &priv->mbox);
> > +	ret = devm_mbox_controller_register(dev, &priv->mbox);
> > +	if (ret)
> > +		return ret;
> > +
> > +	pm_runtime_enable(dev);
> > +
> 
> First registering at the system and then setting up the power management
> looks racy. Don't know if this is serialized by some other means.

Don't have other means, just refer to
drivers/mailbox/omap-mailbox.c, it has same sequence, NOT sure if there is
special requirement about this sequence.

Thanks,
Anson
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-04-13 13:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 12:25 [PATCH] mailbox: imx: Support runtime PM Anson Huang
2020-04-13 12:25 ` Anson Huang
2020-04-13 12:52 ` Marc Kleine-Budde
2020-04-13 12:52   ` Marc Kleine-Budde
2020-04-13 13:13   ` Anson Huang [this message]
2020-04-13 13:13     ` Anson Huang
2020-05-28  2:01     ` Anson Huang
2020-05-28  2:01       ` Anson Huang

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=DB3PR0402MB3916D05B44D776E5242434B1F5DD0@DB3PR0402MB3916.eurprd04.prod.outlook.com \
    --to=anson.huang@nxp.com \
    --cc=festevam@gmail.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.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.