devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: James Liao <jamesjj.liao@mediatek.com>,
	devicetree@vger.kernel.org, srv_heupstream@mediatek.com,
	Kevin Hilman <khilman@kernel.org>,
	linux-kernel@vger.kernel.org, Daniel Kurtz <djkurtz@chromium.org>,
	linux-mediatek@lists.infradead.org,
	Sascha Hauer <kernel@pengutronix.de>,
	Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH 2/4] soc: mediatek: Init MT8173 scpsys driver earlier
Date: Wed, 30 Dec 2015 11:35:01 +0100	[thread overview]
Message-ID: <6145950.8rtkDup7QD@wuerfel> (raw)
In-Reply-To: <1451470328.22426.5.camel@mtksdaap41>

On Wednesday 30 December 2015 18:12:08 James Liao wrote:
> On Wed, 2015-12-30 at 09:52 +0100, Arnd Bergmann wrote:
> > On Wednesday 30 December 2015 14:41:44 James Liao wrote:
> > > Some power domain comsumers may init before module_init.
> > > So the power domain provider (scpsys) need to be initialized
> > > earlier too.
> > > 
> > > Signed-off-by: James Liao <jamesjj.liao@mediatek.com>
> > > ---
> > > 
> > 
> > Why?
> 
> Some drivers use different init level to ensure they can be initialized
> before other drivers. To support these drivers, moving scpsys driver's
> initial function to subsys_init is the most easy way.

This is just the same generic explanation that you already have.

Please be more specific what the dependency is and why we can't rely
on deferred probing here.

	Arnd

  reply	other threads:[~2015-12-30 10:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30  6:41 [PATCH 0/4] Mediatek MT2701 SCPSYS power domain support James Liao
     [not found] ` <1451457706-14798-1-git-send-email-jamesjj.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-12-30  6:41   ` [PATCH 1/4] soc: mediatek: Separate scpsys driver common code James Liao
2015-12-30  8:52     ` Arnd Bergmann
2015-12-30 10:08       ` James Liao
2015-12-30  6:41   ` [PATCH 2/4] soc: mediatek: Init MT8173 scpsys driver earlier James Liao
     [not found]     ` <1451457706-14798-3-git-send-email-jamesjj.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-12-30  8:52       ` Arnd Bergmann
2015-12-30 10:12         ` James Liao
2015-12-30 10:35           ` Arnd Bergmann [this message]
2015-12-31  5:59             ` James Liao
2015-12-31  9:16               ` James Liao
2015-12-31 14:45                 ` Arnd Bergmann
2016-01-04  2:52                   ` James Liao
2015-12-30  6:41   ` [PATCH 3/4] soc: mediatek: Add MT2701 power dt-bindings James Liao
2015-12-30  6:41   ` [PATCH 4/4] soc: mediatek: Add MT2701/MT7623 scpsys driver James Liao
     [not found]     ` <1451457706-14798-5-git-send-email-jamesjj.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-12-30  9:01       ` Daniel Kurtz
2015-12-30 10:18         ` James Liao
2015-12-30 17:49           ` Matthias Brugger
2016-01-05  5:23             ` James Liao
2016-01-08 11:26               ` Matthias Brugger

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=6145950.8rtkDup7QD@wuerfel \
    --to=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=djkurtz@chromium.org \
    --cc=jamesjj.liao@mediatek.com \
    --cc=kernel@pengutronix.de \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=srv_heupstream@mediatek.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).