linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: moving gpio driver to drivers/gpio, how to initialize?
Date: Wed, 11 May 2011 16:42:21 +0200	[thread overview]
Message-ID: <20110511144221.GK30963@pengutronix.de> (raw)
In-Reply-To: <20110511142016.GG3188@pulham.picochip.com>

On Wed, May 11, 2011 at 03:20:16PM +0100, Jamie Iles wrote:
> On Wed, May 11, 2011 at 04:11:53PM +0200, Sascha Hauer wrote:
> > I think we mostly agree on moving the gpio drivers from arch/arm to
> > drivers/gpio.  A question we have to answer is how we want to initialize
> > these drivers. On nomadik these are platform drivers, but on i.MX and
> > others platform drivers initialize too late, since the gpio functions
> > are already used at init_machine time. PXA uses sysdev for their gpios,
> > but is this the correct answer?
> 
> The omap gpio driver registers the platform_driver as a 
> postcore_initcall so that it can use GPIO in the machine init for this 
> reason.  A platform_device/driver feels like the right way to do this 
> IMHO.

Ah, I somehow missed that platform drivers can be up and running at
init_machine time. Then this is not a problem at all.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2011-05-11 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 14:11 moving gpio driver to drivers/gpio, how to initialize? Sascha Hauer
2011-05-11 14:20 ` Jamie Iles
2011-05-11 14:42   ` Sascha Hauer [this message]
2011-05-11 16:07   ` Rob Herring

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=20110511144221.GK30963@pengutronix.de \
    --to=s.hauer@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).