From: Thierry Reding <thierry.reding@gmail.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: Sebastian Reichel <sre@kernel.org>,
Martin Michlmayr <tbm@cyrius.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Chaitanya Bandi <bandik@nvidia.com>
Subject: Re: [PATCH] power: reset: Add MAX77620 support
Date: Thu, 19 Jan 2017 13:27:44 +0100 [thread overview]
Message-ID: <20170119122744.GG30182@ulmo.ba.sec> (raw)
In-Reply-To: <5877BE49.2010008@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
On Thu, Jan 12, 2017 at 11:05:05PM +0530, Laxman Dewangan wrote:
>
> On Thursday 12 January 2017 11:05 PM, Thierry Reding wrote:
> > * PGP Signed by an unknown key
> >
> > On Thu, Jan 12, 2017 at 10:06:24PM +0530, Laxman Dewangan wrote:
> > > On Thursday 12 January 2017 09:45 PM, Thierry Reding wrote:
> > > >
> > > > + dev_dbg(&pdev->dev, "event recorder: %#x\n", value);
> > > > +
> > > > + system_power_controller = power;
> > > > + pm_power_off = max77620_pm_power_off;
> > > > +#if defined(CONFIG_ARM) || defined(CONFIG_ARM64)
> > > > + arm_pm_restart = max77620_pm_restart;
> > > What if we want to reset via the Tegra and not through PMIC?
> > In that case I assume we either don't have a PMIC, or we should not add
> > the system-power-controller device tree property to the PMIC node. In
> > the latter case this driver won't install any power off or restart
> > callbacks.
>
>
> We need reset from Tegra and power of from PMIC. Tegra does not support
> power OFF.
Can you explain in more details what exactly the combination is that we
need to support? Why can't the PMIC both be the reset and power off
controller? Are there any advantages to resetting with the SoC rather
than the PMIC?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-19 12:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 16:15 [PATCH] power: reset: Add MAX77620 support Thierry Reding
2017-01-12 16:36 ` Laxman Dewangan
2017-01-12 17:35 ` Thierry Reding
2017-01-12 17:35 ` Laxman Dewangan
2017-01-19 12:27 ` Thierry Reding [this message]
2017-01-13 3:44 ` Sebastian Reichel
2017-01-19 12:23 ` Thierry Reding
2017-01-19 23:00 ` Sebastian Reichel
2017-01-19 23:29 ` Guenter Roeck
2017-01-20 8:38 ` Thierry Reding
2017-01-20 17:53 ` Guenter Roeck
2017-01-29 20:02 ` Sebastian Reichel
2017-01-29 20:47 ` Guenter Roeck
2017-01-29 22:43 ` Sebastian Reichel
2017-01-20 12:44 ` Sebastian Reichel
2017-01-20 13:11 ` Thierry Reding
2017-01-20 13:47 ` Sebastian Reichel
2017-01-20 14:32 ` Guenter Roeck
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=20170119122744.GG30182@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=bandik@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@kernel.org \
--cc=tbm@cyrius.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).