From: Tony Lindgren <tony@atomide.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-omap@vger.kernel.org, Balaji T K <balajitk@ti.com>
Subject: Re: [PATCH 1/3] omap4: Add i2c board support on omap4430 sdp platform
Date: Mon, 17 May 2010 19:59:17 -0700 [thread overview]
Message-ID: <20100518025917.GI5818@atomide.com> (raw)
In-Reply-To: <20100518025257.GG5818@atomide.com>
* Tony Lindgren <tony@atomide.com> [100517 19:47]:
> * Santosh Shilimkar <santosh.shilimkar@ti.com> [100512 01:22]:
> > This patch adds the i2c board support for OMAP4430 SDP platform. The
> > necessary drivers support patch is posted earlier.
> >
> > https://patchwork.kernel.org/patch/80659/
> >
> > --- a/arch/arm/plat-omap/i2c.c
> > +++ b/arch/arm/plat-omap/i2c.c
> > @@ -35,6 +35,7 @@
> > #define OMAP2_I2C_BASE1 0x48070000
> > #define OMAP2_I2C_BASE2 0x48072000
> > #define OMAP2_I2C_BASE3 0x48060000
> > +#define OMAP2_I2C_BASE4 0x48350000
> >
> > static const char name[] = "i2c_omap";
> >
> > @@ -54,9 +55,16 @@ static struct resource i2c_resources[][2] = {
> > #if defined(CONFIG_ARCH_OMAP2) || defined(CONFIG_ARCH_OMAP3)
> > { I2C_RESOURCE_BUILDER(OMAP2_I2C_BASE2, INT_24XX_I2C2_IRQ) },
> > #endif
> > +#if defined(CONFIG_ARCH_OMAP4)
> > + { I2C_RESOURCE_BUILDER(OMAP2_I2C_BASE2, OMAP44XX_IRQ_I2C2) },
> > +#endif
> > #if defined(CONFIG_ARCH_OMAP3)
> > { I2C_RESOURCE_BUILDER(OMAP2_I2C_BASE3, INT_34XX_I2C3_IRQ) },
> > #endif
> > +#if defined(CONFIG_ARCH_OMAP4)
> > + { I2C_RESOURCE_BUILDER(OMAP2_I2C_BASE3, OMAP44XX_IRQ_I2C3) },
> > + { I2C_RESOURCE_BUILDER(OMAP2_I2C_BASE4, OMAP44XX_IRQ_I2C4) },
> > +#endif
> > };
> >
> > #define I2C_DEV_BUILDER(bus_id, res, data) \
>
> The above breaks omap3_defconfig. You'll end up with all of the above
> in the array, and as the code is using the array index as the key,
> you end up with wrong resources.
>
> I've posted a fix for that in the MMC series and updated your
> patch accordingly.
In general, I won't be fixing or merging patches that break
omap3_defconfig BTW. So please everybody, make sure you test
with omap3_defconfig.
Regards,
Tony
next prev parent reply other threads:[~2010-05-18 2:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 8:27 [PATCH 0/3] omap4 i2c board support Santosh Shilimkar
2010-05-12 8:27 ` [PATCH 1/3] omap4: Add i2c board support on omap4430 sdp platform Santosh Shilimkar
2010-05-12 8:27 ` [PATCH 2/3] omap4: add i2c1 peripherals data Santosh Shilimkar
2010-05-12 8:27 ` [PATCH 3/3] omap4: Enable RTC and regulator support Santosh Shilimkar
2010-05-18 2:52 ` [PATCH 1/3] omap4: Add i2c board support on omap4430 sdp platform Tony Lindgren
2010-05-18 2:59 ` Tony Lindgren [this message]
2010-05-18 5:29 ` Shilimkar, Santosh
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=20100518025917.GI5818@atomide.com \
--to=tony@atomide.com \
--cc=balajitk@ti.com \
--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