From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CB12BC43215 for ; Mon, 2 Dec 2019 23:31:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9C59A20684 for ; Mon, 2 Dec 2019 23:31:51 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="FHbq7/qo" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726443AbfLBXbu (ORCPT ); Mon, 2 Dec 2019 18:31:50 -0500 Received: from mail-wm1-f41.google.com ([209.85.128.41]:53934 "EHLO mail-wm1-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725957AbfLBXbu (ORCPT ); Mon, 2 Dec 2019 18:31:50 -0500 Received: by mail-wm1-f41.google.com with SMTP id u18so1106477wmc.3 for ; Mon, 02 Dec 2019 15:31:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=xWcs6YBFvK3VWP3N+z+8H4QcT8nQTNi3hW2Yzv1rJdI=; b=FHbq7/qo14idRh4Ycz3BnsTzhOXiVAEwxYErTdKgCSDH61utWT62Z7CfuhzZnQdL+B pxz030T16txh09dKbYYBucqWounpt7XrZXahIEa5f9HVvtWfiA30+WXyFp8rGY3MSKXG uAbONxC7GcKnHmhyp/SFHpGKIEZYln3HNhz3g= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=xWcs6YBFvK3VWP3N+z+8H4QcT8nQTNi3hW2Yzv1rJdI=; b=FiEEt3lv+UA9cCk8QIn+dTCowgiyl/p8H2cZxpldukvNvhBXQ5rqxci/Ut2X5aH5tC FS+Y8wvuwY13Ofg32NK7YqyyLsirI6qxwNJiXY9+hHAmZVM/cdgJOI4SR7rbOePATZXz ThC8nrw7wjYWE4nC9W0A5IQ/WEiB6ZwlpLjDU23ypS43xvHHp5p6p2Jetm5dM3JIgJ9O EvRe6gFyEvuhRNv9ck3PZxHSKevDU32GErkAcPZaAROgabd2GlZHMHSUo1oh1/ql856C jEeVGlkMGCVnngLKQ866GsKvjtHvcDEtB+024O/kjiJo+L6sP3tXcu+jTnqJAyG4bjvP +NcQ== X-Gm-Message-State: APjAAAWwW3+Bb0xtlJtcDJhjgK+HK1lMQho0+YCWiFadFev9n758XrBO KagSS7vlMcSiMh6WmFB1qBCVBw== X-Google-Smtp-Source: APXvYqxmaGXdgBpgNe29YrOm+siaQQufajyUm4E1xiLmmCBSR0ydUEMysFw8OjRat34k1cVFfuznvQ== X-Received: by 2002:a7b:cf39:: with SMTP id m25mr4427262wmg.146.1575329508184; Mon, 02 Dec 2019 15:31:48 -0800 (PST) Received: from rj-aorus.ric.broadcom.com ([192.19.228.250]) by smtp.gmail.com with ESMTPSA id c72sm1066197wmd.11.2019.12.02.15.31.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Dec 2019 15:31:47 -0800 (PST) From: Ray Jui To: Rob Herring , Mark Rutland Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, Rayagonda Kokatanur , Ray Jui Subject: [PATCH 1/2] dt-bindings: soc: Add binding doc for iProc IDM device Date: Mon, 2 Dec 2019 15:31:26 -0800 Message-Id: <20191202233127.31160-2-ray.jui@broadcom.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20191202233127.31160-1-ray.jui@broadcom.com> References: <20191202233127.31160-1-ray.jui@broadcom.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add binding document for iProc based IDM devices. Signed-off-by: Ray Jui --- .../bindings/soc/bcm/brcm,iproc-idm.txt | 44 +++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,iproc-idm.txt diff --git a/Documentation/devicetree/bindings/soc/bcm/brcm,iproc-idm.txt b/Documentation/devicetree/bindings/soc/bcm/brcm,iproc-idm.txt new file mode 100644 index 000000000000..388c6b036d7e --- /dev/null +++ b/Documentation/devicetree/bindings/soc/bcm/brcm,iproc-idm.txt @@ -0,0 +1,44 @@ +Broadcom iProc Interconnect Device Management (IDM) device + +The Broadcom iProc IDM device allows control and monitoring of ASIC internal +bus transactions. Most importantly, it can be configured to detect bus +transaction timeout. In such case, critical information such as transaction +address that caused the error, bus master ID of the transaction that caused +the error, and etc., are made available from the IDM device. + +------------------------------------------------------------------------------- + +Required properties for IDM device node: +- compatible: must be "brcm,iproc-idm" +- reg: base address and length of the IDM register space +- interrupt: IDM interrupt number +- brcm,iproc-idm-bus: IDM bus string + +Optional properties for IDM device node: +- brcm,iproc-idm-elog: phandle to the device node of the IDM logging device + +------------------------------------------------------------------------------- + +Required properties for IDM error logging device node: +- compatible: must be "brcm,iproc-idm-elog"; +- reg: base address and length of reserved memory location where IDM error + events can be saved + +------------------------------------------------------------------------------- + +Example: + +idm { + idm-elog { + compatible = "brcm,iproc-idm-elog"; + reg = <0x8f221000 0x1000>; + }; + + idm-mhb-paxc-axi { + compatible = "brcm,iproc-idm"; + reg = <0x60406900 0x200>; + interrupt = ; + brcm,iproc-idm-bus = "idm-mhb-paxc-axi"; + brcm,iproc-idm-elog = <&idm-elog>; + }; +}; -- 2.17.1