linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] soc: Mediatek: Add SCPSYS power domain driver
Date: Wed, 20 May 2015 16:03:25 +0200	[thread overview]
Message-ID: <20150520140325.GN6325@pengutronix.de> (raw)
In-Reply-To: <CABuKBeKiw8MkG5kWaUBqfDzopwvrX8Kh8XpNfRiC_uJD67OcEg@mail.gmail.com>

On Tue, May 19, 2015 at 01:06:10PM +0200, Matthias Brugger wrote:
> 2015-05-19 12:30 GMT+02:00 Sascha Hauer <s.hauer@pengutronix.de>:
> >
> > I'll check for errors next round. However, I cannot bail out in this
> > case since once pm_genpd_init() is called the domain cannot be
> > unregistered anymore.
> 
> We should think of implementing this.
> I had a quick look on it, and from what I understand as long as you
> don't have any subdomains, devices and masters added, it's just
> deleting an element from a linked list.

In my error path I would have subdomains added though, so I would need
that to be handled.

> Maybe we should split this in pm_genpd_prepare and pm_genpd_add, with
> the last one actually adding the generic_pm_domain to gpd_list.
> 
> This way we could also get rid of the two for loops.

Well, with pm_genpd_prepare and pm_genpd_add I would still need two
loops, one for preparing and one for adding.

I'm not sure how useful it really is to be able to unregister power
domains. For now I suggest to continue with the domains that are
successfully registered. I'll look into it should the pm domain
maintainers request it.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2015-05-20 14:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 19:23 [PATCH v2] Mediatek SCPSYS power domain support Sascha Hauer
2015-05-11 19:23 ` [PATCH 1/5] soc: mediatek: Add infracfg misc driver support Sascha Hauer
2015-05-12  7:12   ` Sascha Hauer
2015-05-12  9:24   ` Paul Bolle
2015-05-12 13:26     ` Sascha Hauer
2015-05-15 14:17   ` Daniel Kurtz
2015-05-18  8:16     ` Sascha Hauer
2015-05-19  6:54       ` Daniel Kurtz
2015-05-19  7:45         ` Sascha Hauer
2015-05-19 10:39           ` Daniel Kurtz
2015-05-26 23:12   ` Kevin Hilman
2015-05-27  7:33     ` Sascha Hauer
2015-05-11 19:23 ` [PATCH 2/5] dt-bindings: soc: Add documentation for the MediaTek SCPSYS unit Sascha Hauer
2015-05-11 19:23 ` [PATCH 3/5] soc: Mediatek: Add SCPSYS power domain driver Sascha Hauer
2015-05-12 11:52   ` Matthias Brugger
2015-05-12 13:47     ` Sascha Hauer
2015-05-15 14:17   ` Daniel Kurtz
2015-05-19 10:30     ` Sascha Hauer
2015-05-19 11:06       ` Matthias Brugger
2015-05-20 14:03         ` Sascha Hauer [this message]
2015-05-20 16:06           ` Matthias Brugger
2015-05-11 19:23 ` [PATCH 4/5] ARM64: MediaTek: Add generic pm domain support Sascha Hauer
2015-05-11 19:23 ` [PATCH 5/5] ARM64: MediaTek MT8173: Add SCPSYS device node Sascha Hauer
  -- strict thread matches above, loose matches on Subject: below --
2015-05-20 14:18 [PATCH v3] Mediatek SCPSYS power domain support Sascha Hauer
2015-05-20 14:18 ` [PATCH 3/5] soc: Mediatek: Add SCPSYS power domain driver Sascha Hauer
2015-05-21  8:22   ` Paul Bolle
2015-06-09  8:42     ` Sascha Hauer
2015-06-09  8:46 [PATCH v4] Mediatek SCPSYS power domain support Sascha Hauer
2015-06-09  8:47 ` [PATCH 3/5] soc: Mediatek: Add SCPSYS power domain driver Sascha Hauer
2015-06-10 12:03   ` Matthias Brugger
2015-06-10 14:47   ` Ulf Hansson
2015-06-15  7:45     ` Sascha Hauer

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=20150520140325.GN6325@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).