public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Pankaj Bansal <pankaj.bansal@nxp.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Varun Sethi <V.Sethi@nxp.com>, Udit Kumar <udit.kumar@nxp.com>,
	linux-efi <linux-efi@vger.kernel.org>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Uefi runtime property in device tree
Date: Wed, 26 Dec 2018 10:15:26 +0000	[thread overview]
Message-ID: <HE1PR0402MB33233B2625F8D7EFF08C4994F1B50@HE1PR0402MB3323.eurprd04.prod.outlook.com> (raw)

Hello Ard et al.

I have a query regarding the device tree usage in UEFI.
In our UEFI implementation for NXP SOCs, we are using device tree to detect Non discoverable platform devices.
Based on the device detected in device tree, a device instance is created and the device's driver binds to that device's handle (a DXE driver or an UEFI driver).
if the device were to be used for runtime service, then we need to allocate the memory for that device instance from runtime pool and set its virtual address using EfiConvertPointer.
To facilitate this, I wish to add an optional property to the device node "uefi-runtime".
If this property is present in device tree the UEFI firmware will allocate the data from runtime pool for this device.
Also firmware will disable/delete the node in device tree before passing onto OS, so that OS doesn't use the device.

I wish to know your thoughts on this. If this doesn't seem the right way, I am happy to hear your suggestions.

Thanks & Regards,
Pankaj Bansal




             reply	other threads:[~2018-12-26 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-26 10:15 Pankaj Bansal [this message]
2018-12-26 10:17 ` Uefi runtime property in device tree Pankaj Bansal
2018-12-26 13:46 ` Ard Biesheuvel
2018-12-27  9:53   ` Pankaj Bansal
2018-12-27  9:58     ` Ard Biesheuvel

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-list 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=HE1PR0402MB33233B2625F8D7EFF08C4994F1B50@HE1PR0402MB3323.eurprd04.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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