From: arno@natisbad.org (Arnaud Ebalard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: kirkwood: Add support for NETGEAR ReadyNAS Duo v2 using DT
Date: Tue, 19 Mar 2013 07:59:20 +0100 [thread overview]
Message-ID: <87zjxzvprr.fsf@natisbad.org> (raw)
In-Reply-To: <20130319060750.GD21478@lunn.ch> (Andrew Lunn's message of "Tue, 19 Mar 2013 07:07:50 +0100")
Thanks guys,
Andrew Lunn <andrew@lunn.ch> writes:
>> [ 7.599773] USB Power: Failed to request enable GPIO14: -517
>> [ 7.605963] reg-fixed-voltage 1.regulator: Failed to register regulator: -517
>> [ 7.613163] platform 1.regulator: Driver reg-fixed-voltage requests probe deferral
>
> Although this is quite noisy, it is actually not an error. What it is
> saying is that it failed to get the gpio and it will try again
> later. -517 is EDEFERE. It failed, because at this point, the GPIO
> driver has not yet loaded. Later in the boot the gpio driver
> loaded. It around the time you see:
>
> kirkwood-pinctrl f1010000.pinctrl: registered pinctrl driver
>
> At some point, the kernel will retry again to load all drivers which
> failed with EDEFER and the second time the regulator driver should
> load.
Stupid me: I first tried w/ "gpio = <&gpio0 14 0>;", plugged a key to
notice it was not seen, then looked at the logs to discover what seems
to be an error message. Then, I noticed I was addressing gpio0 (as Jason
also pointer) and thought this was the reason changed it for gpio1. At
that point, I should have tested w/ a USB key but instead looked at the
log to check if the message was still here.
Bottome line: it works! I'll resubmit a v2 later this day.
Thanks again.
Cheers,
a+
next prev parent reply other threads:[~2013-03-19 6:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 20:31 [PATCH] ARM: kirkwood: Add support for NETGEAR ReadyNAS Duo v2 using DT Arnaud Ebalard
2013-03-17 20:40 ` Jason Cooper
2013-03-17 20:50 ` Andrew Lunn
2013-03-17 21:23 ` Arnaud Ebalard
2013-03-18 23:10 ` Arnaud Ebalard
2013-03-18 23:44 ` Jason Cooper
2013-03-19 6:07 ` Andrew Lunn
2013-03-19 6:59 ` Arnaud Ebalard [this message]
2013-03-19 19:58 ` [PATCHv2] " Arnaud Ebalard
2013-03-19 21:16 ` Andrew Lunn
2013-03-19 21:50 ` Arnaud Ebalard
2013-03-19 22:28 ` [PATCHv3] " Arnaud Ebalard
2013-03-20 19:42 ` Andrew Lunn
2013-03-28 18:36 ` Jason Cooper
2013-03-28 20:08 ` Arnaud Ebalard
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=87zjxzvprr.fsf@natisbad.org \
--to=arno@natisbad.org \
--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 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.