From: Sudeep Holla <sudeep.holla@arm.com>
To: "Schmauss, Erik" <erik.schmauss@intel.com>
Cc: Udit Kumar <udit.kumar@nxp.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
"lenb@kernel.org" <lenb@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: Help on named object in kernel
Date: Wed, 12 Jun 2019 18:00:59 +0100 [thread overview]
Message-ID: <20190612170059.GA30299@e107155-lin> (raw)
In-Reply-To: <CF6A88132359CE47947DB4C6E1709ED53C5E95B1@ORSMSX122.amr.corp.intel.com>
On Wed, Jun 12, 2019 at 04:37:09PM +0000, Schmauss, Erik wrote:
>
>
> > -----Original Message-----
> > From: linux-acpi-owner@vger.kernel.org [mailto:linux-acpi-
> > owner@vger.kernel.org] On Behalf Of Udit Kumar
> > Sent: Wednesday, June 12, 2019 4:48 AM
> > To: ACPI Devel Maling List <linux-acpi@vger.kernel.org>
> > Cc: lenb@kernel.org; Rafael J. Wysocki <rafael@kernel.org>
> > Subject: Help on named object in kernel
> >
> > Dear ACPI experts,
> > I need your help on defining named objected in ACPI under _CRS.
> > In my firmware, I have defined two addresses for my device using
> > Memory32Fixed and QwordMemory under _CRS.
> > These two addresses are 32-bit and 64-bit long respectively.
> > For Memory32Fixed, I gave DescriptorName name as REG0 and for
> > QwordMemory I gave DescriptorName as SATA.
>
> Could you give us the ASL for the code snippet that you're talking about?
>
IIUC, something like below(a very rough example based on the description
above):
Name (_CRS, ResourceTemplate (){
QwordMemory (
ResourceConsumer, PosDecode, MinFixed, MaxFixed, NonCacheable,
ReadWrite, 0x0, 0x700100520, 0x700100523, 0x0, 4, , , "SATA",)
Memory32Fixed(ReadWrite, 0x3200000, 0x10000, "REG0")
}
Basically 2 or more entries of Memory/Address Space Resource Descriptor
which can be identified in OSPM by DescriptorName. IOW if a device has
2 sets of registers/memory/address space associated with it, instead of
relying on the order of declaration, identify them by the descriptor
name provided in ASL namespace.
--
Regards,
Sudeep
next prev parent reply other threads:[~2019-06-12 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 11:48 Help on named object in kernel Udit Kumar
2019-06-12 16:37 ` Schmauss, Erik
2019-06-12 17:00 ` [EXT] " Udit Kumar
2019-06-12 17:00 ` Sudeep Holla [this message]
2019-06-13 1:20 ` [EXT] " Udit Kumar
2019-06-13 17:08 ` Sudeep Holla
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=20190612170059.GA30299@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=erik.schmauss@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=udit.kumar@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox