From: Tony Lindgren <tony@atomide.com>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: Grant Likely <grant.likely@secretlab.ca>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH 01/10] GPIO: gpio-generic: Move initialization up to postcore
Date: Mon, 12 Dec 2011 15:55:44 -0800 [thread overview]
Message-ID: <20111212235544.GM32251@atomide.com> (raw)
In-Reply-To: <201112130044.02007.jkrzyszt@tis.icnet.pl>
* Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> [111212 15:13]:
> On Tuesday 13 of December 2011 at 00:15:20, Tony Lindgren wrote:
> >
> > Might be worth checking if some board specific __initcall helps here
> > too?
>
> If I only knew how I could insert a board specific __initcall between
> two points from where the generic-gpio first, then the 8250 driver, are
> called.
>
> Any hints?
Hmm, can't you do all that in the order you want in
ams_delta_modem_init()? Or make that into a late_initcall so
you have generic-gpio available?
It seems that the pieces of code you're talking about don't need
to be initialized early, just needs to be done in the right
order to get things working.
Regards,
Tony
next prev parent reply other threads:[~2011-12-12 23:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1323634328-856-1-git-send-email-jkrzyszt@tis.icnet.pl>
[not found] ` <1323634328-856-2-git-send-email-jkrzyszt@tis.icnet.pl>
[not found] ` <20111212180456.GF31337@atomide.com>
2011-12-12 23:05 ` [PATCH 01/10] GPIO: gpio-generic: Move initialization up to postcore Janusz Krzysztofik
2011-12-12 23:15 ` Tony Lindgren
2011-12-12 23:44 ` Janusz Krzysztofik
2011-12-12 23:55 ` Tony Lindgren [this message]
2011-12-13 0:15 ` Janusz Krzysztofik
2011-12-14 13:10 ` Janusz Krzysztofik
2011-12-14 18:21 ` Tony Lindgren
2011-12-14 20:07 ` Janusz Krzysztofik
2011-12-14 22:10 ` Tony Lindgren
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=20111212235544.GM32251@atomide.com \
--to=tony@atomide.com \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@suse.de \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.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).