Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp5461516rwb; Mon, 21 Nov 2022 23:42:15 -0800 (PST) X-Google-Smtp-Source: AA0mqf4RwhdjycRho+wCOZHW5Q28xoQIHg1pDelXlsTZf66wUsK0bFLWOEWxGisy3BIoEBNnZB5a X-Received: by 2002:a17:903:204b:b0:179:fe95:f6d9 with SMTP id q11-20020a170903204b00b00179fe95f6d9mr4325284pla.51.1669102935487; Mon, 21 Nov 2022 23:42:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669102935; cv=none; d=google.com; s=arc-20160816; b=oQfHQCwaD09zvvsjdDVctIfNvr3iTFd8ajw1LyAlpAiGoWBeXedCBj3wr4iIgRRPHY vUVwrwY0KFmLW3yEZGWPBytXQTpB5rXNlZuOm6DIW57Lpgfb7I60gEA1WXSRuRXX6ylg fXAWbNjOnZmWAwxG7MBiYhz5wg6T9zh+hddCHLx06CI4YxrifSK46kA01MnUL3jZ61hz ftOAvDOw7QMahDdnNkLYPhMwOkPB3FtQLVnF4dzmJxur7ai53Qi+pojsKY4tlny7gbHO xuHW07JBIFZzvrv30oxBUn7y9lcN9KTc9sMpdpJqEHQhO5cD9heXEBTxdhOaRCVG8Js+ SMNQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=bJ2u7mh9nd2kJ2SvCMIUbxbNtsjSUFYoRollOBUuJAE=; b=UE/acGEZT2h2C3lxGl7vp+5M9nQjpXS5Rd2/uwuI8ZX9CrSs9HmhJE3pMqAgTV+wI4 OX+hADUAOdUNzUFCILnx4rginl/e99zLb8qc5wiLbh4z9mUvA7s6XiQUsskedMV0elT/ gZ5OVO0k7pub4Q1lSupd991ljpNY8t1oLl78zjOdJG+GIizCbo57z1d2Pz6so0Ox0SjT yiHcBXUgjw9V0U0xvqXrhmE0uGrbVzHiH4k5g+0t/PZ0VULa/b/Q0xosptr0MTFNBc/m xbd5vwP7O3cOaXnO2WRisNjP1SSEiDfjsyh1itYcuNra+QCwpLas/tvbs5SHyTe4Rlwq Y+mw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@maxlinear.com header.s=selector header.b=dFC6GbAP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=maxlinear.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id oj2-20020a17090b4d8200b001fe1cc52234si14513766pjb.67.2022.11.21.23.42.03; Mon, 21 Nov 2022 23:42:15 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@maxlinear.com header.s=selector header.b=dFC6GbAP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=maxlinear.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232438AbiKVHka (ORCPT + 92 others); Tue, 22 Nov 2022 02:40:30 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49996 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232242AbiKVHkW (ORCPT ); Tue, 22 Nov 2022 02:40:22 -0500 Received: from us-smtp-delivery-115.mimecast.com (us-smtp-delivery-115.mimecast.com [170.10.129.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 94981B491 for ; Mon, 21 Nov 2022 23:39:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=maxlinear.com; s=selector; t=1669102762; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bJ2u7mh9nd2kJ2SvCMIUbxbNtsjSUFYoRollOBUuJAE=; b=dFC6GbAPpM573pcrn5gst2XnY+L432w5W0DYRLYPUtrXc4RdAbX1VkTDfsXSeh1OqvDHJ4 N2unV+4HbIgbRC53hwGi1p8QYX3Q82uACfD992EePRQuMSwl8FcNdwg3Y26GKmULY7ciwa Zll8ZHTk+NqW2cxFTvpmaGO92PTRQ0U5WMSx9Q4wU4l8J9WKTEJEaWPE8TzRHY+myFWXOU XUmPcrnmcsR9s6XB8jgINsi18CLziugKkYpdXd5xwUIRHkLN2vSU3+KG0fBQiQQ0KveAg6 TdtNLVnJ/2/dFdV8gTJ+gaqAejSfcsij+CbxSz0TlNFdWu8cHPTsNq1CJgkN4Q== Received: from mail.maxlinear.com (174-47-1-84.static.ctl.one [174.47.1.84]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id us-mta-9-8qG2M24zMBahALnruAeT0w-2; Tue, 22 Nov 2022 02:39:21 -0500 X-MC-Unique: 8qG2M24zMBahALnruAeT0w-2 Received: from sgsxdev001.isng.phoenix.local (10.226.81.111) by mail.maxlinear.com (10.23.38.119) with Microsoft SMTP Server id 15.1.2375.24; Mon, 21 Nov 2022 23:39:17 -0800 From: Rahul Tanwar To: , , , , , , CC: , , , , Rahul Tanwar Subject: [PATCH v3 1/4] x86/of: Convert Intel's APIC bindings to YAML schema Date: Tue, 22 Nov 2022 15:39:07 +0800 Message-ID: <0cf089495a422b945ac4fc9c980ddb5429a711c3.1669100394.git.rtanwar@maxlinear.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: References: MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: maxlinear.com Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Intel's APIC family of interrupt controllers support local APIC (lapic) & I/O APIC (ioapic). Convert existing bindings for lapic & ioapic from text to YAML schema. Separate lapic & ioapic schemas. Addditionally, add description which was missing in text file and add few more required standard properties which were also missing in text file. Suggested-by: Andy Shevchenko Signed-off-by: Rahul Tanwar --- .../intel,ce4100-ioapic.txt | 26 -------- .../intel,ce4100-ioapic.yaml | 62 +++++++++++++++++++ .../intel,ce4100-lapic.yaml | 49 +++++++++++++++ 3 files changed, 111 insertions(+), 26 deletions(-) delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/= intel,ce4100-ioapic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/= intel,ce4100-ioapic.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/= intel,ce4100-lapic.yaml diff --git a/Documentation/devicetree/bindings/interrupt-controller/intel,c= e4100-ioapic.txt b/Documentation/devicetree/bindings/interrupt-controller/i= ntel,ce4100-ioapic.txt deleted file mode 100644 index 7d19f494f19a..000000000000 --- a/Documentation/devicetree/bindings/interrupt-controller/intel,ce4100-i= oapic.txt +++ /dev/null @@ -1,26 +0,0 @@ -Interrupt chips ---------------- - -* Intel I/O Advanced Programmable Interrupt Controller (IO APIC) - - Required properties: - -------------------- - compatible =3D "intel,ce4100-ioapic"; - #interrupt-cells =3D <2>; - - Device's interrupt property: - - interrupts =3D

; - - The first number (P) represents the interrupt pin which is wired to the - IO APIC. The second number (S) represents the sense of interrupt which - should be configured and can be one of: - 0 - Edge Rising - 1 - Level Low - 2 - Level High - 3 - Edge Falling - -* Local APIC - Required property: - - compatible =3D "intel,ce4100-lapic"; diff --git a/Documentation/devicetree/bindings/interrupt-controller/intel,c= e4100-ioapic.yaml b/Documentation/devicetree/bindings/interrupt-controller/= intel,ce4100-ioapic.yaml new file mode 100644 index 000000000000..da966287eec2 --- /dev/null +++ b/Documentation/devicetree/bindings/interrupt-controller/intel,ce4100-i= oapic.yaml @@ -0,0 +1,62 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: "http://devicetree.org/schemas/interrupt-controller/intel,ce4100-ioap= ic.yaml#" +$schema: "http://devicetree.org/meta-schemas/core.yaml#" + +title: Intel I/O Advanced Programmable Interrupt Controller (IO APIC) + +maintainers: + - Sebastian Andrzej Siewior + + +description: | + Intel's Advanced Programmable Interrupt Controller (APIC) is a + family of interrupt controllers. The APIC is a split + architecture design, with a local component (LAPIC) integrated + into the processor itself and an external I/O APIC. Local APIC + (lapic) receives interrupts from the processor's interrupt pins, + from internal sources and from an external I/O APIC (ioapic). + And it sends these to the processor core for handling. + See https://pdos.csail.mit.edu/6.828/2008/readings/ia32/IA32-3A.pdf + Chapter 8 for more details. + + Many of the Intel's generic devices like hpet, ioapic, lapic have + the ce4100 name in their compatible property names because they + first appeared in CE4100 SoC. See bindings/x86/ce4100.txt for more + details on it. + + This schema defines bindings for I/O APIC interrupt controller. + +properties: + compatible: + const: intel,ce4100-ioapic + + reg: + maxItems: 1 + + interrupt-controller: true + + '#interrupt-cells': + const: 2 + + interrupts: + maxItems: 1 + +required: + - compatible + - reg + - interrupt-controller + - '#interrupt-cells' + +additionalProperties: false + +examples: + - | + ioapic1: interrupt-controller@fec00000 { + compatible =3D "intel,ce4100-ioapic"; + reg =3D <0xfec00000 0x1000>; + #interrupt-cells =3D <2>; + #address-cells =3D <0>; + interrupt-controller; + }; diff --git a/Documentation/devicetree/bindings/interrupt-controller/intel,c= e4100-lapic.yaml b/Documentation/devicetree/bindings/interrupt-controller/i= ntel,ce4100-lapic.yaml new file mode 100644 index 000000000000..d4b99bf7bf6e --- /dev/null +++ b/Documentation/devicetree/bindings/interrupt-controller/intel,ce4100-l= apic.yaml @@ -0,0 +1,49 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: "http://devicetree.org/schemas/interrupt-controller/intel,ce4100-lapi= c.yaml#" +$schema: "http://devicetree.org/meta-schemas/core.yaml#" + +title: Intel Local Advanced Programmable Interrupt Controller (LAPIC) + +maintainers: + - Sebastian Andrzej Siewior + + +description: | + Intel's Advanced Programmable Interrupt Controller (APIC) is a + family of interrupt controllers. The APIC is a split + architecture design, with a local component (LAPIC) integrated + into the processor itself and an external I/O APIC. Local APIC + (lapic) receives interrupts from the processor's interrupt pins, + from internal sources and from an external I/O APIC (ioapic). + And it sends these to the processor core for handling. + See https://pdos.csail.mit.edu/6.828/2008/readings/ia32/IA32-3A.pdf + Chapter 8 for more details. + + Many of the Intel's generic devices like hpet, ioapic, lapic have + the ce4100 name in their compatible property names because they + first appeared in CE4100 SoC. See bindings/x86/ce4100.txt for more + details on it. + + This schema defines bindings for local APIC interrupt controller. + +properties: + compatible: + const: intel,ce4100-lapic + + reg: + maxItems: 1 + +required: + - compatible + - reg + +additionalProperties: false + +examples: + - | + lapic0: interrupt-controller@fee00000 { + compatible =3D "intel,ce4100-lapic"; + reg =3D <0xfee00000 0x1000>; + }; --=20 2.17.1