From mboxrd@z Thu Jan 1 00:00:00 1970 From: cbostic@linux.vnet.ibm.com (Christopher Bostic) Date: Thu, 11 May 2017 11:14:13 -0500 Subject: [PATCH v6 19/23] drivers/fsi: Add GPIO based FSI master In-Reply-To: References: <20170410194706.64280-1-cbostic@linux.vnet.ibm.com> <20170410194706.64280-20-cbostic@linux.vnet.ibm.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 5/10/17 8:58 PM, Jeremy Kerr wrote: > Hi Chris, > >> I don't think we'd want this per master. The lock is for the 'top' >> master issuing commands. Only the top master can initiate any >> transactions on the bus to any devices connected downstream. Downstream >> masters such as hub masters, etc... cannot initiate a command. > I think what Joel meant there was that we have it per *GPIO* master; if > there are two GPIO masters on a system, there's no need to provide > mutual exclusion to each (separate) set of GPIOs. > > To implement this, we'd just move the lock into struct fsi_master_gpio. Hi Jeremy, Understand now -will make the change. Thanks -Chris > Cheers, > > > Jeremy >