Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp4324049imw; Tue, 12 Jul 2022 06:09:21 -0700 (PDT) X-Google-Smtp-Source: AGRyM1u8U7IQ8p+CNk5tZMXZ1HXHlFiLUTFhhryNASMWgN464NW96BaJ3kRjllVqRtoKEmMa4uHL X-Received: by 2002:aa7:ce8a:0:b0:43a:7b0e:9950 with SMTP id y10-20020aa7ce8a000000b0043a7b0e9950mr31963811edv.58.1657631360776; Tue, 12 Jul 2022 06:09:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657631360; cv=none; d=google.com; s=arc-20160816; b=NtuEeOb5CfFzCn6O7pOH9tbzZ+RJ5ShjEX/A15C+y2DwVJHhJIAVH1R51J3MCLlNJL 7jHo81/x3DjcLWtdYrGwN0+gMIKWUHWpJEC/RXGP94JAw8N82UVRgQD/EvPIUgVqiY5c TB/k4BUxy4QrapfDuvFPRbA46xJ/kBFyNOPCbd9p4cnFw1NweECSjKVI921szMfHYIiQ sM2TkdUAnC6R6CLGZWRZZaQfiE0DGag0BlL2Chs8YIAYVtqZaI6fU9pfMmPZ4gU/Q6cn gVB8wCwJJGno0SXmrUIhnemO95MGFxFStNQohy8D3F1aOuRF5kcigRBTWiN6+j/8dNld 0YiA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=uXl3CHb8A/lD5jRqmuHsnL9LNcbpf2vMXAR0gdRhKTI=; b=ooqXNfuIiCdGsng0UQ/52HTM/5tC+QCub9ipfamfa9opHaM0A2U10td3m/I7kHivR/ I6KyKxBxd6HA5u4cWfLfDsUQZZAF1ccfcVadQ4ik8pgNJyFhfWRvvcj0NdMcu7HsZSQZ DBCsv95IdyDDb8qRNJjCM5RBySuyctlmZjtUItm47MdYXtE7Xhpev3WpYmFLOACAc18s hJpD9RCzrZUqgWCZg1yqyMV4QoOC/3zb3N8jBPzALlhezlAGvWgDbHEZqJ8zG+0yUMrc z0oKyxu/esEm3RKB9yRYTdPx94zAwtPJW0r+CrXVo05U2A2cd/xHH7QREAFktb+KMHfb MVYA== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id oz37-20020a1709077da500b00711ca15cd48si553254ejc.939.2022.07.12.06.08.55; Tue, 12 Jul 2022 06:09:20 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233337AbiGLMyn (ORCPT + 99 others); Tue, 12 Jul 2022 08:54:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42292 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233321AbiGLMym (ORCPT ); Tue, 12 Jul 2022 08:54:42 -0400 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 7CC36AA761; Tue, 12 Jul 2022 05:54:41 -0700 (PDT) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A1A1D1596; Tue, 12 Jul 2022 05:54:41 -0700 (PDT) Received: from [10.57.85.194] (unknown [10.57.85.194]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 2D11B3F70D; Tue, 12 Jul 2022 05:54:39 -0700 (PDT) Message-ID: <94ab770b-8a8a-4299-a54e-2ff77afb9e04@arm.com> Date: Tue, 12 Jul 2022 13:54:37 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [PATCH 4/4] dt-binding:perf: Add Amlogic DDR PMU Content-Language: en-GB To: Jiucheng Xu , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org Cc: Rob Herring , Krzysztof Kozlowski , Will Deacon , Mark Rutland , Neil Armstrong , Kevin Hilman , Jerome Brunet , Martin Blumenstingl , Chris Healy References: <20220712063641.2790997-1-jiucheng.xu@amlogic.com> <20220712063641.2790997-4-jiucheng.xu@amlogic.com> From: Robin Murphy In-Reply-To: <20220712063641.2790997-4-jiucheng.xu@amlogic.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE 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 On 2022-07-12 07:36, Jiucheng Xu wrote: > Add binding documentation for the Amlogic G12 series DDR > performance monitor unit. > > Signed-off-by: Jiucheng Xu > --- > .../devicetree/bindings/perf/aml-ddr-pmu.yaml | 51 +++++++++++++++++++ > MAINTAINERS | 1 + > 2 files changed, 52 insertions(+) > create mode 100644 Documentation/devicetree/bindings/perf/aml-ddr-pmu.yaml > > diff --git a/Documentation/devicetree/bindings/perf/aml-ddr-pmu.yaml b/Documentation/devicetree/bindings/perf/aml-ddr-pmu.yaml > new file mode 100644 > index 000000000000..c586b4ab4009 > --- /dev/null > +++ b/Documentation/devicetree/bindings/perf/aml-ddr-pmu.yaml > @@ -0,0 +1,51 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/perf/aml-ddr-pmu.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Amlogic G12 DDR performance monitor > + > +maintainers: > + - Jiucheng Xu > + > +properties: > + compatible: > + oneOf: > + - enum: > + - aml,g12-ddr-pmu > + - items: > + - enum: > + - aml,g12-ddr-pmu > + - const: aml,g12-ddr-pmu Judging by what the driver actually implements, this should probably be: compatible: items: - enum: - amlogic,g12a-ddr-pmu - amlogic,g12b-ddr-pmu - amlogic,sm1-ddr-pmu - const: amlogic,g12-ddr-pmu There doesn't seem much point in allowing only the common compatible without a SoC-specific identifier. Note also that "aml," is not the documented vendor prefix. > + > + reg: > + maxItems: 2 > + > + interrupts: > + maxItems: 1 > + > +required: > + - compatible > + - model Remove this, and use the compatible strings properly as above. > + - dmc_nr > + - chann_nr I suspect those could probably be inferred from the correct compatible string, but if not (i.e. within one SoC you have multiple PMUs supporting the same events but with different numbers of usable channels), then document what exactly they mean. > + - reg > + - interrupts > + - interrupt-names As mentioned in the driver review, if you really want to use a named interrupt (which should usually be unnecessary when there's only one), it has to be a defined name. DT is not a mechanism for overriding what Linux shows in /proc/interrupts. Thanks, Robin. > + > +additionalProperties: false > + > +examples: > + - | > + ddr_pmu: ddr_pmu { > + compatible = "amlogic,g12-ddr-pmu"; > + model = "g12a"; > + dmc_nr = <1>; > + chann_nr = <4>; > + reg = <0x0 0xff638000 0x0 0x100 > + 0x0 0xff638c00 0x0 0x100>; > + interrupts = ; > + interrupt-names = "ddr_pmu"; > + }; > + }; > diff --git a/MAINTAINERS b/MAINTAINERS > index fd2a56a339b4..ac0a1df4622d 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -1055,6 +1055,7 @@ M: Jiucheng Xu > S: Supported > W: http://www.amlogic.com > F: Documentation/admin-guide/perf/aml-ddr-pmu.rst > +F: Documentation/devicetree/bindings/perf/aml-ddr-pmu.yaml > F: drivers/perf/amlogic/ > F: include/soc/amlogic/ >