From: Srinivas Goud <srinivas.goud@amd.com>
To: <wg@grandegger.com>, <mkl@pengutronix.de>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <p.zabel@pengutronix.de>
Cc: <git@amd.com>, <michal.simek@xilinx.com>,
<linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <appana.durga.rao@xilinx.com>,
<naga.sureshkumar.relli@xilinx.com>,
Srinivas Goud <srgoud@xhdsgoud40.xilinx.com>
Subject: [PATCH v6 0/3] can: xilinx_can: Add ECC feature support
Date: Sat, 25 Nov 2023 16:45:30 +0530 [thread overview]
Message-ID: <1700910933-23868-1-git-send-email-srinivas.goud@amd.com> (raw)
From: Srinivas Goud <srgoud@xhdsgoud40.xilinx.com>
Add ECC feature support to Tx and Rx FIFOs for Xilinx CAN Controller.
ECC is an IP configuration option where counter registers are added in
IP for 1bit/2bit ECC errors count and reset.
Also driver reports 1bit/2bit ECC errors for FIFOs based on ECC error
interrupts.
Add xlnx,has-ecc optional property for Xilinx AXI CAN controller
to support ECC if the ECC block is enabled in the HW.
Add ethtool stats interface for getting all the ECC errors information.
There is no public documentation for it available.
---
BRANCH: linux-can-next/master
Changes in v6:
Update commit description
Changes in v5:
Fix review comments
Change the sequence of updates the stats
Add get_strings and get_sset_count stats interface
Use u64 stats helper function
Changes in v4:
Fix DT binding check warning
Update xlnx,has-ecc property description
Changes in v3:
Update mailing list
Update commit description
Changes in v2:
Address review comments
Add ethtool stats interface
Update commit description
Srinivas Goud (3):
dt-bindings: can: xilinx_can: Add 'xlnx,has-ecc' optional property
can: xilinx_can: Add ECC support
can: xilinx_can: Add ethtool stats interface for ECC errors
.../devicetree/bindings/net/can/xilinx,can.yaml | 5 +
drivers/net/can/xilinx_can.c | 159 ++++++++++++++++++++-
2 files changed, 160 insertions(+), 4 deletions(-)
--
2.1.1
next reply other threads:[~2023-11-25 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 11:15 Srinivas Goud [this message]
2023-11-25 11:15 ` [PATCH v6 1/3] dt-bindings: can: xilinx_can: Add 'xlnx,has-ecc' optional property Srinivas Goud
2023-11-25 11:15 ` [PATCH v6 2/3] can: xilinx_can: Add ECC support Srinivas Goud
2023-11-25 11:15 ` [PATCH v6 3/3] can: xilinx_can: Add ethtool stats interface for ECC errors Srinivas Goud
2023-11-25 17:04 ` Marc Kleine-Budde
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=1700910933-23868-1-git-send-email-srinivas.goud@amd.com \
--to=srinivas.goud@amd.com \
--cc=appana.durga.rao@xilinx.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=git@amd.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mkl@pengutronix.de \
--cc=naga.sureshkumar.relli@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=srgoud@xhdsgoud40.xilinx.com \
--cc=wg@grandegger.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).