linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <acourbot@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] ARM: tegra: TN7: relax some regulators
Date: Thu, 19 Jun 2014 09:59:04 -0600	[thread overview]
Message-ID: <53A308C8.2070004@wwwdotorg.org> (raw)
In-Reply-To: <1403164154-1362-1-git-send-email-acourbot@nvidia.com>

On 06/19/2014 01:49 AM, Alexandre Courbot wrote:
> Remove the regulator-always-on property from some regulators that do not
> need it. On recent kernels fixed regulators which supply is always on
> fail registration.

That sounds like a bug in the regulator core, which should be fixed there.

After all, we can fix *new* DTs to work around that behaviour change,
but old DTs are supposed to work with new kernels. Fixing this in the DT
doesn't help that.

  reply	other threads:[~2014-06-19 15:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19  7:49 [PATCH] ARM: tegra: TN7: relax some regulators Alexandre Courbot
2014-06-19 15:59 ` Stephen Warren [this message]
2014-06-19 17:56   ` Mark Brown
2014-06-20  5:26     ` Alexandre Courbot
2014-06-20  6:44       ` Alexandre Courbot
2014-06-20  9:41         ` Mark Brown
2014-06-20  9:49           ` Alexandre Courbot
2014-06-20 13:23             ` Palmas regulator broken (was Re: [PATCH] ARM: tegra: TN7: relax some regulators) Nishanth Menon
2014-06-20 13:54               ` Nishanth Menon
2014-06-20 14:14                 ` Alexandre Courbot
2014-06-20 17:27                   ` Nishanth Menon
2014-06-20 10:16       ` [PATCH] ARM: tegra: TN7: relax some regulators Mark Brown
2014-06-20 10:33         ` Alexandre Courbot

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=53A308C8.2070004@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=acourbot@nvidia.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.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;
as well as URLs for NNTP newsgroup(s).