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>,
<gcnu.goud@gmail.com>
Cc: <git@amd.com>, <michal.simek@xilinx.com>,
<linux-can@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Srinivas Goud <srinivas.goud@amd.com>
Subject: [PATCH 1/3] dt-bindings: can: xilinx_can: Add ECC property ‘xlnx,has-ecc’
Date: Mon, 12 Jun 2023 17:12:55 +0530 [thread overview]
Message-ID: <1686570177-2836108-2-git-send-email-srinivas.goud@amd.com> (raw)
In-Reply-To: <1686570177-2836108-1-git-send-email-srinivas.goud@amd.com>
ECC feature added to Tx and Rx FIFO’s for Xilinx CAN Controller.
Part of this feature configuration and counter registers
added in IP for 1bit/2bit ECC errors.
Please find more details in PG096 v5.1 document.
xlnx,has-ecc is optional property and added to Xilinx CAN
Controller node if ECC block enabled in the HW.
Signed-off-by: Srinivas Goud <srinivas.goud@amd.com>
---
Documentation/devicetree/bindings/net/can/xilinx,can.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/can/xilinx,can.yaml b/Documentation/devicetree/bindings/net/can/xilinx,can.yaml
index 897d2cb..13503ae 100644
--- a/Documentation/devicetree/bindings/net/can/xilinx,can.yaml
+++ b/Documentation/devicetree/bindings/net/can/xilinx,can.yaml
@@ -46,6 +46,10 @@ properties:
$ref: /schemas/types.yaml#/definitions/uint32
description: CAN Tx mailbox buffer count (CAN FD)
+ xlnx,has-ecc:
+ $ref: /schemas/types.yaml#/definitions/flag
+ description: CAN Tx and Rx fifo ECC enable flag (AXI CAN)
+
required:
- compatible
- reg
@@ -134,6 +138,7 @@ examples:
interrupts = <GIC_SPI 59 IRQ_TYPE_EDGE_RISING>;
tx-fifo-depth = <0x40>;
rx-fifo-depth = <0x40>;
+ xlnx,has-ecc;
};
- |
--
2.1.1
next prev parent reply other threads:[~2023-06-12 11:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 11:42 [PATCH 0/3] can: xilinx_can: Add ECC feature support Srinivas Goud
2023-06-12 11:42 ` Srinivas Goud [this message]
2023-06-13 7:52 ` [PATCH 1/3] dt-bindings: can: xilinx_can: Add ECC property ‘xlnx,has-ecc’ Marc Kleine-Budde
2023-06-14 10:22 ` Goud, Srinivas
2023-06-14 11:11 ` Krzysztof Kozlowski
2023-06-16 10:13 ` Goud, Srinivas
2023-06-16 10:38 ` Krzysztof Kozlowski
2023-06-16 10:44 ` Michal Simek
2023-06-17 7:31 ` Krzysztof Kozlowski
2023-06-19 6:37 ` Michal Simek
2023-06-17 7:32 ` Krzysztof Kozlowski
2023-06-13 8:46 ` Krzysztof Kozlowski
2023-06-12 11:42 ` [PATCH 2/3] can: xilinx_can: Add ECC support Srinivas Goud
2023-06-13 11:30 ` Marc Kleine-Budde
2023-07-21 5:23 ` Goud, Srinivas
2023-07-24 8:54 ` Marc Kleine-Budde
2023-06-16 11:06 ` Marc Kleine-Budde
2023-06-12 11:42 ` [PATCH 3/3] can: xilinx_can: Add debugfs support for ECC Srinivas Goud
2023-06-13 7:51 ` Marc Kleine-Budde
2023-06-16 11:12 ` [PATCH 0/3] can: xilinx_can: Add ECC feature support Marc Kleine-Budde
2023-06-23 7:48 ` Michal Simek
2023-06-30 8: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=1686570177-2836108-2-git-send-email-srinivas.goud@amd.com \
--to=srinivas.goud@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gcnu.goud@gmail.com \
--cc=git@amd.com \
--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=pabeni@redhat.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