From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Hunter Subject: Re: [PATCH v5 10/14] ARM: OMAP2+: gpmc: waitpin helper Date: Wed, 13 Jun 2012 10:44:30 -0500 Message-ID: <4FD8B55E.6010701@ti.com> References: <4FD6783D.9030208@ti.com> <4FD78748.2080504@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from comal.ext.ti.com ([198.47.26.152]:59859 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754439Ab2FMPoa (ORCPT ); Wed, 13 Jun 2012 11:44:30 -0400 In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Mohammed, Afzal" Cc: "tony@atomide.com" , "paul@pwsan.com" , "linux-omap@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Hi Afzal, On 06/13/2012 02:37 AM, Mohammed, Afzal wrote: > Hi Jon, > > On Tue, Jun 12, 2012 at 23:45:36, Hunter, Jon wrote: > >> GPMC_WAITPIN_IDX0 = 0 >> GPMC_WAITPIN_0 = 1 >> >> So, GPMC_WAITPIN_IDX0 = GPMC_WAITPIN_0 - 1, assuming that you want idx = >> 0 and not 1. Or you could change you shift value too. I was just >> highlighting that they are not equal but one set of definitions could be >> used. > > In that case we would be directly depending on user flag whose value may > or may not change and I don't think it is good to directly depend on it > for waitpin # calculation. You are already dependent on it. In other words, you are going to set the waitpin # according to these flags in the first place. I don't see the difference. Bottom line is that we don't need to have multiple definitions for the same thing. Jon