LKML Archive on lore.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>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] Fix Tegra PMC driver racing with cpuidle driver
Date: Mon, 19 Jul 2021 00:27:04 +0300	[thread overview]
Message-ID: <20210718212706.21659-1-digetx@gmail.com> (raw)

I stumbled upon a problem where tegra-cpuidle driver is probed before
Power Management controller driver in a specific kernel configuration,
implicitly disabling the deepest CPU idling state. This series fixes
that trouble.

Dmitry Osipenko (2):
  soc/tegra: pmc: Prevent racing with cpuilde driver
  cpuidle: tegra: Check whether PMC is ready

 arch/arm/mach-tegra/pm.c        |  2 +-
 arch/arm/mach-tegra/pm.h        |  6 ------
 arch/arm/mach-tegra/tegra.c     |  2 --
 drivers/cpuidle/cpuidle-tegra.c |  3 +++
 drivers/soc/tegra/pmc.c         | 14 +++++++++++++-
 include/soc/tegra/pm.h          |  6 ++++++
 6 files changed, 23 insertions(+), 10 deletions(-)

-- 
2.32.0


             reply	other threads:[~2021-07-18 21:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 21:27 Dmitry Osipenko [this message]
2021-07-18 21:27 ` [PATCH v1 1/2] soc/tegra: pmc: Prevent racing with cpuilde driver Dmitry Osipenko
2021-08-11  9:52   ` Thierry Reding
2021-07-18 21:27 ` [PATCH v1 2/2] cpuidle: tegra: Check whether PMC is ready Dmitry Osipenko
2021-08-11  9:49   ` Thierry Reding
2021-08-14 10:37     ` Daniel Lezcano
2021-08-14 13:45       ` Dmitry Osipenko
2021-08-16  9:53         ` Thierry Reding
2021-08-16 15:32           ` 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=20210718212706.21659-1-digetx@gmail.com \
    --to=digetx@gmail.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --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;
as well as URLs for NNTP newsgroup(s).