From: Dmitry Osipenko <digetx@gmail.com>
To: Sowjanya Komatineni <skomatineni@nvidia.com>,
thierry.reding@gmail.com, jonathanh@nvidia.com, sboyd@kernel.org,
mturquette@baylibre.com, pgaikwad@nvidia.com
Cc: pdeschrijver@nvidia.com, linux-tegra@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] clk: tegra: clk-dfll: Fix to remove pm_runtime_irq_safe
Date: Wed, 13 Nov 2019 19:22:39 +0300 [thread overview]
Message-ID: <353b9aef-3bcc-65d2-a942-91d6710b89ca@gmail.com> (raw)
In-Reply-To: <1573575426-31314-2-git-send-email-skomatineni@nvidia.com>
12.11.2019 19:17, Sowjanya Komatineni пишет:
> pm_runtime_irq_safe is not needed as interrupts are allowed during
> suspend and resume. This was added mistakenly during dfll suspend
> and resume support patch.
>
> This patch includes fix to remove pm_runtime_irq_safe.
>
> Also updated description of dfll_suspend argument.
>
> Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
> ---
> drivers/clk/tegra/clk-dfll.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/clk/tegra/clk-dfll.c b/drivers/clk/tegra/clk-dfll.c
> index c051d92c2bbf..cfbaa90c7adb 100644
> --- a/drivers/clk/tegra/clk-dfll.c
> +++ b/drivers/clk/tegra/clk-dfll.c
> @@ -1487,7 +1487,6 @@ static int dfll_init(struct tegra_dfll *td)
> td->last_unrounded_rate = 0;
>
> pm_runtime_enable(td->dev);
> - pm_runtime_irq_safe(td->dev);
> pm_runtime_get_sync(td->dev);
>
> dfll_set_mode(td, DFLL_DISABLED);
> @@ -1516,7 +1515,7 @@ static int dfll_init(struct tegra_dfll *td)
>
> /**
> * tegra_dfll_suspend - check DFLL is disabled
> - * @dev: DFLL device *
> + * @dev: DFLL instance
> *
> * DFLL clock should be disabled by the CPUFreq driver. So, make
> * sure it is disabled and disable all clocks needed by the DFLL.
>
Hello Sowjanya,
It should be better to have the commit's title saying something more
generic like "Clean up code" or to have two separate patches because
this patch does two things that are unrelated to each other in
accordance to the title and this is a bit confusing at first glance.
Although, that's not a big deal for a trivial patch like this and it
should be fine as is (IMO). Please take into account in the future
patches that both commit's title and description should be accurate.
Reviewed-by: Dmitry Osipenko <digetx@gmail.com>
next prev parent reply other threads:[~2019-11-13 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 16:17 [PATCH v1] clk: tegra: clk-dfll: Fix to remove pm_runtime_irq_safe Sowjanya Komatineni
2019-11-12 16:17 ` Sowjanya Komatineni
2019-11-13 16:22 ` Dmitry Osipenko [this message]
2019-11-12 22:46 ` Stephen Boyd
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=353b9aef-3bcc-65d2-a942-91d6710b89ca@gmail.com \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=sboyd@kernel.org \
--cc=skomatineni@nvidia.com \
--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