From: Sumit Gupta <sumitg@nvidia.com>
To: <krzk@kernel.org>, <treding@nvidia.com>, <jonathanh@nvidia.com>,
<robh@kernel.org>, <conor+dt@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<devicetree@vger.kernel.org>
Cc: <bbasu@nvidia.com>, <sumitg@nvidia.com>
Subject: [PATCH v2 1/3] memory: tegra264: Skip clients without bpmp_id or type
Date: Mon, 18 May 2026 18:13:04 +0530 [thread overview]
Message-ID: <20260518124306.2071481-2-sumitg@nvidia.com> (raw)
In-Reply-To: <20260518124306.2071481-1-sumitg@nvidia.com>
Some MC clients are present in tegra264_mc_clients[] only for
fault-log naming and have no .bpmp_id or .type assigned. Skip
forwarding bandwidth requests to BPMP for such clients in
tegra264_mc_icc_set().
Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
---
drivers/memory/tegra/tegra264.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/memory/tegra/tegra264.c b/drivers/memory/tegra/tegra264.c
index e43ef14da1ee..e62890841725 100644
--- a/drivers/memory/tegra/tegra264.c
+++ b/drivers/memory/tegra/tegra264.c
@@ -262,6 +262,10 @@ static int tegra264_mc_icc_set(struct icc_node *src, struct icc_node *dst)
return -ENOENT;
}
+ /* Skip forwarding bw requests to BPMP from clients without bpmp_id/type. */
+ if (pclient->type == TEGRA_ICC_NONE || !pclient->bpmp_id)
+ return 0;
+
if (pclient->type == TEGRA_ICC_NISO)
bwmgr_req.bwmgr_calc_set_req.niso_bw = src->avg_bw;
else
--
2.34.1
next prev parent reply other threads:[~2026-05-18 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 12:43 [PATCH v2 0/3] memory: tegra264: Add full set of MC clients Sumit Gupta
2026-05-18 12:43 ` Sumit Gupta [this message]
2026-05-18 12:43 ` [PATCH v2 2/3] dt-bindings: memory: tegra264: Add full set of MC client IDs Sumit Gupta
2026-05-18 13:10 ` sashiko-bot
2026-05-18 17:51 ` Sumit Gupta
2026-05-18 12:43 ` [PATCH v2 3/3] memory: tegra264: Add full set of MC clients Sumit Gupta
2026-05-18 13:33 ` sashiko-bot
2026-05-18 18:01 ` Sumit Gupta
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=20260518124306.2071481-2-sumitg@nvidia.com \
--to=sumitg@nvidia.com \
--cc=bbasu@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=treding@nvidia.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