public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-edac@vger.kernel.org
Cc: git@amd.com, Krzysztof Kozlowski <krzk@kernel.org>,
	Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@intel.com>,
	James Morse <james.morse@arm.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Robert Richter <rric@kernel.org>,
	Nipun Gupta <nipun.gupta@amd.com>,
	Nikhil Agarwal <nikhil.agarwal@amd.com>
Subject: Re: [PATCH v7 0/5] EDAC/Versal NET: Add support for error notification
Date: Fri, 30 May 2025 16:12:33 +0200	[thread overview]
Message-ID: <73aac6dc-6826-4558-a612-c571577a2e1d@amd.com> (raw)
In-Reply-To: <20250529070017.7288-1-shubhrajyoti.datta@amd.com>



On 5/29/25 09:00, Shubhrajyoti Datta wrote:
> Adds support for the error notification for the Versal NET EDAC driver.
> The driver receives error events via RPMsg instead of directly accessing
> hardware registers. The NMC((Network management controller), which has
> secure access to DDRMC registers, gathers the necessary information and
> transmits it through RPMsg.
> 
> During probe, the driver registers with RPMsg and retrieves DDR
> configuration by scheduling a work item from the NMC.
> Once this is completed, it registers the EDAC controller.
> When an error occurs, the NMC sends an RPMsg, notifying the driver.
> The EDAC driver handles error reporting for all events.
> Also we register the EDAC once and it reports the errors for all the
> events including the 8 DDRMC controllers. So while registering we give
> the particulars of the 1st controller.
> 
> Currently 20 errors has been tested.
> 
> 
> Changes in v7:
> - add a minimal header instead moving them
> - Add the kernel doc description
> - Add the prototype from first patch to export patch
> - Add the reviewed by tag
> - Update the header paths
> - merge edac_cdx_pcol.h
> 
> Changes in v6:
>   - Patch added
> - Update commit description
> - Update the commit message.
> - update to the chip name as xlnx,versal-net
> - Correct indentation
> - Update to xlnx,versal-net-ddrmc5
> - Update the kconfig message
> - Make the messages uniform
> - Add some more supported events
> - rename regval to reglo
> - combine/ reformat functions
> - remove trailing comments
> - Remove unneeded comments
> - make the amd_mcdi function void
> - rename versalnet_rpmsg_edac to versalnet_edac
> - Remove the column bit and use them directly
> - Update the comments
> - Update the mod_name to versalnet_edac
> - remove the global priv col and rows
> - rename edac_priv to mc_priv
> - Update the comment description for dwidth
> - Remove error_id enum
> - rename the variable par to parity
> - make get_ddr_config void
> - Fix memory leak of the mcdi structure
> - Update the spelling
> - Remove the workqueue
> 
> Changes in v5:
> - Update the binding
> - Update the compatible
> - Update the handle_error documentation
> 
> Changes in v4:
> - Update the compatible
> - align the example
> - Enhance the description for rproc
> - Update the compatible
> 
> Changes in v3:
> - make remove void
> 
> Changes in v2:
> - Export the symbols for module compilation
> - New patch addition
> - rename EDAC to memory controller
> - update the compatible name
> - Add remote proc handle
> - Read the data width from the registers
> - Remove the dwidth, rank and channel number the same is
> read from the RpMsg.
> - remove reset
> - Add the remote proc requests
> - remove probe_once
> - reorder the rpmsg registration
> - the data width , rank and number of channel is read from message.
> 
> Shubhrajyoti Datta (5):
>    cdx: add the headers to include/linux
>    cdx: Export Symbols for MCDI RPC and Initialization
>    ras: Export log_non_standard_event for External Usage
>    dt-bindings: memory-controllers: Add support for Versal NET EDAC
>    EDAC/VersalNET: Add support for error notification
> 
>   .../xlnx,versal-net-ddrmc5.yaml               |   41 +
>   drivers/cdx/controller/mcdi.c                 |   29 +
>   drivers/edac/Kconfig                          |   11 +
>   drivers/edac/Makefile                         |    1 +
>   drivers/edac/versalnet_edac.c                 | 1108 +++++++++++++++++
>   drivers/ras/ras.c                             |    1 +
>   include/linux/cdx/bitfield.h                  |   78 ++
>   include/linux/cdx/edac_cdx_pcol.h             |   28 +
>   include/linux/cdx/mcdi.h                      |  198 +++
>   9 files changed, 1495 insertions(+)
>   create mode 100644 Documentation/devicetree/bindings/memory-controllers/xlnx,versal-net-ddrmc5.yaml
>   create mode 100644 drivers/edac/versalnet_edac.c
>   create mode 100644 include/linux/cdx/bitfield.h
>   create mode 100644 include/linux/cdx/edac_cdx_pcol.h
>   create mode 100644 include/linux/cdx/mcdi.h
> 

Acked-by: Michal Simek <michal.simek@amd.com>

Thanks,
Michal



      parent reply	other threads:[~2025-05-30 14:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29  7:00 [PATCH v7 0/5] EDAC/Versal NET: Add support for error notification Shubhrajyoti Datta
2025-05-29  7:00 ` [PATCH v7 1/5] cdx: add the headers to include/linux Shubhrajyoti Datta
2025-06-13 19:59   ` Yazen Ghannam
2025-05-29  7:00 ` [PATCH v7 2/5] cdx: Export Symbols for MCDI RPC and Initialization Shubhrajyoti Datta
2025-06-13 20:10   ` Yazen Ghannam
2025-06-16 12:20     ` Datta, Shubhrajyoti
2025-06-20 11:03       ` Datta, Shubhrajyoti
2025-07-02 10:27         ` Borislav Petkov
2025-05-29  7:00 ` [PATCH v7 3/5] ras: Export log_non_standard_event for External Usage Shubhrajyoti Datta
2025-05-29  7:00 ` [PATCH v7 4/5] dt-bindings: memory-controllers: Add support for Versal NET EDAC Shubhrajyoti Datta
2025-05-29  7:00 ` [PATCH v7 5/5] EDAC/VersalNET: Add support for error notification Shubhrajyoti Datta
2025-07-03 17:31   ` Borislav Petkov
2025-07-21  4:08     ` Datta, Shubhrajyoti
2025-05-30 14:12 ` Michal Simek [this message]

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=73aac6dc-6826-4558-a612-c571577a2e1d@amd.com \
    --to=michal.simek@amd.com \
    --cc=bp@alien8.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=git@amd.com \
    --cc=james.morse@arm.com \
    --cc=krzk@kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nikhil.agarwal@amd.com \
    --cc=nipun.gupta@amd.com \
    --cc=robh@kernel.org \
    --cc=rric@kernel.org \
    --cc=shubhrajyoti.datta@amd.com \
    --cc=tony.luck@intel.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