From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6E89BC4727E for ; Thu, 1 Oct 2020 08:38:23 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 0DA3820780 for ; Thu, 1 Oct 2020 08:38:23 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="HuiJKqPr" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0DA3820780 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Type: Content-Transfer-Encoding:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date:Message-ID:References: To:Subject:From:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=1THXWPj4n0gO/H1QiRzrzEOcOkP30iwu+EMeBU5xW0Q=; b=HuiJKqPrDbIeRaP90rNwV7F8k 3fx6d3hkiGstSUUEd4NMgZztO/j5nPqgERZ+tEyseHojhE+1CNA8Gi2wPvxjNA77kHagExPJNLgHR poWygIJ8YT9v67gD9B+iGXTGX/gOqFxzDaNKmCuLEMNmVxJKvVK2nD1ufQdQ9/qVIkeNM4kZ9P5cR 3IrBk6E7oRDAyTifEMZCoQALpz1o85WdFtW7hVDNIiuGEImQQILGH66cG4J+xFPcxQCi30GdZ647y Id6t6N3St40qT2Y+Efs2ECZ5XjRNykXoNiL5w2K3wCAUTKyoxkDu4H5I7np1VKb3Rm7BnIoQmZ5i6 SuN2DCjFw==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kNu5M-0003s8-7C; Thu, 01 Oct 2020 08:37:08 +0000 Received: from lhrrgout.huawei.com ([185.176.76.210] helo=huawei.com) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kNu5J-0003qc-Mm for linux-arm-kernel@lists.infradead.org; Thu, 01 Oct 2020 08:37:06 +0000 Received: from lhreml724-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id D5057208E5AF44931A9A; Thu, 1 Oct 2020 09:37:00 +0100 (IST) Received: from [127.0.0.1] (10.210.167.80) by lhreml724-chm.china.huawei.com (10.201.108.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 1 Oct 2020 09:37:00 +0100 From: John Garry Subject: Re: [PATCH] drivers/perf: hisi: Add identifier sysfs file To: Will Deacon References: <1592399111-134786-1-git-send-email-john.garry@huawei.com> <20200714083216.GD4516@willie-the-truck> <67db3c30-5aaf-ac17-0256-950494f5ba88@huawei.com> <20200715083016.GB5683@willie-the-truck> Message-ID: Date: Thu, 1 Oct 2020 09:34:02 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.1.2 MIME-Version: 1.0 In-Reply-To: <20200715083016.GB5683@willie-the-truck> Content-Language: en-US X-Originating-IP: [10.210.167.80] X-ClientProxiedBy: lhreml736-chm.china.huawei.com (10.201.108.87) To lhreml724-chm.china.huawei.com (10.201.108.75) X-CFilter-Loop: Reflected X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201001_043705_849281_32BB7E7C X-CRM114-Status: GOOD ( 15.80 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: mark.rutland@arm.com, Robin Murphy , linuxarm@huawei.com, linux-kernel@vger.kernel.org, qiangqing.zhang@nxp.com, zhangshaokun@hisilicon.com, jolsa@redhat.com, linux-arm-kernel@lists.infradead.org Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 15/07/2020 09:30, Will Deacon wrote: > Hi John, > > On Wed, Jul 15, 2020 at 09:23:19AM +0100, John Garry wrote: >>> On Wed, Jun 17, 2020 at 09:05:11PM +0800, John Garry wrote: >>>> To allow userspace to identify the specific implementation of the device, >>>> add an "identifier" sysfs file. >>>> >>>> Encoding is as follows: >>>> hi1620: 0x0 (aka hip08) >>>> hi1630: 0x30 >>>> >>>> Signed-off-by: John Garry >>> >>> I'm struggling a bit to track this. If you still think it's worth pursuing, >>> please could you post a series with a cover-letter describing what this is >>> for, a link to the userspace changes and then patches for all the PMU >>> drivers that need updating? >> >> There is no hi1630 userspace support yet. >> >> So what I can do is post updated userspace support (including hi1630), and >> then post kernel parts together for all drivers we could initially support. >> >> @Joakim, I'll pick your imx driver changes here, if you don't mind. >> >> There was an RFC from you for the SMMUv3 PMU as >>> well, and also some other "arm64" changes. >>> >> >> I hope to drop that RFC if an updated SMMUv3 spec helps us out. > Released SMMUv3.3 spec provides a PMCG_IIDR reg, which we can now use to identify the implementation: https://developer.arm.com/documentation/ihi0070/da/?lang=en So I'll look to put the userspace and kernel parts together for this now for review. Thanks, John _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel