Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752778AbbBXIUH (ORCPT ); Tue, 24 Feb 2015 03:20:07 -0500 Received: from down.free-electrons.com ([37.187.137.238]:37446 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752492AbbBXIUE (ORCPT ); Tue, 24 Feb 2015 03:20:04 -0500 Date: Tue, 24 Feb 2015 09:17:09 +0100 From: Maxime Ripard To: Brian Norris Cc: Ezequiel Garcia , Robert Jarzmik , Gregory Clement , Jason Cooper , Andrew Lunn , Sebastian Hesselbarth , Lior Amsalem , Tawfik Bayouk , Thomas Petazzoni , Seif Mazareeb , linux-kernel@vger.kernel.org, stable@vger.kernel.org, Sudhakar Gundubogula , Nadav Haklai , Boris Brezillon , linux-mtd@lists.infradead.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v3 1/2] mtd: nand: pxa3xx: Fix PIO FIFO draining Message-ID: <20150224081709.GM25269@lukather> References: <1424091072-7738-1-git-send-email-maxime.ripard@free-electrons.com> <1424091072-7738-2-git-send-email-maxime.ripard@free-electrons.com> <87oaotaa6r.fsf@free.fr> <20150216205825.GG25269@lukather> <87k2zha69p.fsf@free.fr> <20150217103740.GK25269@lukather> <877fvga2mb.fsf@free.fr> <54E3777B.20607@free-electrons.com> <20150224034548.GC18140@ld-irv-0074> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BXhH8iG0/4JcYZU2" Content-Disposition: inline In-Reply-To: <20150224034548.GC18140@ld-irv-0074> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2499 Lines: 68 --BXhH8iG0/4JcYZU2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Brian, On Mon, Feb 23, 2015 at 07:45:48PM -0800, Brian Norris wrote: > On Tue, Feb 17, 2015 at 02:16:43PM -0300, Ezequiel Garcia wrote: > > On 02/17/2015 02:07 PM, Robert Jarzmik wrote: > > > It will be Brian choice eventually, but if you say that you will subm= it that > > > approach for next cycle, and yours for stable, and that for next you'= ll convert > > > mdelay() to msleep(), I'll stop arguing. > >=20 > > How about you push a proper patchset with this alternative (and a nice > > cover letter explaining the need for a threaded irq) so we can discuss > > properly this new turn? >=20 > I think both Maxime's change (polling a new HW bit) and Robert J's > change (move to a threaded IRQ) are good. I'll take another look, but I > expect I'll take Maxime's v4 for the 4.0 cycle, and Robert J's v2 for > 4.1 (or will we just jump straight to 5.0? I never know). That's what I would expect too. > Will I see a patch to convert to msleep() and/or a jiffies timeout > in the near future? As soon as both patches are merged. Maxime --=20 Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com --BXhH8iG0/4JcYZU2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7DOFAAoJEBx+YmzsjxAgtm0P/00a7hosgRlJ8OfAo4jxdeDS NrAc1PGdIe55eaJQ0QNrrODLlpSNCp2eNLRTledmuGU46y2D6kIL4JC65vwUdUv7 Gma/Vc+fQHrx5QF60D4GwapNVAuluiAw07v5z+L3WuiekIf43ysKY8O/DS4VISSH PHF6lE7SDjvn4M8nL6EGLPauT2osc78PvuAa54IZR7ToZXJPLQ8J91xjYDyWV1XQ aDk+3F0TX2xPzFrxS32GdDhvPce3NPHhGZnFJ8viZbjE4vsB6SZU+YF5fXVZCSdD zlfzqvRABwI98rG0QEt8QLq3flFDkTRxCCIHdmNeXC/euufcw517x3l8+Tm0W4by lMtjBzWGVvs9vhzGuu1Ga86Eww9zQmtGgaz/BLxvkmy2MDon91V1RYKzvvGNZWXQ Hm1lzis6DW3hKQAypjeLaNXmGHDXZY0hkyj/bT0Va7HMF2zEUzWKl2YeZDk5w4J9 aq8crCZZ+6fn+hK1omkHomjGZ88rYruE+/y5XPghvuDYcc08Q2I99rMhuVO9e5la 2u3C8yhhP3LecOu8ke8ZT+XBIVVvbxpyzqxsqcmob1ojwIe2BAHllDETc/vYaqU9 j+SbB/HE6sRl5JIAcg7TNXz2NvwtTB+647wQnkbYb0ATQlkE9x7l8c2ne7HQ2h+r F9gphax5y8YGXblcAei5 =0fMb -----END PGP SIGNATURE----- --BXhH8iG0/4JcYZU2-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/