From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] ARM: OMAP: boards: changes to support dynamic irq alloc
Date: Mon, 19 Mar 2012 16:39:11 -0700 [thread overview]
Message-ID: <20120319233910.GF9859@atomide.com> (raw)
In-Reply-To: <4F67B9F9.1030906@ti.com>
* Cousson, Benoit <b-cousson@ti.com> [120319 16:00]:
> Hi Tony,
>
> On 3/19/2012 8:17 PM, Tony Lindgren wrote:
> >* Tarun Kanti DebBarma<tarun.kanti@ti.com> [120319 05:09]:
> >>These two patches incorporate changes to OMAP1 and OMAP2 platforms
> >>board files whereby older references to OMAP_GPIO_IRQ macro are
> >>now replaced with gpio_to_irq(), thereby getting rid of static
> >>irq references.
> >>
> >>Reference: git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git omap/dt
> >>Commit: 9a0cee711448335ec43eae83272495e9334c0098
> >
> >Can you please tell the exact two commits causing this
> >breakage?
>
> Well, this is the GPIO DT + SPARSE_IRQ series I have done. It
> appears that the boards I have were already using properly
> gpio_to_irq() and thus were working fine with this series.
>
> But this is unfortunately not the case of most OMAP2 and 3 legacy
> boards that were still using an old OMAP way of converting GPIO to
> IRQ and were never modified to take advantage of the gpiolib stuff.
>
> So if these patches are apply before the GPIO DT + SPARSE_IRQ
> series, there will be no breakage at all.
>
> All the cleanup we have never done before will hurt us at some point
> when we will start using more extensively newer fmwk (DT,
> sparse_irq, dmaengine...). It was not done on purpose, but this GPIO
> series highlighted this remaining static broken mapping inside OMAP
> boards.
Yes I understand. But still, which patch(s) cause the issue
so we can put that in the changelog for the fixes?
> >I'm baffled how despite all the effort for previnting
> >issues like this this still happen. These all seem valid
> >fixes and clean up things, but how come this was not seen
> >earlier?
>
> Maybe because there are much more boards inside mach-omap2 directory
> than inside my cubicle... :-(
Well somehow we need to make sure that patches get properly
tested on a reasonable selection of boards. This pretty much
breaks things for 21 boards out of the 51 board-*.c files :(
Regards,
Tony
next prev parent reply other threads:[~2012-03-19 23:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 12:06 [PATCH v2 0/4] ARM: OMAP: boards: changes to support dynamic irq alloc Tarun Kanti DebBarma
2012-03-19 12:06 ` [PATCH v2 1/4] ARM: OMAP1: boards: Fix OMAP_GPIO_IRQ usage with gpio_to_irq() Tarun Kanti DebBarma
2012-03-29 4:58 ` Olof Johansson
2012-03-29 5:34 ` DebBarma, Tarun Kanti
2012-03-19 12:06 ` [PATCH v2 2/4] ARM: OMAP2+: " Tarun Kanti DebBarma
2012-03-19 12:06 ` [PATCH v2 3/4] drivers: input: Fix OMAP_GPIO_IRQ with gpio_to_irq() in ams_delta_serio_exit() Tarun Kanti DebBarma
2012-03-20 16:52 ` Tony Lindgren
2012-03-20 17:36 ` Dmitry Torokhov
2012-03-19 12:06 ` [PATCH v2 4/4] ARM: OMAP: Remove OMAP_GPIO_IRQ macro definition Tarun Kanti DebBarma
2012-03-19 12:17 ` [PATCH v2 0/4] ARM: OMAP: boards: changes to support dynamic irq alloc Shilimkar, Santosh
2012-03-19 12:30 ` DebBarma, Tarun Kanti
2012-03-19 19:17 ` Tony Lindgren
2012-03-19 22:58 ` Cousson, Benoit
2012-03-19 23:39 ` Tony Lindgren [this message]
2012-03-20 9:00 ` Cousson, Benoit
2012-03-20 10:59 ` DebBarma, Tarun Kanti
2012-03-20 16:51 ` 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=20120319233910.GF9859@atomide.com \
--to=tony@atomide.com \
--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).