Re: [PATCH v4 09/10] dt-bindings: firmware: add arm,ras-cper
Ahmed Tiba <[email protected]> Tue, 19 May 2026 10:57:30 +0100
| Newsgroups | dev.linux.lists.acpica-devel,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-acpi,org.kernel.vger.linux-cxl,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-doc,org.kernel.vger.linux-edac,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 19/05/2026 10:22, Krzysztof Kozlowski wrote: > On 19/05/2026 11:02, Ahmed Tiba wrote: >> On 19/05/2026 08:04, Krzysztof Kozlowski wrote: >>> On 18/05/2026 13:57, Ahmed Tiba wrote: >>>> Describe the DeviceTree node that exposes the Arm firmware-first >>>> CPER provider and hook the file into MAINTAINERS so the >>>> binding has an owner. >>>> >>>> Signed-off-by: Ahmed Tiba <[email protected]> >>> >>> Please implement previous comments. >> >> Could you please clarify which previous DT comments you still see >> as unaddressed? >> >> My understanding was that I had addressed the earlier points on the YAML >> description formatting, the `memory-region` description text, and the >> example. If I missed a specific item beyond the one below, please point >> me to it. > > You do not need other nodes for your device in the example. I asked why > this is needed for the example, but there was no answer. Understood. I wanted the example to show the full binding context, including how the `memory-region` phandles point to the reserved memory, but I see your point. I will remove the `reserved-memory` node from the example and simplify it to only the `arm,ras-cper` device node. Best regards, Ahmed