All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <paul@pwsan.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: linux-omap@vger.kernel.org,
	Enric Balletbo i Serra <eballetbo@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Grant Likely <grant.likely@secretlab.ca>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	khilman@linaro.org
Subject: OMAP5912 boot broken by "gpio/omap: don't create an IRQ mapping for every GPIO on DT"
Date: Mon, 29 Jul 2013 07:52:56 +0000 (UTC)	[thread overview]
Message-ID: <alpine.DEB.2.02.1307290604310.30864@utopia.booyaka.com> (raw)


Hi

your commit 0e970cec05635adbe7b686063e2548a8e4afb8f4 ("gpio/omap: don't 
create an IRQ mapping for every GPIO on DT") breaks the boot on the 
OMAP5912 OSK:

http://www.pwsan.com/omap/testlogs/bisect_5912osk_boot_fail_v3.11-rc3/20130729013931/boot/5912osk/5912osk_log.txt

This test included a stripped-down version of your commit 
949eb1a4d29dc75e0b5b16b03747886b52ecf854 ("gpio/omap: fix build error when 
OF_GPIO is not defined."), since 0e970cec also broke the build.

The previous commit ad81f0545ef01ea651886dddac4bef6cec930092 ("Linux 
3.11-rc1") boots cleanly:

http://www.pwsan.com/omap/testlogs/test_v3.11-rc1/20130721020309/boot/5912osk/5912osk_log.txt

OMAP5912 OSK is an OMAP1 platform, and therefore non-DT.

Could you please put together a fix for this?


regards,

- Paul

WARNING: multiple messages have this Message-ID (diff)
From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP5912 boot broken by "gpio/omap: don't create an IRQ mapping for every GPIO on DT"
Date: Mon, 29 Jul 2013 07:52:56 +0000 (UTC)	[thread overview]
Message-ID: <alpine.DEB.2.02.1307290604310.30864@utopia.booyaka.com> (raw)


Hi

your commit 0e970cec05635adbe7b686063e2548a8e4afb8f4 ("gpio/omap: don't 
create an IRQ mapping for every GPIO on DT") breaks the boot on the 
OMAP5912 OSK:

http://www.pwsan.com/omap/testlogs/bisect_5912osk_boot_fail_v3.11-rc3/20130729013931/boot/5912osk/5912osk_log.txt

This test included a stripped-down version of your commit 
949eb1a4d29dc75e0b5b16b03747886b52ecf854 ("gpio/omap: fix build error when 
OF_GPIO is not defined."), since 0e970cec also broke the build.

The previous commit ad81f0545ef01ea651886dddac4bef6cec930092 ("Linux 
3.11-rc1") boots cleanly:

http://www.pwsan.com/omap/testlogs/test_v3.11-rc1/20130721020309/boot/5912osk/5912osk_log.txt

OMAP5912 OSK is an OMAP1 platform, and therefore non-DT.

Could you please put together a fix for this?


regards,

- Paul

             reply	other threads:[~2013-07-29  7:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  7:52 Paul Walmsley [this message]
2013-07-29  7:52 ` OMAP5912 boot broken by "gpio/omap: don't create an IRQ mapping for every GPIO on DT" Paul Walmsley
2013-07-29  9:01 ` Linus Walleij
2013-07-29  9:01   ` Linus Walleij
2013-07-29  9:19   ` Paul Walmsley
2013-07-29  9:19     ` Paul Walmsley
2013-07-29  9:19   ` Javier Martinez Canillas
2013-07-29  9:19     ` Javier Martinez Canillas
2013-07-29  9:39     ` Javier Martinez Canillas
2013-07-29  9:39       ` Javier Martinez Canillas
2013-07-29 12:57       ` Santosh Shilimkar
2013-07-29 12:57         ` Santosh Shilimkar
2013-07-29 14:52         ` Alexander Holler
2013-07-29 14:52           ` Alexander Holler
2013-07-29 15:06           ` Santosh Shilimkar
2013-07-29 15:06             ` Santosh Shilimkar
2013-07-29 15:18             ` Alexander Holler
2013-07-29 15:18               ` Alexander Holler
2013-07-29 15:23               ` Santosh Shilimkar
2013-07-29 15:23                 ` Santosh Shilimkar
2013-07-29  9:47     ` Paul Walmsley
2013-07-29  9:47       ` Paul Walmsley
2013-07-29 10:19       ` Javier Martinez Canillas
2013-07-29 10:19         ` Javier Martinez Canillas
2013-07-29 11:43         ` Linus Walleij
2013-07-29 11:43           ` Linus Walleij
2013-07-29 12:40           ` Javier Martinez Canillas
2013-07-29 12:40             ` Javier Martinez Canillas
2013-07-29 15:26             ` Linus Walleij
2013-07-29 15:26               ` 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=alpine.DEB.2.02.1307290604310.30864@utopia.booyaka.com \
    --to=paul@pwsan.com \
    --cc=eballetbo@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=javier.martinez@collabora.co.uk \
    --cc=khilman@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=santosh.shilimkar@ti.com \
    /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.