From: Marc Zyngier <maz@kernel.org>
To: Ray Jui <ray.jui@broadcom.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
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
Date: Sat, 7 Dec 2019 17:39:14 +0000 [thread overview]
Message-ID: <20191207173914.353f768d@why> (raw)
In-Reply-To: <20191202233127.31160-1-ray.jui@broadcom.com>
On Mon, 2 Dec 2019 15:31:25 -0800
Ray Jui <ray.jui@broadcom.com> 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...
next prev parent reply other threads:[~2019-12-07 17:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 23:31 [PATCH 0/2] Add iProc IDM device support Ray Jui
2019-12-02 23:31 ` [PATCH 1/2] dt-bindings: soc: Add binding doc for iProc IDM device Ray Jui
2019-12-06 0:09 ` Florian Fainelli
2019-12-07 1:09 ` Ray Jui
2019-12-13 23:50 ` Rob Herring
2019-12-14 0:00 ` Florian Fainelli
2019-12-16 15:52 ` Rob Herring
2019-12-02 23:31 ` [PATCH 2/2] soc: bcm: iproc: Add Broadcom iProc IDM driver Ray Jui
2019-12-06 0:22 ` Florian Fainelli
2019-12-07 1:15 ` Ray Jui
2019-12-07 17:52 ` Florian Fainelli
2019-12-09 18:05 ` Ray Jui
2019-12-07 17:39 ` Marc Zyngier [this message]
2019-12-09 18:02 ` [PATCH 0/2] Add iProc IDM device support Ray Jui
2019-12-09 18:36 ` Marc Zyngier
2019-12-10 0:19 ` Ray Jui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191207173914.353f768d@why \
--to=maz@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ray.jui@broadcom.com \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).