From: Dmitry Osipenko <digetx@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] memory: tegra: Remove calls to dev_pm_opp_set_clkname()
Date: Wed, 27 Jan 2021 22:27:20 +0300 [thread overview]
Message-ID: <7daaf77c-4ba0-0c69-1028-49518eb44d18@gmail.com> (raw)
In-Reply-To: <0f22cc1791d8b88c50a9790c2dc19455b34ec7b0.1611742564.git.viresh.kumar@linaro.org>
27.01.2021 13:16, Viresh Kumar пишет:
> There is no point calling dev_pm_opp_set_clkname() with the "name"
> parameter set to NULL, this is already done by the OPP core at setup
> time and should work as it is.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> ---
> V2: Update tegra124 as well.
>
> Krzysztof, please take this through your tree, it doesn't have any
> dependency in the OPP tree.
> ---
> drivers/memory/tegra/tegra124-emc.c | 13 ++-----------
> drivers/memory/tegra/tegra20-emc.c | 13 ++-----------
> drivers/memory/tegra/tegra30-emc.c | 13 ++-----------
> 3 files changed, 6 insertions(+), 33 deletions(-)
Ideally drivers should be able to ensure that OPP table received the
clk, IMO. But this is also almost fine with me since realistically
clk_get() shouldn't fail if it already succeeded a moment ago.
Reviewed-by: Dmitry Osipenko <digetx@gmail.com>
Tested-by: Dmitry Osipenko <digetx@gmail.com>
Could we please fix the _allocate_opp_table() to not ignore clk_get()
errors like -ENOMEM and etc?
next prev parent reply other threads:[~2021-01-27 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 10:16 Viresh Kumar
2021-01-27 19:27 ` Dmitry Osipenko [this message]
2021-01-28 4:18 ` Viresh Kumar
2021-01-29 6:59 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2021-01-22 6:00 Viresh Kumar
2021-01-22 15:00 ` Dmitry Osipenko
2021-01-25 3:10 ` Viresh Kumar
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=7daaf77c-4ba0-0c69-1028-49518eb44d18@gmail.com \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
/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®