From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-tegra@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/4] Tegra FUSE clock improvements for 5.15
Date: Tue, 3 Aug 2021 01:13:32 +0300 [thread overview]
Message-ID: <20210802221336.32016-1-digetx@gmail.com> (raw)
Hello,
This series improves handling of the FUSE clock by keeping it enabled only
when necessary.
Dmitry Osipenko (4):
soc/tegra: fuse: Clear fuse->clk on driver probe failure
soc/tegra: fuse: Add runtime PM support
soc/tegra: fuse: Enable fuse clock on suspend for Tegra124
clk: tegra: Remove CLK_IS_CRITICAL flag from fuse clock
drivers/clk/tegra/clk-tegra-periph.c | 6 +--
drivers/soc/tegra/fuse/fuse-tegra.c | 60 +++++++++++++++++++++++++++
drivers/soc/tegra/fuse/fuse-tegra20.c | 11 +++--
drivers/soc/tegra/fuse/fuse-tegra30.c | 16 ++++---
drivers/soc/tegra/fuse/fuse.h | 2 +
5 files changed, 81 insertions(+), 14 deletions(-)
--
2.32.0
next reply other threads:[~2021-08-02 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 22:13 Dmitry Osipenko [this message]
2021-08-02 22:13 ` [PATCH v1 1/4] soc/tegra: fuse: Clear fuse->clk on driver probe failure Dmitry Osipenko
2021-08-02 22:13 ` [PATCH v1 2/4] soc/tegra: fuse: Add runtime PM support Dmitry Osipenko
2021-08-02 22:13 ` [PATCH v1 3/4] soc/tegra: fuse: Enable fuse clock on suspend for Tegra124 Dmitry Osipenko
2021-08-02 22:13 ` [PATCH v1 4/4] clk: tegra: Remove CLK_IS_CRITICAL flag from fuse clock Dmitry Osipenko
2021-08-11 9:58 ` Thierry Reding
2021-08-11 9:57 ` [PATCH v1 0/4] Tegra FUSE clock improvements for 5.15 Thierry Reding
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=20210802221336.32016-1-digetx@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=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