mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] regulator: fixed: take regulator-boot-on into account
Date: Mon, 3 Feb 2020 09:12:39 +0100	[thread overview]
Message-ID: <20200203081239.vwo26e2fbgse5tkr@pengutronix.de> (raw)
In-Reply-To: <20200129113823.8304-1-m.felsch@pengutronix.de>

On Wed, Jan 29, 2020 at 12:38:23PM +0100, Marco Felsch wrote:
> There are regulators which are turned on by default (hw-design) and
> shouldn't be disabled during the boot. Upstream uses the
> regulator-boot-on dt-property for it:
> 
> 8<--------------------------------------------------
>   regulator-boot-on:
>     description: bootloader/firmware enabled regulator
>     type: boolean
> 8<--------------------------------------------------
> 
> The difference between boot-on and always-on is the linux suspend
> handling. Regulators marked as boot-on can be disabled during suspend.
> This case isn't interesting for barebox so we can mark those as
> always-on too.
> 
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> ---
>  drivers/regulator/fixed.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

Applied, thanks

Sascha


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2020-02-03  8:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 11:38 Marco Felsch
2020-02-03  8:12 ` Sascha Hauer [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=20200203081239.vwo26e2fbgse5tkr@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=m.felsch@pengutronix.de \
    /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