Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Songwei Chai <songwei.chai@oss.qualcomm.com>,
	andersson@kernel.org, alexander.shishkin@linux.intel.com,
	mike.leach@linaro.org, suzuki.poulose@arm.com,
	james.clark@arm.com, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, coresight@lists.linaro.org,
	devicetree@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH v10 5/7] qcom-tgu: Add support to configure next action
Date: Tue, 13 Jan 2026 12:15:50 +0100	[thread overview]
Message-ID: <f211054c-ecb7-4f90-b9ce-9fdd7710c8c4@oss.qualcomm.com> (raw)
In-Reply-To: <20260109021141.3778421-6-songwei.chai@oss.qualcomm.com>

On 1/9/26 3:11 AM, Songwei Chai wrote:
> Add "select" node for each step to determine if another step is taken,
> trigger(s) are generated, counters/timers incremented/decremented, etc.
> 
> Signed-off-by: Songwei Chai <songwei.chai@oss.qualcomm.com>
> ---

[...]

> +		case TGU_CONDITION_SELECT:
> +		/* 'default' register is at the end of 'select' region */
> +			if (tgu_attr->reg_num ==
> +			    drvdata->max_condition_select - 1)
> +				attr->name = "default";
> +			ret = (tgu_attr->reg_num <
> +				drvdata->max_condition_select) ?
> +				attr->mode : 0;

similarly to my previous comments

[...]

> +	for (i = 0; i < drvdata->max_step; i++) {
> +		for (j = 0; j < drvdata->max_condition_select; j++) {
> +			index = check_array_location(drvdata, i,
> +						TGU_CONDITION_SELECT, j);
> +
> +			if (index == -EINVAL)

stray \n
> +				goto exit;
> +
> +			writel(drvdata->value_table->condition_select[index],
> +				drvdata->base + CONDITION_SELECT_STEP(i, j));
> +		}
> +	}
>  	/* Enable TGU to program the triggers */
>  	writel(1, drvdata->base + TGU_CONTROL);
>  exit:
> @@ -225,6 +258,8 @@ static void tgu_set_conditions(struct tgu_drvdata *drvdata)
>  
>  	devid = readl(drvdata->base + TGU_DEVID);
>  	drvdata->max_condition_decode = TGU_DEVID_CONDITIONS(devid);
> +	/* select region has an additional 'default' register */
> +	drvdata->max_condition_select = TGU_DEVID_CONDITIONS(devid) + 1;
>  }
>  
>  static int tgu_enable(struct device *dev)
> @@ -356,6 +391,14 @@ static const struct attribute_group *tgu_attr_groups[] = {
>  	CONDITION_DECODE_ATTRIBUTE_GROUP_INIT(5),
>  	CONDITION_DECODE_ATTRIBUTE_GROUP_INIT(6),
>  	CONDITION_DECODE_ATTRIBUTE_GROUP_INIT(7),
> +	CONDITION_SELECT_ATTRIBUTE_GROUP_INIT(0),
> +	CONDITION_SELECT_ATTRIBUTE_GROUP_INIT(1),
> +	CONDITION_SELECT_ATTRIBUTE_GROUP_INIT(2),
> +	CONDITION_SELECT_ATTRIBUTE_GROUP_INIT(3),
> +	CONDITION_SELECT_ATTRIBUTE_GROUP_INIT(4),
> +	CONDITION_SELECT_ATTRIBUTE_GROUP_INIT(5),
> +	CONDITION_SELECT_ATTRIBUTE_GROUP_INIT(6),
> +	CONDITION_SELECT_ATTRIBUTE_GROUP_INIT(7),
>  	NULL,
>  };
>  
> @@ -363,8 +406,8 @@ static int tgu_probe(struct amba_device *adev, const struct amba_id *id)
>  {
>  	struct device *dev = &adev->dev;
>  	struct tgu_drvdata *drvdata;
> -	size_t priority_size, condition_size;
> -	unsigned int *priority, *condition;
> +	size_t priority_size, condition_size, select_size;
> +	unsigned int *priority, *condition, *select;
>  	int ret;
>  
>  	drvdata = devm_kzalloc(dev, sizeof(*drvdata), GFP_KERNEL);
> @@ -417,6 +460,16 @@ static int tgu_probe(struct amba_device *adev, const struct amba_id *id)
>  
>  	drvdata->value_table->condition_decode = condition;
>  
> +	select_size = drvdata->max_condition_select * drvdata->max_step *
> +		      sizeof(*(drvdata->value_table->condition_select));
> +
> +	select = devm_kzalloc(dev, select_size, GFP_KERNEL);
> +
> +	if (!select)

stray \n

> +		return -ENOMEM;
> +
> +	drvdata->value_table->condition_select = select;

I don't see a need for an intemediate variable here

[...]

>   * @max_condition_decode: Maximum number of condition_decode
> + * @max_condition_select: Maximum number of condition_select

Maximum value, perhaps? You haven't explained the feature very well
so I'm not sure what this is supposed to reflect

Konrad

  reply	other threads:[~2026-01-13 11:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09  2:11 [PATCH v10 0/7] Provide support for Trigger Generation Unit Songwei Chai
2026-01-09  2:11 ` [PATCH v10 1/7] dt-bindings: arm: Add support for Qualcomm TGU trace Songwei Chai
2026-01-09  2:11 ` [PATCH v10 2/7] qcom-tgu: Add TGU driver Songwei Chai
2026-01-09 10:27   ` Suzuki K Poulose
2026-01-12  1:43     ` Songwei Chai
2026-01-09 11:28   ` Jie Gan
2026-01-12  1:41     ` Songwei Chai
2026-01-13 10:33   ` Konrad Dybcio
2026-01-27  2:13     ` Songwei Chai
2026-01-27 10:35       ` Konrad Dybcio
2026-01-09  2:11 ` [PATCH v10 3/7] qcom-tgu: Add signal priority support Songwei Chai
2026-01-13 11:09   ` Konrad Dybcio
2026-01-27  2:23     ` Songwei Chai
2026-01-27 10:30       ` Konrad Dybcio
2026-01-09  2:11 ` [PATCH v10 4/7] qcom-tgu: Add TGU decode support Songwei Chai
2026-01-13 11:13   ` Konrad Dybcio
2026-01-27  2:34     ` Songwei Chai
2026-01-27 10:31       ` Konrad Dybcio
2026-01-09  2:11 ` [PATCH v10 5/7] qcom-tgu: Add support to configure next action Songwei Chai
2026-01-13 11:15   ` Konrad Dybcio [this message]
2026-01-27  2:43     ` Songwei Chai
2026-01-27 10:32       ` Konrad Dybcio
2026-01-09  2:11 ` [PATCH v10 6/7] qcom-tgu: Add timer/counter functionality for TGU Songwei Chai
2026-01-13 11:19   ` Konrad Dybcio
2026-01-27  3:02     ` Songwei Chai
2026-01-09  2:11 ` [PATCH v10 7/7] qcom-tgu: Add reset node to initialize Songwei Chai
2026-01-13 11:22   ` Konrad Dybcio
2026-01-27  2:50     ` Songwei Chai
2026-01-13  1:53 ` [PATCH v10 0/7] Provide support for Trigger Generation Unit Songwei Chai

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=f211054c-ecb7-4f90-b9ce-9fdd7710c8c4@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=coresight@lists.linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=james.clark@arm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.leach@linaro.org \
    --cc=songwei.chai@oss.qualcomm.com \
    --cc=suzuki.poulose@arm.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