From: johan@kernel.org (Johan Hovold)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: omap: fix 4.7 gpmc networking regression
Date: Sun, 24 Jul 2016 14:10:57 +0200 [thread overview]
Message-ID: <1469362260-20066-1-git-send-email-johan@kernel.org> (raw)
Networking is currently broken for Overo boards due to a regression in
4.7. I bisected it down to
d2d00862dfbb ("memory: omap-gpmc: Support general purpose input
for WAITPINs")
which changed how errors when probing gpmc child nodes are handled.
Instead of proceeding with setting up any other children as before, a
single error now aborts the whole process.
Due to an unrelated issue with a nand gpmc-node, this change broke
networking for Overo Tobi and other Overo boards with gpmc ethernet:
[ 0.823364] omap-gpmc 6e000000.gpmc: GPMC revision 5.0
[ 0.823822] gpmc_mem_init: disabling cs 0 mapped at 0x0-0x1000000
[ 0.823974] gpiochip_find_base: found new base at 508
[ 0.824096] gpio gpiochip6: (omap-gpmc): added GPIO chardev (254:6)
[ 0.827148] gpiochip_setup_dev: registered GPIOs 508 to 511 on device: gpiochip6 (omap-gpmc)
[ 0.827362] omap-gpmc 6e000000.gpmc: /ocp/gpmc at 6e000000/nand at 0,0 has malformed 'reg' property
[ 0.827392] omap-gpmc 6e000000.gpmc: failed to probe DT children
This series restores the 4.6 behaviour of allowing probe of gpmc child
nodes to fail, and also fixes the problems with the Overo nand node.
Note that simply fixing the Overo NAND issue would fix the Overo
networking regression, but by restoring the 4.6 gpmc-probe behaviour
similar regressions on other OMAP systems are also avoided.
Johan
Johan Hovold (3):
memory: omap-gpmc: allow probe of child nodes to fail
ARM: dts: overo: fix gpmc nand cs0 range
ARM: dts: overo: fix gpmc nand on boards with ethernet
arch/arm/boot/dts/omap3-overo-base.dtsi | 4 +++-
.../arm/boot/dts/omap3-overo-chestnut43-common.dtsi | 2 --
arch/arm/boot/dts/omap3-overo-tobi-common.dtsi | 2 --
arch/arm/boot/dts/omap3-overo-tobiduo-common.dtsi | 3 ---
drivers/memory/omap-gpmc.c | 21 +++++++--------------
5 files changed, 10 insertions(+), 22 deletions(-)
--
2.7.3
next reply other threads:[~2016-07-24 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 12:10 Johan Hovold [this message]
2016-07-24 12:10 ` [PATCH 1/3] memory: omap-gpmc: allow probe of child nodes to fail Johan Hovold
2016-07-24 12:10 ` [PATCH 2/3] ARM: dts: overo: fix gpmc nand cs0 range Johan Hovold
2016-07-24 12:11 ` [PATCH 3/3] ARM: dts: overo: fix gpmc nand on boards with ethernet Johan Hovold
2016-08-02 10:35 ` [PATCH 0/3] ARM: omap: fix 4.7 gpmc networking regression Tony Lindgren
2016-08-03 7:46 ` Roger Quadros
2016-08-03 8:01 ` Johan Hovold
2016-08-03 9:55 ` Roger Quadros
2016-08-15 16:07 ` Tony Lindgren
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=1469362260-20066-1-git-send-email-johan@kernel.org \
--to=johan@kernel.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 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).