Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp2013977ybm; Thu, 23 May 2019 10:00:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqzHBYb7hXtZ0NZ6DcUJlmgb5hgM7c23QKGCAlCKmj2vhemg5IbU32kj+rNyZ2oDTQvaw/mU X-Received: by 2002:a63:e52:: with SMTP id 18mr98256257pgo.3.1558630816544; Thu, 23 May 2019 10:00:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558630816; cv=none; d=google.com; s=arc-20160816; b=IepIgV9UU7Wkgmur4sxXAuxXafgdwLgxnbuU1ziHcqr2dMMU3XTk/PXFxRo1ZmDqYB l0aFzlHzD030eyVaQiO22/0xXZra4yt+m2AGAXmkvC5D5ybaNZ/YdHYp4CI2UDKPhMCM knwm7zOC8HVDg//i8PFB6ce9drx6/t2wSCvnfNzlw74s9H8sgrCllQmaohBoDzz8miru KHg7IOBqKVTCKzz9XVe5ARy5/lhdIKsfvJquQGAOsMDgXqD9bVsx9xSA0WXM0fy4z+7V MhAGpHy2lkuLsy/4X78V9l2zQvF1ZS1vYRWk4qGqOYr5m6q09/yGP6TzCJCsZP/QGLH/ 7AVA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=mqWJ9rdMKcI9dC6zQ8vkOalJU68bRDYAS7EAPNPnVtA=; b=UhKYQvsThK/tbv63hRL2M7FHIZbSpkJ+iZJO0Xl8416gKiL29smO0FFgwqBQyBx967 rqfGTXZDH1bn9sqKzgf5gzAgfnsys+R5VfnNavgZkmxJ341rqrSb2LflfRpTPKPSDHrM /XD6Br7LaA6MzgCII20ZkW2p71JeHPiK5u/fR6ruR2ymws4PYohj1edOVFzKNdBaSLHL oFR7dqzEMVv2fqUqfWDZOaXwk7J2aFkhNotalETosw0+v2yD8BK2hD65CSYCjW1v7EeP F1teZdZor3AkyIX30EH/qeUzjFQd1CPhrrzpkDmcrT7LQVvxzEdlZFtI4TIv2Nk3XWQP u9sg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h91si1469120pje.38.2019.05.23.10.00.00; Thu, 23 May 2019 10:00:16 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731237AbfEWQ6q (ORCPT + 99 others); Thu, 23 May 2019 12:58:46 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:50982 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730899AbfEWQ6q (ORCPT ); Thu, 23 May 2019 12:58:46 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id DBD31374; Thu, 23 May 2019 09:58:45 -0700 (PDT) Received: from lakrids.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 61A693F5AF; Thu, 23 May 2019 09:58:44 -0700 (PDT) Date: Thu, 23 May 2019 17:58:41 +0100 From: Mark Rutland To: Lei Wang Cc: "bp@alien8.de" , "james.morse@arm.com" , "robh+dt@kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-edac@vger.kernel.org" , "lewan@microsoft.com" Subject: Re: [PATCH v3 1/2] dt-bindings: edac: arm-dmc520.txt Message-ID: <20190523165841.GD7523@lakrids.cambridge.arm.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.1+11 (2f07cb52) (2018-12-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 16, 2019 at 02:35:47AM +0000, Lei Wang wrote: > From: Lei Wang > > This is the device tree bindings for new EDAC driver dmc520_edac.c. > > Signed-off-by: Lei Wang > --- > .../devicetree/bindings/edac/arm-dmc520.txt | 26 ++++++++++++++++++++++ > 1 file changed, 26 insertions(+) > create mode 100644 Documentation/devicetree/bindings/edac/arm-dmc520.txt > > diff --git a/Documentation/devicetree/bindings/edac/arm-dmc520.txt b/Documentation/devicetree/bindings/edac/arm-dmc520.txt > new file mode 100644 > index 0000000..71e7aa3 > --- /dev/null > +++ b/Documentation/devicetree/bindings/edac/arm-dmc520.txt > @@ -0,0 +1,26 @@ > +* ARM DMC-520 EDAC node > + > +Required properties: > +- compatible : "brcm,dmc-520", "arm,dmc-520". > +- reg : Address range of the DMC-520 registers. > +- interrupts : DMC-520 interrupt numbers. The example below specifies > + two interrupt lines for dram_ecc_errc_int and > + dram_ecc_errd_int. > +- interrupt-config : This is an array of interrupt masks. For each of the > + above interrupt line, add one interrupt mask element to > + it. That is, there is a 1:1 mapping from each interrupt > + line to an interrupt mask. An interrupt mask can represent > + multiple interrupts being enabled. Refer to interrupt_control > + register in DMC-520 TRM for interrupt mapping. In the example > + below, the interrupt configuration enables dram_ecc_errc_int > + and dram_ecc_errd_int. And each interrupt is connected to > + a separate interrupt line. Generally we use interrupt-names to distinguish interrupts. Do you really have arbitary subsets of lines muxed together? Thanks, Mark. > + > +Example: > + > +dmc0: dmc@200000 { > + compatible = "brcm,dmc-520", "arm,dmc-520"; > + reg = <0x200000 0x80000>; > + interrupts = <0x0 0x349 0x4>, <0x0 0x34B 0x4>; > + interrupt-config = <0x4>, <0x8>; > +}; > -- > 2.7.4 >