From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8] reset: Add driver for gpio-controlled reset pins
Date: Fri, 26 Jul 2013 12:26:37 +0200 [thread overview]
Message-ID: <1374834397.4013.15.camel@pizza.hi.pengutronix.de> (raw)
In-Reply-To: <CAOesGMgi0j_mPyeBLVHb_QW+DwtAPoFY697eQO3-yp9tnP1vmA@mail.gmail.com>
Am Donnerstag, den 18.07.2013, 11:45 -0700 schrieb Olof Johansson:
> Hi,
>
> On Thu, Jul 18, 2013 at 4:25 AM, Pavel Machek <pavel@denx.de> wrote:
>
> > It sound to me like keeping ammount of -EPROBE_DEFER to minimum is
> > still preferred.
>
> Hand-crafting initcall level ordering of various drivers and subsystem
> is probably an even greater evil though. We've done it in the past,
> but now that we have deferred probe we have the option of not having
> to do it every time, such as this.
>
> You're spending an awful lot of energy arguing over this, but nobody
> has actually shown data of how much deferral is happening -- and that
> it's a real problem. Until someone does so there's no reason to change
> it from the default module init level at all, I'd say.
Alright, I've backed out the arch_initcall change and resent the patch.
If you are fine with that, I'll send you a pull request for this and the
"reset: allow drivers to request probe deferral" patch.
regards
Philipp
next prev parent reply other threads:[~2013-07-26 10:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 9:09 [PATCH v8] reset: Add driver for gpio-controlled reset pins Philipp Zabel
2013-05-30 10:37 ` Pavel Machek
2013-07-16 1:50 ` Shawn Guo
2013-07-16 3:35 ` Stephen Warren
2013-07-16 4:10 ` Shawn Guo
2013-07-16 9:49 ` Philipp Zabel
2013-07-16 12:56 ` Shawn Guo
2013-07-16 15:45 ` Stephen Warren
2013-07-17 3:02 ` Shawn Guo
2013-07-17 16:57 ` Stephen Warren
2013-07-17 21:38 ` Pavel Machek
2013-07-17 22:24 ` Stephen Warren
2013-07-18 11:25 ` Pavel Machek
2013-07-18 18:45 ` Olof Johansson
2013-07-19 3:23 ` Shawn Guo
2013-07-19 15:45 ` Stephen Warren
2013-07-22 7:47 ` Shawn Guo
2013-07-26 10:26 ` Philipp Zabel [this message]
2013-07-18 22:55 ` Grant Likely
2013-07-18 22:50 ` Grant Likely
2013-07-16 9:59 ` Philipp Zabel
2013-07-16 15:48 ` Stephen Warren
2013-07-16 6:51 ` Shawn Guo
2013-07-16 9:51 ` Philipp Zabel
2013-07-16 12:15 ` Shawn Guo
2013-07-16 15:47 ` Stephen Warren
2013-07-17 3:43 ` Shawn Guo
2013-07-17 7:17 ` Philipp Zabel
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=1374834397.4013.15.camel@pizza.hi.pengutronix.de \
--to=p.zabel@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).