From: Vivek Yadav <vivek.2311@samsung.com>
To: rcsekar@samsung.com, wg@grandegger.com, mkl@pengutronix.de,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, pankaj.dubey@samsung.com,
ravi.patel@samsung.com, alim.akhtar@samsung.com
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vivek Yadav <vivek.2311@samsung.com>
Subject: [PATCH 2/7] dt-bindings: can: mcan: Add ECC functionality to message ram
Date: Fri, 21 Oct 2022 15:28:28 +0530 [thread overview]
Message-ID: <20221021095833.62406-3-vivek.2311@samsung.com> (raw)
In-Reply-To: <20221021095833.62406-1-vivek.2311@samsung.com>
Whenever the data is transferred or stored on message ram, there are
inherent risks of it being lost or corruption known as single-bit errors.
ECC constantly scans data as it is processed to the message ram, using a
method known as parity checking and raise the error signals for corruption.
Add error correction code config property to enable/disable the
error correction code (ECC) functionality for Message RAM used to create
valid ECC checksums.
Signed-off-by: Chandrasekar R <rcsekar@samsung.com>
Signed-off-by: Vivek Yadav <vivek.2311@samsung.com>
---
Documentation/devicetree/bindings/net/can/bosch,m_can.yaml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml b/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
index 26aa0830eea1..0ba3691863d7 100644
--- a/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
+++ b/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
@@ -50,6 +50,10 @@ properties:
- const: hclk
- const: cclk
+ mram-ecc-cfg:
+ items:
+ - description: M_CAN ecc registers map with configuration register offset
+
bosch,mram-cfg:
description: |
Message RAM configuration data.
--
2.17.1
next prev parent reply other threads:[~2022-10-21 12:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221021102614epcas5p18bcb932e697a378a8244bd91065c5496@epcas5p1.samsung.com>
2022-10-21 9:58 ` [PATCH 0/7] can: mcan: Add MCAN support for FSD SoC Vivek Yadav
[not found] ` <CGME20221021102621epcas5p3f10b063ae972bee587eb5beb6e1b5617@epcas5p3.samsung.com>
2022-10-21 9:58 ` [PATCH 1/7] dt-bindings: Document the SYSREG specific compatibles found on " Vivek Yadav
[not found] ` <CGME20221021102625epcas5p4e1c5900b9425e41909e82072f2c1713d@epcas5p4.samsung.com>
2022-10-21 9:58 ` Vivek Yadav [this message]
2022-10-25 7:24 ` [PATCH 2/7] dt-bindings: can: mcan: Add ECC functionality to message ram Marc Kleine-Budde
2022-11-09 8:47 ` Vivek Yadav
2022-10-25 7:31 ` Marc Kleine-Budde
2022-11-09 8:52 ` Vivek Yadav
[not found] ` <CGME20221021102628epcas5p1ecf91523d9db65b066bc4f2cb693ea45@epcas5p1.samsung.com>
2022-10-21 9:58 ` [PATCH 3/7] arm64: dts: fsd: add sysreg device node Vivek Yadav
2022-11-09 11:13 ` Krzysztof Kozlowski
[not found] ` <CGME20221021102632epcas5p29333840201aacbae42bc90f651ac85cd@epcas5p2.samsung.com>
2022-10-21 9:58 ` [PATCH 4/7] can: mcan: enable peripheral clk to access mram Vivek Yadav
2022-10-25 7:44 ` Marc Kleine-Budde
2022-11-09 9:55 ` Vivek Yadav
[not found] ` <CGME20221021102635epcas5p33623e6b6ed02d3fb663da9ec253585ad@epcas5p3.samsung.com>
2022-10-21 9:58 ` [PATCH 5/7] arm64: dts: fsd: Add MCAN device node Vivek Yadav
2022-10-25 7:44 ` Marc Kleine-Budde
2022-11-09 9:16 ` Vivek Yadav
[not found] ` <CGME20221021102639epcas5p2241192d3ac873d1262372eeae948b401@epcas5p2.samsung.com>
2022-10-21 9:58 ` [PATCH 6/7] can: m_can: Add ECC functionality for message RAM Vivek Yadav
2022-10-21 15:28 ` kernel test robot
2022-10-25 8:16 ` Marc Kleine-Budde
2022-11-09 9:59 ` Vivek Yadav
[not found] ` <CGME20221021102642epcas5p24fec1e1e90632f6d9e768f7d25dc5480@epcas5p2.samsung.com>
2022-10-21 9:58 ` [PATCH 7/7] arm64: dts: fsd: Add support for error correction code " Vivek Yadav
2022-10-25 7:32 ` [PATCH 0/7] can: mcan: Add MCAN support for FSD SoC Marc Kleine-Budde
2022-11-09 8:55 ` Vivek Yadav
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=20221021095833.62406-3-vivek.2311@samsung.com \
--to=vivek.2311@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pankaj.dubey@samsung.com \
--cc=ravi.patel@samsung.com \
--cc=rcsekar@samsung.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 NNTP newsgroup(s).