All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Dmitry Osipenko <digetx@gmail.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Nicolas Chauvet <kwizart@gmail.com>,
	Matt Merhar <mattmerhar@protonmail.com>,
	Peter Geis <pgwipeout@gmail.com>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] reset: Add devm_reset_control_get_optional_exclusive_released()
Date: Mon, 25 Jan 2021 17:46:21 +0100	[thread overview]
Message-ID: <8432b6e84b2a4acd500c88228c37ba573330b235.camel@pengutronix.de> (raw)
In-Reply-To: <20210123163445.24474-1-digetx@gmail.com>

Hi Dmitry,

On Sat, 2021-01-23 at 19:34 +0300, Dmitry Osipenko wrote:
> NVIDIA Tegra DRM and media drivers will need a resource-managed-optional
> variant of reset_control_get_exclusive_released() in order to switch away
> from a legacy Tegra-specific PD API to a GENPD API without much hassle.
> Add the new reset helper to the reset API.
> 
> Tested-by: Peter Geis <pgwipeout@gmail.com> # Ouya T30
> Tested-by: Nicolas Chauvet <kwizart@gmail.com> # PAZ00 T20
> Tested-by: Matt Merhar <mattmerhar@protonmail.com> # Ouya T30
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
> 
> Hello Philipp,
> 
> This patch is a prerequisite for a power domain enablement using
> GENPD API on NVIDIA Tegra20/30 SoCs. The hardware resets are acquired
> by a Tegra PMC (Power Management Controller) driver until device is
> RPM-resumed if GENPD API is used, and thus, device drivers need to
> request resets in a released state. The resets are also optional,
> depending on hardware and DTB versions. This is why we will need the
> new helper. Will be awesome if you could pick up this patch for v5.12,
> this will help to avoid inter-subsystem dependencies for the driver
> patches that will target v5.13. Thanks in advance!

Thank you, looks good to me. Applied to reset/next for v5.12.

regards
Philipp

      reply	other threads:[~2021-01-26  2:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-23 16:34 [PATCH v1] reset: Add devm_reset_control_get_optional_exclusive_released() Dmitry Osipenko
2021-01-25 16:46 ` Philipp Zabel [this message]

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=8432b6e84b2a4acd500c88228c37ba573330b235.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --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=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 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.