From mboxrd@z Thu Jan 1 00:00:00 1970 From: Felipe Balbi Subject: Re: [PATCH 29/35] arm: omap: intc: switch over to linear irq domain Date: Fri, 1 Aug 2014 08:54:07 -0500 Message-ID: <20140801135407.GB9216@saruman.home> References: <20140729154057.GE17808@saruman.home> <20140729163345.GF17808@saruman.home> <20140730060420.GY29045@atomide.com> <20140730144059.GA7272@saruman.home> <20140730162038.GH7272@saruman.home> <20140731062843.GA29045@atomide.com> <53D9F6D5.1080307@ti.com> <20140731134945.GB19512@saruman.home> <53DB877A.5000004@ti.com> Reply-To: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CdrF4e02JqNVZeln" Return-path: Content-Disposition: inline In-Reply-To: <53DB877A.5000004@ti.com> Sender: linux-kernel-owner@vger.kernel.org To: Tero Kristo Cc: balbi@ti.com, Tony Lindgren , Nishanth Menon , dt list , Russell King - ARM Linux , jason@lakedaemon.net, Kevin Hilman , Linux Kernel Mailing List , Benoit Cousson , tglx@linutronix.de, Linux OMAP Mailing List , Linux ARM Kernel Mailing List List-Id: devicetree@vger.kernel.org --CdrF4e02JqNVZeln Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Fri, Aug 01, 2014 at 03:26:34PM +0300, Tero Kristo wrote: > >>>>>>I might have sent the wrong version as I had that same build error = and > >>>>>>fixed it localy. > >>>>>> > >>>>>>>it fixes the regression for me, Also now the whole series works for > >>>>>>>me :) > >>>>>> > >>>>>>good to know. > >>>>>> > >>>>>>What do you want to do now ? Wait for PRCM to become a driver ? Wai= t for > >>>>>>Nishanth's series to get accepted ? I guess the same thing could be= done > >>>>>>for OMAP3 and AM33, then we would have a chance of having working w= ake > >>>>>>from idle with the new irqchip. > >>>>> > >>>>>I can repost the current series as it stands now once 17-rc1 comes o= ut > >>>>>(without the build failure ofcourse).. if that helps to move it out = of > >>>>>RFC status. > >>>> > >>>>That'd be great. It would be ever greater if you could add support for > >>>>OMAP3 on that too. > >>> > >>>Yeah sounds good to me. Tero, does that work OK for your PRCM changes? > >> > >>Well, this set seems to break PM. suspend-resume on omap3-beagle just h= angs > >>after this set is applied. Works fine without it with 3.16-rc5 tag. > > > >did you apply the quick little hack to prm3xxx.c ? prcm IRQ is hardcoded > >to 11, once we switch to a linear irq domain, irq_base may change. >=20 > Yea, with that hack it works. However, you should make that into a proper > patch and add it to this series, otherwise you will be causing regression= s. can you please read the thread ? Nishanth has a proper series properly doing that for OMAP4, I asking him to add OMAP3 and respin his series without RFC. --=20 balbi --CdrF4e02JqNVZeln Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJT25v/AAoJEIaOsuA1yqREiS0P/AoGDhuqicj/49uoLHq9d3L7 88m2hoTIGMD5TM7xuYWCYK23YNnE/j8/gcDAGyctc73lbytzVU0Y12ZK7XOUji2u iz8GhMz2Q7fxjBCJYB56CbiZYCqA4mycezXgHNShuVXDQQJb/sqjLuoIih1Cdd2E nsoA2axA/IjbSPbH/VYEKroXIX7vvInZlH0oQVEegM1F/XRNcHoUq8ColWqkw9Hi 7s6LgX3Zxv7zFJEOywElR659XZ9lbBMZeewGQoOOk3NcjTqWhXT8st/I/Mc1y8cq Vusaoj7av0DImJJTqGf8mRn92zR95RpIVUWT/Z/mEuyEC2zgjHV6XKxqpA77HWi0 Tp5IsXA8ihkIfgco3PG5JPBrgUQ9muhT8tixGuXFur5OSK5ITVqJyOaj2Ixu1Iyp yYsvtPBzhqY4dHTcMHR2u3TB9zcrxZLKL24rOyvj7RHxTXli9srFN96l6wMz4dx2 mozYkhimVqZjdOdRXvzD3gq0Efd/q56Y8U9EtQBhzNhq7llqNtoZyrpxJHW4co7t 4Gxns5BLCx2C0ixDftKSnsZiFGO0VEvJ62fscEeGnSgBf2AucFBIkPcOdCrh2PSh Mh+3E7HD/btyfoMT7DcKPIJ4WMaDJsSpf8xLuPKLordwaPpoh3ZSiMio46Gp0jMV LKOANSX5dyXjmVMpuAR1 =Mbkb -----END PGP SIGNATURE----- --CdrF4e02JqNVZeln--