From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Datta, Shubhrajyoti" <shubhrajyoti.datta@amd.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"git (AMD-Xilinx)" <git@amd.com>,
"robh@kernel.org" <robh@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"rric@kernel.org" <rric@kernel.org>
Subject: Re: [PATCH 1/3] dt-bindings: memory-controllers: Add support for Versal NET EDAC
Date: Tue, 26 Nov 2024 08:07:26 +0100 [thread overview]
Message-ID: <fab9ebcd-535c-49c0-b356-ca6a4886049b@kernel.org> (raw)
In-Reply-To: <SA1PR12MB89479EFB910D009F2F3A7641812F2@SA1PR12MB8947.namprd12.prod.outlook.com>
On 26/11/2024 07:57, Datta, Shubhrajyoti wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
What is this? Why would we bother? How does it affect me?
Please remove all corporate boilerplate.
...
>>> +
>>> +required:
>>> + - compatible
>>
>> Eh, no resources? How do you talk with the hardware? This looks way too Linuxy...
>
> The address space is secure, making it inaccessible to Linux. In this setup, the secure firmware (NMC)
> communicates the necessary information to Linux through RPMsg.
Don't you need to acquire a reference to the rpmsg interface? Don't you
need to encode the device dependency? All this is achieved with phandles
and proper driver support.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-11-26 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 10:06 [PATCH 0/3] EDAC: Versal NET: Add support for error notification Shubhrajyoti Datta
2024-11-22 10:06 ` [PATCH 1/3] dt-bindings: memory-controllers: Add support for Versal NET EDAC Shubhrajyoti Datta
2024-11-23 16:44 ` Krzysztof Kozlowski
2024-11-26 6:57 ` Datta, Shubhrajyoti
2024-11-26 7:07 ` Krzysztof Kozlowski [this message]
2024-12-23 9:58 ` Shubhrajyoti Datta
2024-12-23 14:02 ` Krzysztof Kozlowski
2024-11-22 10:06 ` [PATCH 2/3] cdx: add DDRMC commands Shubhrajyoti Datta
2024-11-22 10:06 ` [PATCH 3/3] EDAC: Versal NET: Add support for error notification Shubhrajyoti Datta
2024-11-23 16:49 ` Krzysztof Kozlowski
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=fab9ebcd-535c-49c0-b356-ca6a4886049b@kernel.org \
--to=krzk@kernel.org \
--cc=bp@alien8.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.