From: Sudeep Patil <quic_sudeepgo@quicinc.com>
To: <quic_bjorande@quicinc.com>, <andersson@kernel.org>,
<quic_clew@quicinc.com>, <mathieu.poirier@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <quic_deesin@quicinc.com>,
<linux-arm-msm@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>
Subject: Re: [PATCH V3 1/2] soc: qcom: smp2p: Use devname for interrupt descriptions
Date: Tue, 2 Jul 2024 12:09:10 +0530 [thread overview]
Message-ID: <4a5c0b88-d4be-4dd2-9bce-981f093737aa@quicinc.com> (raw)
In-Reply-To: <20240627104831.4176799-2-quic_sudeepgo@quicinc.com>
On 6/27/2024 4:18 PM, Sudeepgoud Patil wrote:
> From: Chris Lew <quic_clew@quicinc.com>
>
> When using /proc/interrupts to collect statistics on smp2p interrupt
> counts, it is hard to distinguish the different instances of smp2p from
> each other. For example to debug a processor boot issue, the ready and
> handover interrupts are checked for sanity to ensure the firmware
> reached a specific initialization stage.
>
> Remove "smp2p" string from the irq request so that the irq will default
> to the device name. Add an .irq_print_chip() callback to print the irq
> chip name as the device name. These two changes allow for a unique name
> to be used in /proc/interrupts as shown below.
>
> / # cat /proc/interrupts | grep smp2p
> 18: ... ipcc 196610 Edge smp2p-adsp
> 20: ... ipcc 131074 Edge smp2p-modem
> 170: ... smp2p-modem 1 Edge q6v5 ready
> 178: ... smp2p-adsp 1 Edge q6v5 ready
>
> Signed-off-by: Chris Lew <quic_clew@quicinc.com>
Signed-off-by: Sudeepgoud Patil <quic_sudeepgo@quicinc.com>
> ---
> drivers/soc/qcom/smp2p.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/soc/qcom/smp2p.c b/drivers/soc/qcom/smp2p.c
> index a21241cbeec7..696c2a8387d0 100644
> --- a/drivers/soc/qcom/smp2p.c
> +++ b/drivers/soc/qcom/smp2p.c
> @@ -16,6 +16,7 @@
> #include <linux/platform_device.h>
> #include <linux/pm_wakeirq.h>
> #include <linux/regmap.h>
> +#include <linux/seq_file.h>
> #include <linux/soc/qcom/smem.h>
> #include <linux/soc/qcom/smem_state.h>
> #include <linux/spinlock.h>
> @@ -353,11 +354,19 @@ static int smp2p_set_irq_type(struct irq_data *irqd, unsigned int type)
> return 0;
> }
>
> +static void smp2p_irq_print_chip(struct irq_data *irqd, struct seq_file *p)
> +{
> + struct smp2p_entry *entry = irq_data_get_irq_chip_data(irqd);
> +
> + seq_printf(p, " %8s", dev_name(entry->smp2p->dev));
> +}
> +
> static struct irq_chip smp2p_irq_chip = {
> .name = "smp2p",
> .irq_mask = smp2p_mask_irq,
> .irq_unmask = smp2p_unmask_irq,
> .irq_set_type = smp2p_set_irq_type,
> + .irq_print_chip = smp2p_irq_print_chip,
> };
>
> static int smp2p_irq_map(struct irq_domain *d,
> @@ -617,7 +626,7 @@ static int qcom_smp2p_probe(struct platform_device *pdev)
> ret = devm_request_threaded_irq(&pdev->dev, irq,
> NULL, qcom_smp2p_intr,
> IRQF_ONESHOT,
> - "smp2p", (void *)smp2p);
> + NULL, (void *)smp2p);
> if (ret) {
> dev_err(&pdev->dev, "failed to request interrupt\n");
> goto unwind_interfaces;
next prev parent reply other threads:[~2024-07-02 6:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 10:48 [PATCH V3 0/2] Use of devname for interrupt descriptions and tracepoint support for smp2p Sudeepgoud Patil
2024-06-27 10:48 ` [PATCH V3 1/2] soc: qcom: smp2p: Use devname for interrupt descriptions Sudeepgoud Patil
2024-06-29 13:03 ` Konrad Dybcio
2024-07-02 6:39 ` Sudeep Patil [this message]
2024-07-02 7:59 ` Dmitry Baryshkov
2024-06-27 10:48 ` [PATCH V3 2/2] soc: qcom: smp2p: Introduce tracepoint support Sudeepgoud Patil
2024-06-28 9:22 ` Deepak Kumar Singh
2024-06-28 17:36 ` kernel test robot
2024-07-02 8:03 ` Dmitry Baryshkov
2024-07-03 3:37 ` (subset) [PATCH V3 0/2] Use of devname for interrupt descriptions and tracepoint support for smp2p Bjorn Andersson
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=4a5c0b88-d4be-4dd2-9bce-981f093737aa@quicinc.com \
--to=quic_sudeepgo@quicinc.com \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_bjorande@quicinc.com \
--cc=quic_clew@quicinc.com \
--cc=quic_deesin@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
all inboxes | Powered by JetHome®