On Thu, Feb 15, 2024 at 02:55:06PM +0530, Shradha Todi wrote: > > [...] > > For the error injection and counters, we already have the EDAC framework. So > > adding them in the DWC driver doesn't make sense to me. > > > > Sorry for late response, was going through the EDAC framework to understand better how we can fit RAS DES support in it. Below are some technical challenges found so far: > 1: This debugfs framework proposed [1] can run on both side of the link i.e. RC and EP as it will be a part of the link controller platform driver. Here for the EP side the assumption is that it has Linux running, which is primarily a use case for chip-to-chip communication. After your suggestion to migrate to EDAC framework we studied and here are the findings: > - If we move to EDAC framework, we need to have RAS DES as a pci_driver which will be binded based on vendor_id and device_id. Our observation is that on EP side system we are unable to bind two function driver (pci_driver), as pci_endpoint_test function driver or some other chip-to-chip function driver will already be bound. On the other hand, on RC side we observed that if we have portdrv enabled in Linux running on RC system, it gets bound to RC controller and then it does not allow EDAC pci_driver to bind. So basically we see a problem here, that we can't have two pci_driver binding to same PCI device > 2: Another point is even though we use EDAC driver framework, we may not be able to use any of EDAC framework APIs as they are mostly suitable for memory controller devices sitting on PCI BUS. We will end up using debugfs entries just via a pci_driver placed inside EDAC framework. Please wrap your replies to 80 characters. There is no need to bind the edac driver to VID:PID of the device. The edac driver can be a platform driver and you can instantiate the platform device from the DWC driver. This way, the PCI device can be assocaited with whatever driver, but still there can be a separate edac driver for handling errors. Regarding API limitation, you should ask the maintainer about the possibility of extending them. > > Please let me know if my understanding is wrong. > > > But first check with the perf driver author if they have any plans on adding the > > proposed functionality. If they do not have any plan or not working on it, then > > look into EDAC. > > > > - Mani > > > > Since we already worked and posted patches [1], [2], we will continue to work on this and based on consent from community we will adopt to most suitable framework. > We see many subsystems like ethernet, usb, gpu, cxl having debugfs files that give information about the current status of the running system and as of now based on our findings, we still feel there is no harm in having debugfs entry based support in DesignWare controller driver itself. There is no issue in exposing the debug information through debugfs, that's the sole purpose of the interface. But here, you are trying to add support for DWC RAS feature for which a dedicated framework already exists. And there will be more similar requests coming for vendor specific error protocols as well. So your investigation could benefit everyone. >From your above investigation, looks like there are some shortcomings of the EDAC framework. So let's get that clarified by writing to the EDAC maintainers (keep us in CC). If the EDAC maintainer suggests you to add support for this feature in DWC driver itself citing some reasons, then no issues with me. - Mani -- மணிவண்ணன் சதாசிவம்
