From: Udit Kumar <udit.kumar@nxp.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Varun Sethi <V.Sethi@nxp.com>
Subject: [RFC] ACPI table HID/CID allocation
Date: Tue, 21 Nov 2017 09:19:38 +0000 [thread overview]
Message-ID: <AM6PR0402MB333421DBCB717031E741428B91230@AM6PR0402MB3334.eurprd04.prod.outlook.com> (raw)
Hi,
I am enabling ACPI on NXP platform , In order to do minimal changes in Linux driver for device-driver binding.
I want to use PRP0001 device as CID and HID as actual (NXP allocated HID).
So that Linux can bind with PRP0001 and compatible field, where as other OS (Window etc) can rely on HID.
Below is sample, ACPI table for SPI controller and its slave device.
Hope this approach is ok ?
Thanks
Udit
Scope(_SB)
{
Device(SPI0) {
Name(_HID, "NXP0001")
Name(_CID, "PRP0001")
Name(_CRS, ResourceTemplate() {
}) // end of _CRS for i2c0 device
Name (_DSD, Package () {
ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
Package () {
Package() {"compatible", " fsl,ls2085a-dspi"},
}
}) // end of DSD SPI device
Device (EEP0) {
Name(_HID, " NXP0002") //HID can be discussed with flash vendor
Name(_CID, "PRP0001") // m25p80 flash
Name(_CRS, ResourceTemplate()
{
SPISerialBus(....)
}) // ResourceTemplate()
Name (_DSD, Package () {
ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
Package () {
Package() {"compatible", "st,m25p80"},
}
} // End of e2prom device
} // end of SPI device
}
next reply other threads:[~2017-11-21 9:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 9:19 Udit Kumar [this message]
2017-11-21 9:38 ` [RFC] ACPI table HID/CID allocation Ard Biesheuvel
2017-11-21 9:59 ` Udit Kumar
2017-11-21 10:13 ` Ard Biesheuvel
2017-11-21 11:32 ` Udit Kumar
2017-11-21 12:29 ` Ard Biesheuvel
2017-11-21 13:24 ` Udit Kumar
2017-11-21 14:03 ` Ard Biesheuvel
2017-11-21 18:10 ` Udit Kumar
2017-11-22 11:30 ` Daniel Thompson
2017-11-22 13:39 ` Udit Kumar
2017-11-22 17:34 ` Andrew Fish
2017-11-25 12:40 ` Udit Kumar
2017-11-22 19:39 ` Ard Biesheuvel
2017-11-22 20:11 ` Daniel Thompson
2017-11-25 12:56 ` Udit Kumar
2017-11-25 19:41 ` Andrew Fish
2017-11-26 8:35 ` Udit Kumar
2017-11-27 12:13 ` Daniel Thompson
2017-11-27 13:31 ` Udit Kumar
2017-11-25 12:47 ` Udit Kumar
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=AM6PR0402MB333421DBCB717031E741428B91230@AM6PR0402MB3334.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