From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3vDSF36T41zDqGH for ; Thu, 2 Feb 2017 15:48:39 +1100 (AEDT) Received: from pps.filterd (m0098416.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v124mZnu044575 for ; Wed, 1 Feb 2017 23:48:37 -0500 Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by mx0b-001b2d01.pphosted.com with ESMTP id 28bkgx4nfs-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Wed, 01 Feb 2017 23:48:36 -0500 Received: from localhost by e36.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 1 Feb 2017 21:48:36 -0700 Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Wed, 1 Feb 2017 21:48:33 -0700 Received: from b03cxnp07029.gho.boulder.ibm.com (b03cxnp07029.gho.boulder.ibm.com [9.17.130.16]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 48BF33E40041; Wed, 1 Feb 2017 21:48:33 -0700 (MST) Received: from b03ledav002.gho.boulder.ibm.com (b03ledav002.gho.boulder.ibm.com [9.17.130.233]) by b03cxnp07029.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v124mXm716122194; Wed, 1 Feb 2017 21:48:33 -0700 Received: from b03ledav002.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 28126136046; Wed, 1 Feb 2017 21:48:33 -0700 (MST) Received: from Venkateshs-MacBook-Pro.local (unknown [9.109.223.96]) by b03ledav002.gho.boulder.ibm.com (Postfix) with ESMTP id CA487136044; Wed, 1 Feb 2017 21:48:31 -0700 (MST) Subject: Re: Users of SBE FIFO kernel driver To: Joel Stanley , Christopher Bostic References: Cc: OpenBMC Maillist From: Venkatesh Sainath Date: Thu, 2 Feb 2017 10:18:30 +0530 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; 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-Content-Scanned: Fidelis XPS MAILER x-cbid: 17020204-0020-0000-0000-00000B414446 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00006540; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000201; SDB=6.00816006; UDB=6.00398436; IPR=6.00593443; BA=6.00005108; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00014147; XFM=3.00000011; UTC=2017-02-02 04:48:35 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17020204-0021-0000-0000-000059C15B85 Message-Id: <0a7745db-75d8-43b5-acf6-6f789964bdc0@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-02_03:, , 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-1612050000 definitions=main-1702020043 X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2017 04:48:40 -0000 I believe there are 2 drivers here. SBE FIFO driver and SBEI protocol driver. The SBEI protocol driver is the only user for the submit operation of SBE FIFO driver (as it requires the protocol knowledge to communicate with SBE). The SBEI protocol driver will be used by OCC and any user-space application that may want to perform a direct HW access over FSI ( for eg any scom operation). On 02/02/17 8:59 AM, Joel Stanley wrote: > Hi Chris, > > On Thu, Feb 2, 2017 at 5:58 AM, Christopher Bostic > wrote: >> I've not seen this discussed in the group but if this has already been >> determined than any pointers to the latest documentation would be >> appreciated. >> >> Who are all the potential users of the OpenBMC SBE FIFO device driver? I >> understand it will need to export its general submit interface to other >> kernel drivers. Only one I know of for sure would be the OCC driver Eddie >> James is working on. > In addition to Eddie's driver, in userspace we will have the code that > performs the power on sequence. > >> Any others? >> >> What about user space access of the SBE FIFO engine? What apps would >> require it? Cronus I assume will need some means to directly access it. > We want userspace API and an in-kernel API. > > The driver you design will need to take into account that there will > be multiple users from each of these APIs. For instance, there will be > Eddie's OCC hwmon driver and the userspace code that kicks off the > boot sequence. > > Cheers, > > Joel > _______________________________________________ > openbmc mailing list > openbmc@lists.ozlabs.org > https://lists.ozlabs.org/listinfo/openbmc