From nobody Mon Feb 9 13:37:03 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 D534C446BD; Fri, 12 Apr 2024 16:21:12 +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=1712938874; cv=none; b=mmsZT82RxCOOGgyuqXhJwStps6j4Xl7Ro92iXGcxTvbZ8Qa+hd1yU5fLO+B6M9WlJl5uOa5ihXSWiDKfIHg30mC8W/H20mggKnZdoAO7ZcWS15WK9cFIOGTTlRpKYHmnwrDVCvQmMMw+MsThKolLCTJvmmhROzexXWrGVgWV3NE= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712938874; c=relaxed/simple; bh=IigfVy1IYq5rcANH6+TO5CGSD+vRuzAC24jufyja+rA=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=bsAovmLObM8iZf0ZE0UXKmuFXPlbHL3dV0HMEsu/W6I7DufKvLM6cIDlpzpaW4yKql9Bm4AkDnkGki6juXS5xQa5tJ0gC87bFGJV2E5DvR7XZJtTPxuQq20MFYsTLBPZnDvcMfNBDftRKa/hi5dHRghE5M85uqD8iQdUCGs0oB4= 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 4VGMG441shz67Lmq; Sat, 13 Apr 2024 00:19:24 +0800 (CST) Received: from lhrpeml500005.china.huawei.com (unknown [7.191.163.240]) by mail.maildlp.com (Postfix) with ESMTPS id 726C3140119; Sat, 13 Apr 2024 00:21:10 +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:21:09 +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 20/30] perf/arm-dmc620: Assign parents for event_source device Date: Fri, 12 Apr 2024 17:10:47 +0100 Message-ID: <20240412161057.14099-21-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/ Signed-off-by: Jonathan Cameron --- drivers/perf/arm_dmc620_pmu.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/perf/arm_dmc620_pmu.c b/drivers/perf/arm_dmc620_pmu.c index 8a81be2dd5ec..2ec96e204c40 100644 --- a/drivers/perf/arm_dmc620_pmu.c +++ b/drivers/perf/arm_dmc620_pmu.c @@ -673,6 +673,7 @@ static int dmc620_pmu_device_probe(struct platform_devi= ce *pdev) =20 dmc620_pmu->pmu =3D (struct pmu) { .module =3D THIS_MODULE, + .parent =3D &pdev->dev, .capabilities =3D PERF_PMU_CAP_NO_EXCLUDE, .task_ctx_nr =3D perf_invalid_context, .event_init =3D dmc620_pmu_event_init, --=20 2.39.2