public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <mani@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Sibi Sankar <quic_sibis@quicinc.com>,
	bjorn.andersson@linaro.org, jassisinghbrar@gmail.com,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	agross@kernel.org, Prasad Sodagudi <quic_psodagud@quicinc.com>
Subject: Re: [PATCH v3] mailbox: qcom-ipcc: Log the pending interrupt during resume
Date: Tue, 24 May 2022 19:27:35 +0530	[thread overview]
Message-ID: <20220524135735.GD5745@thinkpad> (raw)
In-Reply-To: <20220524134825.GA4188122@roeck-us.net>

On Tue, May 24, 2022 at 06:48:25AM -0700, Guenter Roeck wrote:
> On Tue, May 17, 2022 at 04:13:00PM +0530, Sibi Sankar wrote:
> > From: Prasad Sodagudi <quic_psodagud@quicinc.com>
> > 
> > Enable logging of the pending interrupt that triggered device wakeup. This
> > logging information helps to debug IRQs that cause periodic device wakeups
> > by printing the detailed information of pending IPCC interrupts.
> > 
> > Scenario: Device wakeup caused by Modem crash
> > Logs:
> > qcom-ipcc mailbox: virq: 182 triggered client-id: 2; signal-id: 2
> > 
> > >From the IPCC bindings it can further be understood that the client here is
> > IPCC_CLIENT_MPSS and the signal was IPCC_MPROC_SIGNAL_SMP2P.
> > 
> > Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
> > Signed-off-by: Prasad Sodagudi <quic_psodagud@quicinc.com>
> > Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com>
> > ---
> > 
> > V3:
> >  * Use pm_sleep_ptr and convert info to dbg [Mani]
> 
> Unfortunately, this results in
> 
> drivers/mailbox/qcom-ipcc.c:258:12: error: 'qcom_ipcc_pm_resume' defined but not used
> 
> on builds with PM disabled, as seen in next-20220524.
> 

Yep, I missed it during review :(

But the fix has been submitted:
https://patchwork.kernel.org/project/linux-arm-msm/patch/20220523224702.2002652-1-nathan@kernel.org/

Thanks,
Mani

> Guenter
> 
> >  * Fixup commit message
> > 
> > V2:
> >  * Fix build error when ipcc is a module [Kernel Test Bot]
> > 
> >  drivers/mailbox/qcom-ipcc.c | 23 +++++++++++++++++++++++
> >  1 file changed, 23 insertions(+)
> > 
> > diff --git a/drivers/mailbox/qcom-ipcc.c b/drivers/mailbox/qcom-ipcc.c
> > index c5d963222014..5a42bc2a1083 100644
> > --- a/drivers/mailbox/qcom-ipcc.c
> > +++ b/drivers/mailbox/qcom-ipcc.c
> > @@ -254,6 +254,24 @@ static int qcom_ipcc_setup_mbox(struct qcom_ipcc *ipcc,
> >  	return devm_mbox_controller_register(dev, mbox);
> >  }
> >  
> > +static int qcom_ipcc_pm_resume(struct device *dev)
> > +{
> > +	struct qcom_ipcc *ipcc = dev_get_drvdata(dev);
> > +	u32 hwirq;
> > +	int virq;
> > +
> > +	hwirq = readl(ipcc->base + IPCC_REG_RECV_ID);
> > +	if (hwirq == IPCC_NO_PENDING_IRQ)
> > +		return 0;
> > +
> > +	virq = irq_find_mapping(ipcc->irq_domain, hwirq);
> > +
> > +	dev_dbg(dev, "virq: %d triggered client-id: %ld; signal-id: %ld\n", virq,
> > +		FIELD_GET(IPCC_CLIENT_ID_MASK, hwirq), FIELD_GET(IPCC_SIGNAL_ID_MASK, hwirq));
> > +
> > +	return 0;
> > +}
> > +
> >  static int qcom_ipcc_probe(struct platform_device *pdev)
> >  {
> >  	struct qcom_ipcc *ipcc;
> > @@ -324,6 +342,10 @@ static const struct of_device_id qcom_ipcc_of_match[] = {
> >  };
> >  MODULE_DEVICE_TABLE(of, qcom_ipcc_of_match);
> >  
> > +static const struct dev_pm_ops qcom_ipcc_dev_pm_ops = {
> > +	SET_NOIRQ_SYSTEM_SLEEP_PM_OPS(NULL, qcom_ipcc_pm_resume)
> > +};
> > +
> >  static struct platform_driver qcom_ipcc_driver = {
> >  	.probe = qcom_ipcc_probe,
> >  	.remove = qcom_ipcc_remove,
> > @@ -331,6 +353,7 @@ static struct platform_driver qcom_ipcc_driver = {
> >  		.name = "qcom-ipcc",
> >  		.of_match_table = qcom_ipcc_of_match,
> >  		.suppress_bind_attrs = true,
> > +		.pm = pm_sleep_ptr(&qcom_ipcc_dev_pm_ops),
> >  	},
> >  };
> >  
> > -- 
> > 2.7.4
> > 

-- 
மணிவண்ணன் சதாசிவம்

      reply	other threads:[~2022-05-24 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 10:43 [PATCH v3] mailbox: qcom-ipcc: Log the pending interrupt during resume Sibi Sankar
2022-05-24 13:48 ` Guenter Roeck
2022-05-24 13:57   ` Manivannan Sadhasivam [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=20220524135735.GD5745@thinkpad \
    --to=mani@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=quic_psodagud@quicinc.com \
    --cc=quic_sibis@quicinc.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