From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751668AbdJBDOX (ORCPT ); Sun, 1 Oct 2017 23:14:23 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:54674 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750943AbdJBDOW (ORCPT ); Sun, 1 Oct 2017 23:14:22 -0400 From: Stewart Smith To: Shilpasri G Bhat , mpe@ellerman.id.au Cc: ego@linux.vnet.ibm.com, linux-kernel@vger.kernel.org, paulus@samba.org, Shilpasri G Bhat , linuxppc-dev@lists.ozlabs.org, akshay.adiga@linux.vnet.ibm.com Subject: Re: [PATCH] powernv: Add OCC driver to mmap sensor area In-Reply-To: <1506667651-32301-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com> References: <1506667651-32301-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com> Date: Mon, 02 Oct 2017 14:14:10 +1100 MIME-Version: 1.0 Content-Type: text/plain X-TM-AS-GCONF: 00 x-cbid: 17100203-0052-0000-0000-0000026AD79C X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00007826; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000233; SDB=6.00925262; UDB=6.00465307; IPR=6.00705422; BA=6.00005615; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00017355; XFM=3.00000015; UTC=2017-10-02 03:14:19 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17100203-0053-0000-0000-0000522F9B69 Message-Id: <87bmlqutq5.fsf@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-10-02_01:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=1 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710020046 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Shilpasri G Bhat writes: > This driver provides interface to mmap the OCC sensor area > to userspace to parse and read OCC inband sensors. Why? Is this for debug? If so, the existing exports interface should be used. If there's actual sensors, we already have two ways of exposing sensors to Linux: the OPAL_SENSOR API and the IMC API. Why this method and not use the existing ones? -- Stewart Smith OPAL Architect, IBM.