| commit | 24d4076734b4ecf083a6be611040fe0743e59989 | |
| author | Mark Brown <broonie@opensource.wolfsonmicro.com> | |
| Fri, 23 Jan 2009 17:06:23 +0000 (23 17:06 +0000) | ||
| committer | Ben Dooks <ben-linux@fluff.org> | |
| Thu, 26 Feb 2009 23:21:50 +0000 (26 23:21 +0000) | ||
| tree | 0661c58a9ff55916fb0aef8520c137cd85cdd884 | treesnapshot (tar.gz zip) |
| parent | 8bd8dbdf3725ce569467bd704840249869f626d6 | commitdiff |
[ARM] S3C64XX: Do gpiolib configuration earlier
arch_initcall() runs after the machine init function which means that
any configuration of GPIO pins must currently be done later on, for
example in callbacks from drivers. Move the initialisation earlier in
order to allow machines to configure GPIOs directly in their init
functions rather than having to have a callback invoked later on.
Some other ARM platforms use this method. Other solutions for this
include providing a special interface for setting up GPIOs en masse,
adding callbacks to do the GPIO configuration from devices and doing
the GPIO configuration implicitly.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
arch_initcall() runs after the machine init function which means that
any configuration of GPIO pins must currently be done later on, for
example in callbacks from drivers. Move the initialisation earlier in
order to allow machines to configure GPIOs directly in their init
functions rather than having to have a callback invoked later on.
Some other ARM platforms use this method. Other solutions for this
include providing a special interface for setting up GPIOs en masse,
adding callbacks to do the GPIO configuration from devices and doing
the GPIO configuration implicitly.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
| arch/arm/plat-s3c64xx/gpiolib.c | diffblobblamehistory |