[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF04A0687289@HQMAIL01.nvidia.com>
Date: Tue, 9 Aug 2011 09:21:31 -0700
From: Stephen Warren <swarren@...dia.com>
To: Ben Dooks <ben-i2c@...ff.org>
CC: "devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jean Delvare <khali@...ux-fr.org>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
Colin Cross <ccross@...roid.com>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
Axel Lin <axel.lin@...il.com>,
Rob Herring <robherring2@...il.com>,
Grant Likely <grant.likely@...retlab.ca>,
"marc.zyngier@....com" <marc.zyngier@....com>
Subject: Tegra I2C driver compilation failure (was: RE: [PATCH] dt: add
empty of_get_property for non-dt)
Stephen Warren wrote at Monday, August 08, 2011 1:26 PM:
> Rob Herring wrote at Sunday, August 07, 2011 8:38 AM:
> > On 08/05/2011 05:50 PM, Stephen Warren wrote:
> > > The patch adds empty function of_get_property for non-dt build, so that
> > > drivers migrating to dt can save some '#ifdef CONFIG_OF'.
> > >
> > > This also fixes the current Tegra compile problem in linux-next.
> >
> > You could just use of_property_read_u32 in the driver. It already has
> > empty version and will simplify the driver code some.
>
> Yes, that would also work.
>
> Grant, Ben, do you have a preference for which option to choose?
Well, all three possible fixes have been posted now:
Add ifdef to i2c driver:
http://www.spinics.net/lists/linux-tegra/msg01720.html
Implement empty of_get_property:
http://www.spinics.net/lists/linux-tegra/msg01881.html
Switch i2c driver to use of_property_read_u32:
http://permalink.gmane.org/gmane.linux.ports.arm.kernel/127807
Ben, please could you please pick one of the changes and apply it, so
that linux-next compiles for Tegra? Thanks!
--
nvpublic
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists