From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] memory: tegra: Add support for DBB clock on Tegra264
Date: Fri, 16 Jan 2026 13:15:11 +0000 [thread overview]
Message-ID: <7510a358-608a-475f-9f71-50fa72a72d27@nvidia.com> (raw)
In-Reply-To: <20260116123732.140813-1-thierry.reding@gmail.com>
On 16/01/2026 12:37, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The DBB clock is needed by many IP blocks in order to access system
> memory via the data backbone. The memory controller and external memory
> controllers are the central place where these accesses are managed, so
> make sure that the clock can be controlled from the corresponding
> driver.
>
> Note that not all drivers fully register bandwidth requests, and hence
> the EMC driver doesn't have enough information to know when it's safe to
> switch the clock off, so for now it will be kept on permanently.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Changes in v2:
> - convert to dev_err_probe() (Krzysztof)
>
> drivers/memory/tegra/tegra186-emc.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/memory/tegra/tegra186-emc.c b/drivers/memory/tegra/tegra186-emc.c
> index dfddceecdd1a..03ebab6fbe68 100644
> --- a/drivers/memory/tegra/tegra186-emc.c
> +++ b/drivers/memory/tegra/tegra186-emc.c
> @@ -22,6 +22,7 @@ struct tegra186_emc {
> struct tegra_bpmp *bpmp;
> struct device *dev;
> struct clk *clk;
> + struct clk *clk_dbb;
>
> struct tegra186_emc_dvfs *dvfs;
> unsigned int num_dvfs;
> @@ -328,6 +329,13 @@ static int tegra186_emc_probe(struct platform_device *pdev)
> goto put_bpmp;
> }
>
> + emc->clk_dbb = devm_clk_get_optional_enabled(&pdev->dev, "dbb");
> + if (IS_ERR(emc->clk_dbb)) {
> + err = dev_err_probe(&pdev->dev, PTR_ERR(emc->clk_dbb),
> + "failed to get DBB clock\n");
> + goto put_bpmp;
> + }
> +
> platform_set_drvdata(pdev, emc);
> emc->dev = &pdev->dev;
>
Looks good to me!
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2026-01-16 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 12:37 Thierry Reding
2026-01-16 13:15 ` Jon Hunter [this message]
2026-01-18 18:13 ` Krzysztof Kozlowski
2026-02-24 11:01 ` Krzysztof Kozlowski
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=7510a358-608a-475f-9f71-50fa72a72d27@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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®