From: "Grant Likely" <grant.likely@secretlab.ca>
To: avorontsov@ru.mvista.com
Cc: David Brownell <david-b@pacbell.net>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 4/5] [POWERPC] QE: implement support for the GPIO LIB API
Date: Mon, 21 Apr 2008 15:15:34 -0600 [thread overview]
Message-ID: <fa686aa40804211415q7a477651q3b1b516a5fb262e5@mail.gmail.com> (raw)
In-Reply-To: <20080421164128.GA28561@polina.dev.rtsoft.ru>
On Mon, Apr 21, 2008 at 10:41 AM, Anton Vorontsov
<avorontsov@ru.mvista.com> wrote:
> On Mon, Apr 21, 2008 at 08:58:09AM -0600, Grant Likely wrote:
> > Its not great. It has a boot time impact for every platform compiled
> > into the kernel. The problem gets worse every time another block of
> > code uses this method. Personally I prefer platform code calling it
> > explicitly.
> >
> > Making it an of_platform device would also eliminate that problem, but
> > you'd need a method to synchronize the driver with its users.
> >
> > I'm not going to raise a big stink about it, but the issue should not
> > be ignored.
>
> Heh.. how QE GPIO is different from FSL GTM then? Should I call
> fsl_gtm_init() from the board file too? For the every board? I do
> believe that years later someone will show up with something like this:
>
>
> From: J. Random Hacker
> Subject: [POWERPC] cleanup board initialization code
>
> This patch removes vast amount of machine_arch_initcall()s that were
> used to solely initialize some hardware, like this:
>
> qe_add_gpio_chips();
> fsl_gtm_init();
> fsl_spi_init();
Or have a soc-level helper function for calling them for you; but yes.
And, no, we shouldn't have a vast array of individual initcalls
because the platform code shouldn't be that large. As much as
possible, multiple boards should be supported by the same platform
code. I argue that most boards using the same SoC should use the same
platform code. (see platforms/52xx/mpc5200_simple.c)
Individual calls has the added advantage that if a board port needs
those functions to *not* be called (for whatever reason) then it has
the ability to not call them.
It is for the same reason that the platform code is responsible for
calling of_platform_bus_probe() instead of it being an initcall; it
give the platform code control over the device registrations.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-04-21 21:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 19:06 [PATCH 0/5 v2] Few more patches for Kumar's powerpc.git Anton Vorontsov
2008-04-18 19:09 ` [PATCH 1/5] [POWERPC] sysdev: implement FSL GTM support Anton Vorontsov
2008-04-21 14:03 ` Grant Likely
2008-04-21 14:28 ` Anton Vorontsov
2008-04-21 16:28 ` Segher Boessenkool
2008-04-21 18:39 ` Scott Wood
2008-04-21 23:27 ` Grant Likely
2008-04-18 19:09 ` [PATCH 2/5] [POWERPC] QE: add support for QE USB clocks routing Anton Vorontsov
2008-04-18 19:09 ` [PATCH 3/5] [POWERPC] QE: prepare QE PIO code for GPIO LIB support Anton Vorontsov
2008-04-21 14:08 ` Grant Likely
2008-04-21 14:28 ` Anton Vorontsov
2008-04-18 19:09 ` [PATCH 4/5] [POWERPC] QE: implement support for the GPIO LIB API Anton Vorontsov
2008-04-19 5:49 ` David Brownell
2008-04-21 14:19 ` Grant Likely
2008-04-21 14:33 ` Anton Vorontsov
2008-04-21 14:49 ` Anton Vorontsov
2008-04-21 14:58 ` Grant Likely
2008-04-21 16:41 ` Anton Vorontsov
2008-04-21 20:01 ` David Brownell
2008-04-21 21:33 ` Anton Vorontsov
2008-04-21 22:19 ` David Brownell
2008-04-21 21:15 ` Grant Likely [this message]
2008-04-21 16:30 ` Segher Boessenkool
2008-04-18 19:10 ` [PATCH 5/5] [POWERPC] 83xx: new board support: MPC8360E-RDK Anton Vorontsov
2008-04-21 21:05 ` Grant Likely
2008-04-21 22:04 ` Anton Vorontsov
-- strict thread matches above, loose matches on Subject: below --
2008-04-17 19:26 [PATCH 0/5] Few more patches for Kumar's powerpc.git Anton Vorontsov
2008-04-17 19:29 ` [PATCH 4/5] [POWERPC] QE: implement support for the GPIO LIB API Anton Vorontsov
2008-04-17 22:35 ` Kumar Gala
2008-04-17 22:41 ` Anton Vorontsov
2008-04-18 2:21 ` Kumar Gala
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=fa686aa40804211415q7a477651q3b1b516a5fb262e5@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=avorontsov@ru.mvista.com \
--cc=david-b@pacbell.net \
--cc=linuxppc-dev@ozlabs.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).