All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Nicolas Schichan <nschichan@freebox.fr>
Cc: Alexandre Courbot <acourbot@nvidia.com>,
	Linux MIPS <linux-mips@linux-mips.org>,
	Maxime Bizon <mbizon@freebox.fr>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: bcm63xx gpio issue on 3.19
Date: Wed, 18 Mar 2015 11:02:48 +0100	[thread overview]
Message-ID: <CACRpkdYqkZAyV1kXVHWYP8TCSqRF9X7fLOcsKNu8wL7t0MX2Mg@mail.gmail.com> (raw)
In-Reply-To: <5500803A.7080409@freebox.fr>

On Wed, Mar 11, 2015 at 6:49 PM, Nicolas Schichan <nschichan@freebox.fr> wrote:

> Moving the bcm63xx_gpio_init() call from board_prom_init() to
> bcm63xx_register_devices() (an arch_initcall) is enough to get called when
> kmalloc is working. If code poking GPIOs is invoked earlier by a board code,
> it will have to move in the board_register_devices() function though there
> doesn't seem to any problems with the mainline bcm63xx board code in that regard.
>
> I can produce a patch for that if it is an accepted solution. It has the
> advantage of not requiring changes to the gpiolib code.

It would be *awesome* if you can come up with a patch like this.
Because it makes our life so much more simple.

(Maybe there is already such a patch in my INBOX somewhere...)

Yours,
Linus Walleij

      parent reply	other threads:[~2015-03-18 10:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 17:53 bcm63xx gpio issue on 3.19 Nicolas Schichan
2015-03-11  5:23 ` Alexandre Courbot
2015-03-11  5:23   ` Alexandre Courbot
2015-03-11 17:49   ` Nicolas Schichan
2015-03-12  4:03     ` Alexandre Courbot
2015-03-12  4:03       ` Alexandre Courbot
2015-03-18 10:02     ` Linus Walleij [this message]

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=CACRpkdYqkZAyV1kXVHWYP8TCSqRF9X7fLOcsKNu8wL7t0MX2Mg@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=acourbot@nvidia.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mbizon@freebox.fr \
    --cc=nschichan@freebox.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.