From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Paul Fertser <fercerpav@gmail.com>,
Matt Merhar <mattmerhar@protonmail.com>,
Peter Geis <pgwipeout@gmail.com>,
Nicolas Chauvet <kwizart@gmail.com>,
Viresh Kumar <vireshk@kernel.org>,
Stephen Boyd <sboyd@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] Make Tegra memory drivers to use devm_tegra_core_dev_init_opp_table()
Date: Mon, 17 May 2021 00:13:00 +0300 [thread overview]
Message-ID: <20210516211302.32404-1-digetx@gmail.com> (raw)
Tegra20/30 memory drivers could take advantage of the new helper which
initializes OPP table right now [1]. Other memory drivers can't be
switched to the new helper until core voltage scaling will be supported
by the corresponding Tegra SoC generations, for now only Tegra20/30 SoCs
support core voltage scaling in the upstream kernel.
Please note that [1] hasn't been reviewed and merged yet.
[1] https://lore.kernel.org/lkml/20210516205138.22501-1-digetx@gmail.com/T/#m247b51a938244c500d70c38cdb9d44adb5f389a7
Dmitry Osipenko (2):
memory: tegra20-emc: Use devm_tegra_core_dev_init_opp_table()
memory: tegra30-emc: Use devm_tegra_core_dev_init_opp_table()
drivers/memory/tegra/tegra20-emc.c | 48 +++---------------------------
drivers/memory/tegra/tegra30-emc.c | 48 +++---------------------------
2 files changed, 8 insertions(+), 88 deletions(-)
--
2.30.2
next reply other threads:[~2021-05-16 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 21:13 Dmitry Osipenko [this message]
2021-05-16 21:13 ` [PATCH v1 1/2] memory: tegra20-emc: Use devm_tegra_core_dev_init_opp_table() Dmitry Osipenko
2021-05-16 21:13 ` [PATCH v1 2/2] memory: tegra30-emc: " Dmitry Osipenko
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=20210516211302.32404-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=fercerpav@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzk@kernel.org \
--cc=kwizart@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mattmerhar@protonmail.com \
--cc=pgwipeout@gmail.com \
--cc=sboyd@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vireshk@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.