From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757714AbdEKQO0 (ORCPT ); Thu, 11 May 2017 12:14:26 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:47039 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757335AbdEKQOW (ORCPT ); Thu, 11 May 2017 12:14:22 -0400 Subject: Re: [PATCH v6 19/23] drivers/fsi: Add GPIO based FSI master To: Jeremy Kerr , Joel Stanley References: <20170410194706.64280-1-cbostic@linux.vnet.ibm.com> <20170410194706.64280-20-cbostic@linux.vnet.ibm.com> Cc: Rob Herring , Mark Rutland , Russell King , rostedt@goodmis.org, mingo@redhat.com, Greg KH , devicetree , linux-arm-kernel@lists.infradead.org, Linux Kernel Mailing List , Andrew Jeffery , Alistair Popple , Benjamin Herrenschmidt , "Edward A . James" From: Christopher Bostic Date: Thu, 11 May 2017 11:14:13 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 17051116-0016-0000-0000-000006B8B5AF X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00007047; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000211; SDB=6.00859202; UDB=6.00425810; IPR=6.00638677; BA=6.00005345; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00015413; XFM=3.00000015; UTC=2017-05-11 16:14:19 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17051116-0017-0000-0000-000039990F11 Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-05-11_12:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705110085 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.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 >