public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
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/1] Add devm_tegra_core_dev_init_opp_table() helper
Date: Sun, 16 May 2021 23:51:37 +0300	[thread overview]
Message-ID: <20210516205138.22501-1-digetx@gmail.com> (raw)

Hello,

This patch adds a new devm_tegra_core_dev_init_opp_table() helper
which is specific to NVIDIA Tegra SoCs. The goal of this helper is to
remove code duplication from Tegra device drivers.

Previously this helper was a part of patchsets that added core power
domain support. Krzysztof Kozlowski suggested to separate patches into
smaller sets with explicit dependencies.

This helper is a mandatory prerequisite by a multiple patchsets that
will add more advanced power management to GPU/media/clk and etc drivers,
fixing overheating troubles of Tegra devices. It provides OPP support
for newer device-trees and preserves compatibility with the older DTBs.

Dmitry Osipenko (1):
  soc/tegra: Add devm_tegra_core_dev_init_opp_table()

 drivers/soc/tegra/common.c | 112 +++++++++++++++++++++++++++++++++++++
 include/soc/tegra/common.h |  30 ++++++++++
 2 files changed, 142 insertions(+)

-- 
2.30.2


             reply	other threads:[~2021-05-16 20:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16 20:51 Dmitry Osipenko [this message]
2021-05-16 20:51 ` [PATCH v1 1/1] soc/tegra: Add devm_tegra_core_dev_init_opp_table() Dmitry Osipenko
2021-05-17  3:37   ` Viresh Kumar
2021-05-17 14:09     ` Dmitry Osipenko
2021-05-18  3:26       ` Viresh Kumar
2021-05-17 11:43   ` Krzysztof Kozlowski
2021-05-17 14:47     ` Dmitry Osipenko
2021-05-17 14:52       ` Krzysztof Kozlowski
2021-05-17 15:23         ` 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=20210516205138.22501-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox