From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] dm: core: Add a flag for power domain control on device removal
Date: Tue, 18 Feb 2020 20:42:07 +0100 [thread overview]
Message-ID: <20200218204156.52304aaa@crub> (raw)
In-Reply-To: <CAPnjgZ38Bg5ObSZz8sJQVipJAXJoj1xknbQuqUPrEdsJ__ohdw@mail.gmail.com>
Hi Simon,
On Tue, 18 Feb 2020 11:31:26 -0700
Simon Glass sjg at chromium.org wrote:
> Hi Anatolij,
>
> On Mon, 17 Feb 2020 at 04:36, Anatolij Gustschin <agust@denx.de> wrote:
> >
> > In various cases a power domain must stay enabled after device
> > removal when booting OS (i.e. serial debug console or display).
> > Add a flag to selectively skip switching off a power domain.
> >
> > Fixes: 52edfed65de9 ("dm: core: device: switch off power domain after device removal")
> > Signed-off-by: Anatolij Gustschin <agust@denx.de>
> > ---
> > drivers/core/device-remove.c | 5 +++--
> > include/dm/device.h | 6 ++++++
> > 2 files changed, 9 insertions(+), 2 deletions(-)
>
> This seems OK. Should we add a device tree property for this? Or is
> the driver-level side enough.
For all potential users I'm currently aware of the driver-level
side is enough. Should this ever be required per device, then we
can add a property later.
--
Anatolij
next prev parent reply other threads:[~2020-02-18 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 11:36 [PATCH 1/2] dm: core: Add a flag for power domain control on device removal Anatolij Gustschin
2020-02-17 11:36 ` [PATCH 2/2] video: meson: keep power domain up after booting Anatolij Gustschin
2020-02-17 16:55 ` Neil Armstrong
2020-03-03 2:46 ` sjg at google.com
2020-02-17 16:55 ` [PATCH 1/2] dm: core: Add a flag for power domain control on device removal Neil Armstrong
2020-02-18 18:31 ` Simon Glass
2020-02-18 19:42 ` Anatolij Gustschin [this message]
2020-02-18 23:59 ` Simon Glass
2020-03-03 2:46 ` sjg at google.com
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=20200218204156.52304aaa@crub \
--to=agust@denx.de \
--cc=u-boot@lists.denx.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