From: Nicolas Schichan <nschichan@freebox.fr>
To: Alexandre Courbot <acourbot@nvidia.com>, linux-mips@linux-mips.org
Cc: Maxime Bizon <mbizon@freebox.fr>
Subject: bcm63xx gpio issue on 3.19
Date: Mon, 09 Mar 2015 18:53:04 +0100 [thread overview]
Message-ID: <54FDDE00.7030100@freebox.fr> (raw)
Hello Alexandre,
Using the latest 3.19 kernel, the bcm63xx GPIO code under
arch/mips/bcm63xx/gpio.c is unable to register the gpio chip via
gpiochip_add(), as it returns -ENOMEM. The kcalloc call for the gpio_desc
array fails, as during prom code, it is too early for the kmalloc to work.
It looks like the issue is caused by your patch: "gpio: remove gpio_descs
global array"
Could you please advise on how to fix/workaround that ? (ideally while keeping
the possibility to invoke the gpiolib code from the setup/prom code).
Regards,
--
Nicolas Schichan
Freebox SAS
next reply other threads:[~2015-03-09 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 17:53 Nicolas Schichan [this message]
2015-03-11 5:23 ` bcm63xx gpio issue on 3.19 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
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=54FDDE00.7030100@freebox.fr \
--to=nschichan@freebox.fr \
--cc=acourbot@nvidia.com \
--cc=linux-mips@linux-mips.org \
--cc=mbizon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox