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=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_2 autolearn=no 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 4F653C43603 for ; Sat, 7 Dec 2019 17:39:29 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 20E8024673 for ; Sat, 7 Dec 2019 17:39:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="OTQZkyxW" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 20E8024673 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=ujOfL2DtwYu9pCmV1HhhZffavLMX1l88vLzy4dv9F5o=; b=OTQZkyxWI0XzmS zcUzSaMJwm5XLyPOSF/5/vtnIsMZPJ4c5fbePh22LWGmGFbWWvSMSKPs3chfO85ViGae8ILcFyPAa y3XW6MP30ZBFc6KtnqdeUHBBRDmN6IcLCdASduRmr5RR0DjDTLK4mYjCeJ8ujz4G9JSosv6DWxPEv hLL0hSOytCqYN20FQXhH24pslgqVz3VLbHifkCSZL53SHjeIeY2byxAD0Ho3rwuj298hqwzVe4wP9 LhrgxtLYWRYa1lZN8qP2exYqB8bk7J3R6KR1VrLr4E8++EO+Eh8y1mrib6lTbQGEaZG9ev3orUB/j ZdAG5SHpc3bhoCwGamxw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1ide3B-0003pV-QP; Sat, 07 Dec 2019 17:39:25 +0000 Received: from inca-roads.misterjones.org ([213.251.177.50]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1ide37-0003oh-Qi for linux-arm-kernel@lists.infradead.org; Sat, 07 Dec 2019 17:39:23 +0000 Received: from 78.163-31-62.static.virginmediabusiness.co.uk ([62.31.163.78] helo=why) by cheepnis.misterjones.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.80) (envelope-from ) id 1ide32-0008Ha-2c; Sat, 07 Dec 2019 18:39:16 +0100 Date: Sat, 7 Dec 2019 17:39:14 +0000 From: Marc Zyngier To: Ray Jui Subject: Re: [PATCH 0/2] Add iProc IDM device support Message-ID: <20191207173914.353f768d@why> In-Reply-To: <20191202233127.31160-1-ray.jui@broadcom.com> References: <20191202233127.31160-1-ray.jui@broadcom.com> Organization: Approximate X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 X-SA-Exim-Connect-IP: 62.31.163.78 X-SA-Exim-Rcpt-To: ray.jui@broadcom.com, robh+dt@kernel.org, mark.rutland@arm.com, devicetree@vger.kernel.org, rayagonda.kokatanur@broadcom.com, linux-kernel@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-arm-kernel@lists.infradead.org X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on cheepnis.misterjones.org); SAEximRunCond expanded to false X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20191207_093922_013453_D33BAF18 X-CRM114-Status: UNSURE ( 8.58 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , devicetree@vger.kernel.org, Rayagonda Kokatanur , linux-kernel@vger.kernel.org, Rob Herring , bcm-kernel-feedback-list@broadcom.com, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, 2 Dec 2019 15:31:25 -0800 Ray Jui wrote: > 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. This seems to have many of the features of an EDAC device reporting uncorrectable errors. Is there any reason why it is not implemented as such? Thanks, M. -- Jazz is not dead. It just smells funny... _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel 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=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_2 autolearn=no 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 BC35FC43603 for ; Sat, 7 Dec 2019 17:39:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8CD66217BA for ; Sat, 7 Dec 2019 17:39:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1575740360; bh=T++ydQOV27cJbVsEb9mju7e2HDkTJb9/H8TvZE8Cq9s=; h=Date:From:To:Cc:Subject:In-Reply-To:References:List-ID:From; b=dSru8aOvu3TJnvcMc1JMbCc+LckSQBWjvdhMeIisAyVqpnM75jCSZPoORdLin/ZL6 oL7iRi3C5R3TxxQxGC7NrYGbQlPC4n+EQOgLGRPFWpmZnZWxrb9gK2Krsi0lBk0FT4 gy1IUJtCQ1sThwIfIZRbbXZOCYWXQVz0rn72XnUM= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726464AbfLGRjU (ORCPT ); Sat, 7 Dec 2019 12:39:20 -0500 Received: from inca-roads.misterjones.org ([213.251.177.50]:55248 "EHLO inca-roads.misterjones.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726455AbfLGRjT (ORCPT ); Sat, 7 Dec 2019 12:39:19 -0500 Received: from 78.163-31-62.static.virginmediabusiness.co.uk ([62.31.163.78] helo=why) by cheepnis.misterjones.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.80) (envelope-from ) id 1ide32-0008Ha-2c; Sat, 07 Dec 2019 18:39:16 +0100 Date: Sat, 7 Dec 2019 17:39:14 +0000 From: Marc Zyngier To: Ray Jui Cc: Rob Herring , Mark Rutland , devicetree@vger.kernel.org, Rayagonda Kokatanur , linux-kernel@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 0/2] Add iProc IDM device support Message-ID: <20191207173914.353f768d@why> In-Reply-To: <20191202233127.31160-1-ray.jui@broadcom.com> References: <20191202233127.31160-1-ray.jui@broadcom.com> Organization: Approximate X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 62.31.163.78 X-SA-Exim-Rcpt-To: ray.jui@broadcom.com, robh+dt@kernel.org, mark.rutland@arm.com, devicetree@vger.kernel.org, rayagonda.kokatanur@broadcom.com, linux-kernel@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-arm-kernel@lists.infradead.org X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on cheepnis.misterjones.org); SAEximRunCond expanded to false Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Mon, 2 Dec 2019 15:31:25 -0800 Ray Jui wrote: > 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. This seems to have many of the features of an EDAC device reporting uncorrectable errors. Is there any reason why it is not implemented as such? Thanks, M. -- Jazz is not dead. It just smells funny...