From nobody Mon Feb 9 19:26:53 2026 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A8C751494D9; Fri, 12 Apr 2024 16:24:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.176.79.56 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712939089; cv=none; b=rGvoKW9fbjhqIQZJDS+ntuS5B4NmfliiM3VtrQUAwyZxWvitsxqdke6P8maTk+ugBKOJpXwLb8aewemjkgGKWwRNVzsSL9nxXIsi1LzaziIqoOkp+zkMsN/XPrXA7PGN1INjz1r7QRSAcLnZsym4hdGRvGjYLMX5vRM621P6Nv8= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712939089; c=relaxed/simple; bh=knChXPbAby4vPyCTbD9SHOU5rvr1w2NKjGFBpG0ctng=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=tt9yR656R6weVgiK9qB9fdDeE/ChQdpiCD/yUrOLnIr5+veiYbLzzxyKXpsy8nL0Jbias9c4B0HrGdpgAKwtDkvs3kS+R2+yxu2G/8Ijsq/46JpzXaSNHlQJ5F18jBqJPE5znLejBvgc0k1fUQX2t06rgwj3E8+MH6EYPjVcMP8= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=185.176.79.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4VGMGf75Pfz688p7; Sat, 13 Apr 2024 00:19:54 +0800 (CST) Received: from lhrpeml500005.china.huawei.com (unknown [7.191.163.240]) by mail.maildlp.com (Postfix) with ESMTPS id 71EAD140119; Sat, 13 Apr 2024 00:24:45 +0800 (CST) Received: from SecurePC-101-06.china.huawei.com (10.122.247.231) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Fri, 12 Apr 2024 17:24:44 +0100 From: Jonathan Cameron To: Mark Rutland , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Will Deacon , , , CC: , Shaokun Zhang , Yicong Yang , Jiucheng Xu , Khuong Dinh , Atish Patra , Anup Patel , Andy Gross , Bjorn Andersson , Frank Li , Shuai Xue , Vineet Gupta , Shawn Guo , Fenghua Yu , Dave Jiang , Wu Hao , Tom Rix , , Suzuki K Poulose , Liang Kan Subject: [PATCH v2 27/30] fpga: dfl: Assign parent for event_source device Date: Fri, 12 Apr 2024 17:10:54 +0100 Message-ID: <20240412161057.14099-28-Jonathan.Cameron@huawei.com> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20240412161057.14099-1-Jonathan.Cameron@huawei.com> References: <20240412161057.14099-1-Jonathan.Cameron@huawei.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: lhrpeml100003.china.huawei.com (7.191.160.210) To lhrpeml500005.china.huawei.com (7.191.163.240) Content-Type: text/plain; charset="utf-8" Currently the PMU device appears directly under /sys/devices/ Only root busses should appear there, so instead assign the pmu->dev parent to be the Platform device. Link: https://lore.kernel.org/linux-cxl/ZCLI9A40PJsyqAmq@kroah.com/ Cc: linux-fpga@vger.kernel.org Reviewed-by: Xu Yilun Signed-off-by: Jonathan Cameron --- drivers/fpga/dfl-fme-perf.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/fpga/dfl-fme-perf.c b/drivers/fpga/dfl-fme-perf.c index 7422d2bc6f37..2d59f1c620b1 100644 --- a/drivers/fpga/dfl-fme-perf.c +++ b/drivers/fpga/dfl-fme-perf.c @@ -912,6 +912,7 @@ static int fme_perf_pmu_register(struct platform_device= *pdev, =20 fme_perf_setup_hardware(priv); =20 + pmu->parent =3D &pdev->dev; pmu->task_ctx_nr =3D perf_invalid_context; pmu->attr_groups =3D fme_perf_groups; pmu->attr_update =3D fme_perf_events_groups; --=20 2.39.2