From: <Claudiu.Beznea@microchip.com>
To: <broonie@kernel.org>
Cc: <Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<Ludovic.Desroches@microchip.com>, <linux@armlinux.org.uk>,
<lgirdwood@gmail.com>, <rjw@rjwysocki.net>, <pavel@ucw.cz>,
<len.brown@intel.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] regulator: core: add helper to check if regulator is disabled in suspend
Date: Tue, 15 Jan 2019 09:19:15 +0000 [thread overview]
Message-ID: <6cce226c-882a-9356-7be6-769d30ef0380@microchip.com> (raw)
In-Reply-To: <20190114225311.GJ11073@sirena.org.uk>
On 15.01.2019 00:53, Mark Brown wrote:
> On Fri, Jan 11, 2019 at 02:08:19PM +0000, Claudiu.Beznea@microchip.com wrote:
>> On 11.01.2019 14:39, Mark Brown wrote:
>
>>> Like I say I'm working offline so I can't check the links but it sounds
>>> like you're saying that the existing suspend mode configuration features
>>> are enough for your systems?
>
>> Yes, if we rely on the fact that core's regulator device tree bindings for
>> suspend-to-mem/suspend-to-standby were filled correctly.
>
>> The function I added here was to double check that core's regulator will be
>> off in suspend/standby based on what was parsed from DT.
>
> Ah, so it's being used as a consistency check?
Yes, that was the idea.
Thank you,
Claudiu Beznea
> OK, that does make sense
> to me.
>
WARNING: multiple messages have this Message-ID (diff)
From: <Claudiu.Beznea@microchip.com>
To: broonie@kernel.org
Cc: Nicolas.Ferre@microchip.com, alexandre.belloni@bootlin.com,
Ludovic.Desroches@microchip.com, linux@armlinux.org.uk,
lgirdwood@gmail.com, rjw@rjwysocki.net, pavel@ucw.cz,
len.brown@intel.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 2/3] regulator: core: add helper to check if regulator is disabled in suspend
Date: Tue, 15 Jan 2019 09:19:15 +0000 [thread overview]
Message-ID: <6cce226c-882a-9356-7be6-769d30ef0380@microchip.com> (raw)
In-Reply-To: <20190114225311.GJ11073@sirena.org.uk>
On 15.01.2019 00:53, Mark Brown wrote:
> On Fri, Jan 11, 2019 at 02:08:19PM +0000, Claudiu.Beznea@microchip.com wrote:
>> On 11.01.2019 14:39, Mark Brown wrote:
>
>>> Like I say I'm working offline so I can't check the links but it sounds
>>> like you're saying that the existing suspend mode configuration features
>>> are enough for your systems?
>
>> Yes, if we rely on the fact that core's regulator device tree bindings for
>> suspend-to-mem/suspend-to-standby were filled correctly.
>
>> The function I added here was to double check that core's regulator will be
>> off in suspend/standby based on what was parsed from DT.
>
> Ah, so it's being used as a consistency check?
Yes, that was the idea.
Thank you,
Claudiu Beznea
> OK, that does make sense
> to me.
>
WARNING: multiple messages have this Message-ID (diff)
From: <Claudiu.Beznea@microchip.com>
To: <broonie@kernel.org>
Cc: len.brown@intel.com, alexandre.belloni@bootlin.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
rjw@rjwysocki.net, lgirdwood@gmail.com,
Ludovic.Desroches@microchip.com, pavel@ucw.cz,
linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/3] regulator: core: add helper to check if regulator is disabled in suspend
Date: Tue, 15 Jan 2019 09:19:15 +0000 [thread overview]
Message-ID: <6cce226c-882a-9356-7be6-769d30ef0380@microchip.com> (raw)
In-Reply-To: <20190114225311.GJ11073@sirena.org.uk>
On 15.01.2019 00:53, Mark Brown wrote:
> On Fri, Jan 11, 2019 at 02:08:19PM +0000, Claudiu.Beznea@microchip.com wrote:
>> On 11.01.2019 14:39, Mark Brown wrote:
>
>>> Like I say I'm working offline so I can't check the links but it sounds
>>> like you're saying that the existing suspend mode configuration features
>>> are enough for your systems?
>
>> Yes, if we rely on the fact that core's regulator device tree bindings for
>> suspend-to-mem/suspend-to-standby were filled correctly.
>
>> The function I added here was to double check that core's regulator will be
>> off in suspend/standby based on what was parsed from DT.
>
> Ah, so it's being used as a consistency check?
Yes, that was the idea.
Thank you,
Claudiu Beznea
> OK, that does make sense
> to me.
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-15 9:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 10:56 [PATCH v2 0/3] add support for power off check in suspend Claudiu.Beznea
2019-01-08 10:56 ` Claudiu.Beznea
2019-01-08 10:56 ` Claudiu.Beznea
2019-01-08 10:56 ` [PATCH v2 1/3] PM / Suspend: Add support to check if platform's power is off " Claudiu.Beznea
2019-01-08 10:56 ` Claudiu.Beznea
2019-01-08 10:56 ` Claudiu.Beznea
2019-01-09 14:14 ` Pavel Machek
2019-01-09 14:14 ` Pavel Machek
2019-01-10 10:24 ` Claudiu.Beznea
2019-01-10 10:24 ` Claudiu.Beznea
2019-01-10 10:24 ` Claudiu.Beznea
2019-01-08 10:56 ` [PATCH v2 2/3] regulator: core: add helper to check if regulator is disabled " Claudiu.Beznea
2019-01-08 10:56 ` Claudiu.Beznea
2019-01-08 10:56 ` Claudiu.Beznea
2019-01-09 16:57 ` Mark Brown
2019-01-09 16:57 ` Mark Brown
2019-01-10 10:24 ` Claudiu.Beznea
2019-01-10 10:24 ` Claudiu.Beznea
2019-01-10 10:24 ` Claudiu.Beznea
2019-01-11 12:39 ` Mark Brown
2019-01-11 12:39 ` Mark Brown
2019-01-11 14:08 ` Claudiu.Beznea
2019-01-11 14:08 ` Claudiu.Beznea
2019-01-11 14:08 ` Claudiu.Beznea
2019-01-14 22:53 ` Mark Brown
2019-01-14 22:53 ` Mark Brown
2019-01-15 9:19 ` Claudiu.Beznea [this message]
2019-01-15 9:19 ` Claudiu.Beznea
2019-01-15 9:19 ` Claudiu.Beznea
2019-01-08 10:56 ` [PATCH v2 3/3] ARM: at91: pm: add support for .off_in_suspend Claudiu.Beznea
2019-01-08 10:56 ` Claudiu.Beznea
2019-01-08 10:56 ` Claudiu.Beznea
2019-01-08 11:46 ` [PATCH v2 0/3] add support for power off check in suspend Rafael J. Wysocki
2019-01-08 11:46 ` Rafael J. Wysocki
2019-01-08 14:07 ` Claudiu.Beznea
2019-01-08 14:07 ` Claudiu.Beznea
2019-01-08 14:07 ` Claudiu.Beznea
2019-01-28 9:50 ` Claudiu.Beznea
2019-01-28 9:50 ` Claudiu.Beznea
2019-01-28 9:50 ` Claudiu.Beznea
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=6cce226c-882a-9356-7be6-769d30ef0380@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=len.brown@intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/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.