From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp02.smtpout.orange.fr ([80.12.242.124] helo=smtp.smtpout.orange.fr) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1ZVe3T-0001SG-SO for linux-mtd@lists.infradead.org; Sat, 29 Aug 2015 11:12:17 +0000 From: Robert Jarzmik To: Ezequiel Garcia Cc: Ezequiel Garcia , David Woodhouse , Brian Norris , "linux-mtd\@lists.infradead.org" , "linux-kernel\@vger.kernel.org" Subject: Re: [PATCH] mtd: nand: pxa3xx-nand: prevent DFI bus lockup on removal References: <1440356741-24308-1-git-send-email-robert.jarzmik@free.fr> <20150824150847.GA8497@laptop.cereza> <87io8435q4.fsf@belgarion.home> Date: Sat, 29 Aug 2015 13:07:28 +0200 In-Reply-To: (Ezequiel Garcia's message of "Fri, 28 Aug 2015 19:46:09 -0300") Message-ID: <87pp261hfz.fsf@belgarion.home> MIME-Version: 1.0 Content-Type: text/plain List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Ezequiel Garcia writes: > Robert, > > On 24 August 2015 at 15:24, Robert Jarzmik wrote: >> Ezequiel Garcia writes: >> >>> Should we worry about having two definitions for the same bit? >>> Would it be too ugly to mix the two meaning? Something like this: >>> >>> /* This bit has two different meanings on NFCv1 and NFCv2 */ >>> #define NDCR_STOP_ON_UNCOR_ARB_CNTL (0x1 << 19) >> I don't find that very pretty, but if you want I can put that in the patch >> instead. >> > > Yeah, it's far from pretty. > > OK, another idea. How about this: > > #define NFCV2_NDCR_STOP_ON_UNCOR (0x1 << 19) > #define NFCV1_NDCR_ARB_CNTL (0x1 << 19) This one looks much more prettier, I'll take it. > That'll work. Feel free to send a v2. Okay, I'm on my way. Cheers. -- Robert