mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shivendra Pratap <shivendra.pratap@oss.qualcomm.com>
To: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Unnathi Chalicheemala <unnathi.chalicheemala@oss.qualcomm.com>,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v10 1/3] firmware: qcom_scm: Add API to get waitqueue IRQ info
Date: Tue, 2 Dec 2025 22:06:24 +0530	[thread overview]
Message-ID: <e4c58df3-253f-7acf-0bb9-e0f6535bab50@oss.qualcomm.com> (raw)
In-Reply-To: <20251202114332.wlc2vdd2phslndek@hu-mojha-hyd.qualcomm.com>



On 12/2/2025 5:13 PM, Mukesh Ojha wrote:
> On Sun, Nov 30, 2025 at 08:11:02PM +0530, Shivendra Pratap wrote:
>> From: Unnathi Chalicheemala <unnathi.chalicheemala@oss.qualcomm.com>
>>

[SNIP..]

>>
>> diff --git a/drivers/firmware/qcom/qcom_scm.c b/drivers/firmware/qcom/qcom_scm.c
>> index e777b7cb9b127944fe112f453cae9cbc40c06cae..79ab1707f71b0157835deaea6309f33016e3de8c 100644
>> --- a/drivers/firmware/qcom/qcom_scm.c
>> +++ b/drivers/firmware/qcom/qcom_scm.c
>> @@ -29,12 +29,18 @@
>>  #include <linux/reset-controller.h>
>>  #include <linux/sizes.h>
>>  #include <linux/types.h>
>> +#include <dt-bindings/interrupt-controller/arm-gic.h>
> 
> At most places, where this header is used there is a line feed
> before it, if the header before it is not from dt-bindings.

Ack.

> 
>>  
>>  #include "qcom_scm.h"
>>  #include "qcom_tzmem.h"
>>  
>>  static u32 download_mode;
>>  
>> +#define GIC_SPI_BASE        32
>> +#define GIC_MAX_SPI       1019  // SPIs in GICv3 spec range from 32..1019
>> +#define GIC_ESPI_BASE     4096
>> +#define GIC_MAX_ESPI      5119 // ESPIs in GICv3 spec range from 4096..5119
>> +
>>  struct qcom_scm {
>>  	struct device *dev;
>>  	struct clk *core_clk;
>> @@ -2223,6 +2229,55 @@ bool qcom_scm_is_available(void)
>>  }
>>  EXPORT_SYMBOL_GPL(qcom_scm_is_available);
>>  
>> +static int qcom_scm_fill_irq_fwspec_params(struct irq_fwspec *fwspec, u32 hwirq)
>> +{
>> +	if (hwirq >= GIC_SPI_BASE && hwirq <= GIC_MAX_SPI) {
>> +		fwspec->param[0] = GIC_SPI;
>> +		fwspec->param[1] = hwirq - GIC_SPI_BASE;
>> +	} else if (hwirq >= GIC_ESPI_BASE && hwirq <= GIC_MAX_ESPI) {
>> +		fwspec->param[0] = GIC_ESPI;
>> +		fwspec->param[1] = hwirq - GIC_ESPI_BASE;
>> +	} else {
>> +		WARN(1, "Unexpected hwirq: %d\n", hwirq);
>> +		return -ENXIO;
>> +	}
> 
> line feed after } would make it look better..

Ack.

> 
>> +	fwspec->param[2] = IRQ_TYPE_EDGE_RISING;
>> +	fwspec->param_count = 3;
>> +
>> +	return 0;
>> +}
>> +
>> +static int qcom_scm_get_waitq_irq(struct qcom_scm *scm)
>> +{
>> +	struct device_node *parent_irq_node;
> 
> after desc ?

ok.

> 
>> +	struct qcom_scm_desc desc = {
>> +		.svc = QCOM_SCM_SVC_WAITQ,
>> +		.cmd = QCOM_SCM_WAITQ_GET_INFO,
>> +		.owner = ARM_SMCCC_OWNER_SIP
>> +	};
>> +	struct irq_fwspec fwspec;
>> +	struct qcom_scm_res res;
>> +	u32 hwirq;
>> +	int ret;
>> +
>> +	ret = qcom_scm_call_atomic(scm->dev, &desc, &res);
>> +	if (ret)
>> +		return ret;
>> +
>> +	hwirq = res.result[1] & GENMASK(15, 0);
>> +
> 
> redundant line feed ?

will remove. thanks.

> 
>> +	ret = qcom_scm_fill_irq_fwspec_params(&fwspec, hwirq);
>> +	if (ret)
>> +		return ret;
> 
> Line feed needed here after return or } ?

will add it.

thanks,
Shivendra

  reply	other threads:[~2025-12-02 16:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-30 14:41 [PATCH v10 0/3] SCM: Support latest version of waitq-aware firmware Shivendra Pratap
2025-11-30 14:41 ` [PATCH v10 1/3] firmware: qcom_scm: Add API to get waitqueue IRQ info Shivendra Pratap
2025-12-02 11:43   ` Mukesh Ojha
2025-12-02 16:36     ` Shivendra Pratap [this message]
2025-11-30 14:41 ` [PATCH v10 2/3] firmware: qcom_scm: Support multiple waitq contexts Shivendra Pratap
2025-12-02 12:52   ` Mukesh Ojha
2025-11-30 14:41 ` [PATCH v10 3/3] firmware: qcom_scm: Use TASK_IDLE state in wait_for_wq_completion() Shivendra Pratap
2025-12-03  8:31   ` Mukesh Ojha
2025-12-03 10:57     ` Shivendra Pratap
2025-12-04  7:36       ` Mukesh Ojha

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=e4c58df3-253f-7acf-0bb9-e0f6535bab50@oss.qualcomm.com \
    --to=shivendra.pratap@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mukesh.ojha@oss.qualcomm.com \
    --cc=unnathi.chalicheemala@oss.qualcomm.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®