From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] drivers: bus: Move the OMAP interconnect driver to drivers/bus/
Date: Wed, 19 Sep 2012 12:11:00 -0700 [thread overview]
Message-ID: <20120919191059.GH11762@atomide.com> (raw)
In-Reply-To: <201209191857.57862.arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> [120919 11:59]:
> On Monday 17 September 2012, Tony Lindgren wrote:
> > * Santosh Shilimkar <santosh.shilimkar@ti.com> [120914 02:21]:
> > > OMAP interconnect drivers are used for the interconnect error handling.
> > > Since they are bus driver, lets move it to newly created drivers/bus.
> > >
> > > Cc: Arnd Bergmann <arnd@arndb.de>
> > > Cc: Tony Lindgren <tony@atomide.com>
> > > Tested-by: Lokesh Vutla <lokeshvutla@ti.com>
> > > Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> > > ---
> > > Patch just moves OMAP interconnect drivers as is to the newly created
> > > driver/bus/* directory. Patch is generated against "arm-soc/drivers/ocp2scp"
> > > tree and test on all OMAP boards.
> >
> > Great, looks like this should not conflict with other
> > omap patches queued, so Arnd should probably take this into
> > the bus branch:
> >
> > Acked-by: Tony Lindgren <tony@atomide.com>
>
> It turns out that the patch actually did conflict and we now have a broken
> omap2plus_defconfig. The patch below seems to fix it, but please verify
> that this makes sense.
Heh a conflict caused by hard coded irqs for the error message :)
Looks like a good fix that removes some unncecessary dependencies:
Acked-by: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> diff --git a/drivers/bus/omap_l3_noc.c b/drivers/bus/omap_l3_noc.c
> index f447e02..ab911a3 100644
> --- a/drivers/bus/omap_l3_noc.c
> +++ b/drivers/bus/omap_l3_noc.c
> @@ -28,7 +28,6 @@
> #include <linux/kernel.h>
> #include <linux/slab.h>
>
> -#include "soc.h"
> #include "omap_l3_noc.h"
>
> /*
> @@ -191,7 +190,7 @@ static int __devinit omap4_l3_probe(struct platform_device *pdev)
> IRQF_DISABLED, "l3-dbg-irq", l3);
> if (ret) {
> pr_crit("L3: request_irq failed to register for 0x%x\n",
> - 9 + OMAP44XX_IRQ_GIC_START);
> + l3->debug_irq);
> goto err3;
> }
>
> @@ -201,7 +200,7 @@ static int __devinit omap4_l3_probe(struct platform_device *pdev)
> IRQF_DISABLED, "l3-app-irq", l3);
> if (ret) {
> pr_crit("L3: request_irq failed to register for 0x%x\n",
> - 10 + OMAP44XX_IRQ_GIC_START);
> + l3->app_irq);
> goto err4;
> }
>
next prev parent reply other threads:[~2012-09-19 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 9:20 [PATCH 1/1] drivers: bus: Move the OMAP interconnect driver to drivers/bus/ Santosh Shilimkar
2012-09-17 21:51 ` Tony Lindgren
2012-09-19 14:58 ` Arnd Bergmann
2012-09-19 15:10 ` Olof Johansson
2012-09-19 16:21 ` Shilimkar, Santosh
2012-09-19 18:57 ` Arnd Bergmann
2012-09-19 19:11 ` Tony Lindgren [this message]
2012-09-20 5:56 ` Shilimkar, Santosh
2012-09-20 23:22 ` Olof Johansson
2012-09-20 23:54 ` 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=20120919191059.GH11762@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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 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).