From patchwork Fri Dec 9 19:38:11 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Lizhi Hou X-Patchwork-Id: 13070103 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E73A3C4332F for ; Fri, 9 Dec 2022 19:38:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229835AbiLITiu (ORCPT ); Fri, 9 Dec 2022 14:38:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34046 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229813AbiLITir (ORCPT ); Fri, 9 Dec 2022 14:38:47 -0500 Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on2068.outbound.protection.outlook.com [40.107.96.68]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6CA4DA19BF; Fri, 9 Dec 2022 11:38:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PAVYAJXrwHzgR8z3CXieQ8mkQK14ay1M0xwY0nOtfb+mvH+CiJQD5BV3dFkBuoRKD9/vcxaz7Dc577w4OiQjMUvOashLSfRX8DdclpBDVRMIwudxGY1p3BH6hqSwKmXRWqGLspGbg0t8/Guxv+XAhIc3zZ3NbGmxU0+Lgmph2WTw7MmR516VeW7gRoGZGwrO7JFWN02TSSoLbBPLhYoLx07V3va/c4KuHjytCe1F2lnS+E7z0BJK6YfPGwtVRYpjIXZMMYyaIumNqYl1SYn+zwSXjX0YDqC8VVDoasXo+zmyq300E34xoqOxdmq04hIWPrgvQyK9HmtLYbLeahSaQg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=WjgYwgkf+xg/Uvk6V45vb6yqrGleoFNZLlEw/luaQKw=; b=n2WUQdryYch2/BaxfLYdgACTkPiu6w1jQElAopzHJ6oBxQaHOstzFs0ZnCkKkRp0q0a255ENqUCLRzQr9q+UxQalE8IF0u1RRULPejdBbmXwFnTi82PaZ/HbqXAPruwfr/8b6x1YI7y7/qdhGlrMegSXCXWwjSXR6Xc6xQcowW8yTGfcaIR9PB2aIXSStUJ9ulNcTddMiF4+RHF1+1p8aLLGCFgV32q8A8vOKxeAxp2b48mGbo+yWVTeOiiYDjlwv7Vlf7a54XLxal/pPbwYrpRevln81ksqooSZfFD8HT6TprPeika7O7rCYNCJA3yuFySS0KzY7VV+kqJx5MqvzQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=vger.kernel.org smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amd.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WjgYwgkf+xg/Uvk6V45vb6yqrGleoFNZLlEw/luaQKw=; b=Xhr2B9fQsMsQZL/xl2ypjVM5jnjbfYRcJiTCjMwJ1WobiX3ccPiGpwFJuxAwgyaQgBs/pLxCTSd2yy69YgLXEL2hANYCm/k3ZoGFt265P19QsgyuluhhrKAvf1AV1XnteH7ZpnUyIIuhcP3fiPgJWSEdlULlfq24WIdh0hj0nSc= Received: from BN9PR03CA0444.namprd03.prod.outlook.com (2603:10b6:408:113::29) by BL1PR12MB5828.namprd12.prod.outlook.com (2603:10b6:208:397::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5880.16; Fri, 9 Dec 2022 19:38:44 +0000 Received: from BL02EPF0000EE3E.namprd05.prod.outlook.com (2603:10b6:408:113:cafe::c0) by BN9PR03CA0444.outlook.office365.com (2603:10b6:408:113::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5880.18 via Frontend Transport; Fri, 9 Dec 2022 19:38:44 +0000 X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 165.204.84.17) smtp.mailfrom=amd.com; dkim=none (message not signed) header.d=none;dmarc=pass action=none header.from=amd.com; Received-SPF: Pass (protection.outlook.com: domain of amd.com designates 165.204.84.17 as permitted sender) receiver=protection.outlook.com; client-ip=165.204.84.17; helo=SATLEXMB04.amd.com; pr=C Received: from SATLEXMB04.amd.com (165.204.84.17) by BL02EPF0000EE3E.mail.protection.outlook.com (10.167.241.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.5880.8 via Frontend Transport; Fri, 9 Dec 2022 19:38:42 +0000 Received: from SATLEXMB05.amd.com (10.181.40.146) by SATLEXMB04.amd.com (10.181.40.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.34; Fri, 9 Dec 2022 13:38:42 -0600 Received: from SATLEXMB04.amd.com (10.181.40.145) by SATLEXMB05.amd.com (10.181.40.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.34; Fri, 9 Dec 2022 13:38:42 -0600 Received: from xsjlizhih40.xilinx.com (10.180.168.240) by SATLEXMB04.amd.com (10.181.40.145) with Microsoft SMTP Server id 15.1.2375.34 via Frontend Transport; Fri, 9 Dec 2022 13:38:41 -0600 From: Lizhi Hou To: , , , , , CC: Lizhi Hou , , , , , , , Subject: [PATCH V5 0/3] Generate device tree node for pci devices Date: Fri, 9 Dec 2022 11:38:11 -0800 Message-ID: <1670614694-68049-1-git-send-email-lizhi.hou@amd.com> X-Mailer: git-send-email 1.8.3.1 MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-MS-PublicTrafficType: Email X-MS-TrafficTypeDiagnostic: BL02EPF0000EE3E:EE_|BL1PR12MB5828:EE_ X-MS-Office365-Filtering-Correlation-Id: 43dc24e7-48da-40c1-f7cc-08dada1cfae8 X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: jjx1D8ziBkz0jf1rJFrtJbvTFrXrZMgkeSIRSB57P5ySaSSZ6k6fGKsqKJrQHpbEFhjT5HYOAOrce/4tJESkM0/M6Ey/U39hEB0lW9nw3Ub/UQHO5U6DCYS4sgzjx0+vKD6ZR4V0tRh801wAcP0bc8gM0LC4Bj+b31RQzPpwlTt/wB3mF934rIzIZAInC8AKb2TtWw7USlOVK3x+jzN6KkwQDuQcwY/Tp+UbvAoxXyAg/hfIH4j8BKTpxgPBbeumFoONJYiXMBaeXMDOclERDdhCYUJ6nB/cz/m+24xTBfh79aHzF9GwzVD+uuTV0+i2KhG4isZbQTmxuCINvqPFeMlrP3laN1qC8wWu2fzzf4eMqSdIzHcyLGTZolt2enX/RnFWV8A2D1QBanK3dAOfKK2zxvmkgcJ4aWVRcIXXzusCIv1DhW2NdCsj9gSrTNNtPotIcFBazg6OJp8soBIHg8+J+hkqp9Dpof9KRzOmxF0RxRi7AbTkcWSnGLycaMH3S7rWOXbU4V9DRfonCarDIDnAaBoToHQ3SAJg+MRX1zS/Oj9ivMAgDBChkecdmSqGCozBvTujLSrb1NrDy1TZ0cm92XO9U+9fDBen8DVU4GVQWARGJd5AWNrKgksyJut44xCFSXbBCRehiIsHuDoyfo+K6qj9UThXN9dnQofi4TZyAlMhLglyaF/6PNPAcJAB3ixCKUOvO4vfpwgJbUBdkH7gsxxELHIsQxt3C2bAcvWRel+d+GnBdOh/6V7zl1GT88vFpZNScUwlsGA7AtExr0yrXMyyTkTMDDPshac5o/xHhY2aBsHtuJ6LTf0ZSo5e X-Forefront-Antispam-Report: CIP:165.204.84.17;CTRY:US;LANG:en;SCL:1;SRV:;IPV:CAL;SFV:NSPM;H:SATLEXMB04.amd.com;PTR:InfoDomainNonexistent;CAT:NONE;SFS:(13230022)(4636009)(396003)(346002)(136003)(376002)(39860400002)(451199015)(36840700001)(46966006)(40470700004)(44832011)(40460700003)(54906003)(36756003)(2906002)(86362001)(40480700001)(2616005)(83380400001)(336012)(26005)(47076005)(426003)(6666004)(110136005)(966005)(82740400003)(186003)(82310400005)(478600001)(41300700001)(70206006)(356005)(8936002)(5660300002)(8676002)(4326008)(70586007)(316002)(81166007)(36860700001)(36900700001);DIR:OUT;SFP:1101; X-OriginatorOrg: amd.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Dec 2022 19:38:42.9545 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 43dc24e7-48da-40c1-f7cc-08dada1cfae8 X-MS-Exchange-CrossTenant-Id: 3dd8961f-e488-4e60-8e11-a82d994e183d X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3dd8961f-e488-4e60-8e11-a82d994e183d;Ip=[165.204.84.17];Helo=[SATLEXMB04.amd.com] X-MS-Exchange-CrossTenant-AuthSource: BL02EPF0000EE3E.namprd05.prod.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL1PR12MB5828 Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org This patch series introduces OF overlay support for PCI devices which primarily addresses two use cases. First, it provides a data driven method to describe hardware peripherals that are present in a PCI endpoint and hence can be accessed by the PCI host. Second, it allows reuse of a OF compatible driver -- often used in SoC platforms -- in a PCI host based system. There are 2 series devices rely on this patch: 1) Xilinx Alveo Accelerator cards (FPGA based device) 2) Microchip LAN9662 Ethernet Controller Please see: https://lore.kernel.org/lkml/20220427094502.456111-1-clement.leger@bootlin.com/ Normally, the PCI core discovers PCI devices and their BARs using the PCI enumeration process. However, the process does not provide a way to discover the hardware peripherals that are present in a PCI device, and which can be accessed through the PCI BARs. Also, the enumeration process does not provide a way to associate MSI-X vectors of a PCI device with the hardware peripherals that are present in the device. PCI device drivers often use header files to describe the hardware peripherals and their resources as there is no standard data driven way to do so. This patch series proposes to use flattened device tree blob to describe the peripherals in a data driven way. Based on previous discussion, using device tree overlay is the best way to unflatten the blob and populate platform devices. To use device tree overlay, there are three obvious problems that need to be resolved. First, we need to create a base tree for non-DT system such as x86_64. A patch series has been submitted for this: https://lore.kernel.org/lkml/20220624034327.2542112-1-frowand.list@gmail.com/ https://lore.kernel.org/lkml/20220216050056.311496-1-lizhi.hou@xilinx.com/ Second, a device tree node corresponding to the PCI endpoint is required for overlaying the flattened device tree blob for that PCI endpoint. Because PCI is a self-discoverable bus, a device tree node is usually not created for PCI devices. This series adds support to generate a device tree node for a PCI device which advertises itself using PCI quirks infrastructure. Third, we need to generate device tree nodes for PCI bridges since a child PCI endpoint may choose to have a device tree node created. This patch series is made up of three patches. The first patch is adding OF interface to create or destroy OF node dynamically. The second patch introduces a kernel option, CONFIG_DYNAMIC_PCI_OF_NODEX. When the option is turned on, the kernel will generate device tree nodes for all PCI bridges unconditionally. The patch also shows how to use the PCI quirks infrastructure, DECLARE_PCI_FIXUP_FINAL to generate a device tree node for a device. Specifically, the patch generates a device tree node for Xilinx Alveo U50 PCIe accelerator device. The generated device tree nodes do not have any property. The third patch adds basic properties ('reg', 'compatible' and 'device_type') to the dynamically generated device tree nodes. More properties can be added in the future. Here is the example of device tree nodes generated within the ARM64 QEMU. # lspci -t -[0000:00]-+-00.0 +-01.0-[01]-- +-01.1-[02]----00.0 +-01.2-[03]----00.0 +-01.3-[04]----00.0 +-01.4-[05]----00.0 +-01.5-[06]-- +-01.6-[07]-- +-01.7-[08]-- +-02.0-[09-0b]----00.0-[0a-0b]----00.0-[0b]--+-00.0 | \-00.1 +-02.1-[0c]-- \-03.0-[0d-0e]----00.0-[0e]----01.0 # tree /sys/firmware/devicetree/base/pcie\@10000000 /sys/firmware/devicetree/base/pcie@10000000 |-- #address-cells |-- #interrupt-cells |-- #size-cells |-- bus-range |-- compatible |-- device_type |-- dma-coherent |-- interrupt-map |-- interrupt-map-mask |-- linux,pci-domain |-- msi-parent |-- name |-- pci@1,0 | |-- #address_cells | |-- #size_cells | |-- compatible | |-- device_type | |-- ranges | `-- reg |-- pci@1,1 | |-- #address_cells | |-- #size_cells | |-- compatible | |-- device_type | |-- ranges | `-- reg |-- pci@1,2 | |-- #address_cells | |-- #size_cells | |-- compatible | |-- device_type | |-- ranges | `-- reg |-- pci@1,3 | |-- #address_cells | |-- #size_cells | |-- compatible | |-- device_type | |-- ranges | `-- reg |-- pci@1,4 | |-- #address_cells | |-- #size_cells | |-- compatible | |-- device_type | |-- ranges | `-- reg |-- pci@1,5 | |-- #address_cells | |-- #size_cells | |-- compatible | |-- device_type | |-- ranges | `-- reg |-- pci@1,6 | |-- #address_cells | |-- #size_cells | |-- compatible | |-- device_type | |-- ranges | `-- reg |-- pci@1,7 | |-- #address_cells | |-- #size_cells | |-- compatible | |-- device_type | |-- ranges | `-- reg |-- pci@2,0 | |-- #address_cells | |-- #size_cells | |-- compatible | |-- device_type | |-- pci@0,0 | | |-- #address_cells | | |-- #size_cells | | |-- compatible | | |-- device_type | | |-- pci@0,0 | | | |-- #address_cells | | | |-- #size_cells | | | |-- compatible | | | |-- dev@0,0 | | | | |-- compatible | | | | `-- reg | | | |-- dev@0,1 | | | | |-- compatible | | | | `-- reg | | | |-- device_type | | | |-- ranges | | | `-- reg | | |-- ranges | | `-- reg | |-- ranges | `-- reg |-- pci@2,1 | |-- #address_cells | |-- #size_cells | |-- compatible | |-- device_type | |-- ranges | `-- reg |-- pci@3,0 | |-- #address_cells | |-- #size_cells | |-- compatible | |-- device_type | |-- pci@0,0 | | |-- #address_cells | | |-- #size_cells | | |-- compatible | | |-- device_type | | |-- ranges | | `-- reg | |-- ranges | `-- reg |-- ranges `-- reg Changes since RFC v4: - Fixed code review comments Changes since RFC v3: - Split the Xilinx Alveo U50 PCI quirk to a separate patch - Minor changes in commit description and code comment Changes since RFC v2: - Merged patch 3 with patch 2 - Added OF interfaces of_changeset_add_prop_* and use them to create properties. - Added '#address-cells', '#size-cells' and 'ranges' properties. Changes since RFC v1: - Added one patch to create basic properties. - To move DT related code out of PCI subsystem, replaced of_node_alloc() with of_create_node()/of_destroy_node() Lizhi Hou (3): of: dynamic: Add interfaces for creating device node dynamically PCI: Create device tree node for selected devices PCI: Add PCI quirks to generate device tree node for Xilinx Alveo U50 drivers/of/dynamic.c | 197 ++++++++++++++++++++++++++++++++ drivers/pci/Kconfig | 12 ++ drivers/pci/Makefile | 1 + drivers/pci/bus.c | 2 + drivers/pci/msi/irqdomain.c | 6 +- drivers/pci/of.c | 71 ++++++++++++ drivers/pci/of_property.c | 222 ++++++++++++++++++++++++++++++++++++ drivers/pci/pci-driver.c | 3 +- drivers/pci/pci.h | 19 +++ drivers/pci/quirks.c | 11 ++ drivers/pci/remove.c | 1 + include/linux/of.h | 24 ++++ 12 files changed, 566 insertions(+), 3 deletions(-) create mode 100644 drivers/pci/of_property.c