From: Robin Murphy <robin.murphy@arm.com>
To: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
iommu@lists.linux-foundation.org
Cc: Will.Deacon@arm.com, lorenzo.pieralisi@arm.com,
hanjun.guo@linaro.org, sudeep.holla@arm.com, lv.zheng@intel.com,
joro@8bytes.org, rjw@rjwysocki.net, lenb@kernel.org,
jnair@caviumnetworks.com, gpkulkarni@gmail.com
Subject: Re: [PATCH v3 1/2] acpica: iort: Update SMMUv3 header for proximity domain mapping
Date: Mon, 19 Jun 2017 18:54:52 +0100 [thread overview]
Message-ID: <0d0d6cb6-7674-5751-d780-af5114ddd569@arm.com> (raw)
In-Reply-To: <1496897059-8272-2-git-send-email-ganapatrao.kulkarni@cavium.com>
On 08/06/17 05:44, Ganapatrao Kulkarni wrote:
> ARM IORT specification (rev. C) has added two new fields to define
> proximity domain for the SMMUv3 node in the IORT table.
>
> Proximity Domain Valid:
> Set to 1 if the value provided in the Proximity Domain field is
> valid. Set to 0 otherwise.
>
> Proximity domain:
> If the Proximity Domain Valid flag is set to 1, this entry
> provides the proximity domain to which this SMMU
> instance belongs.
>
> Update header file to reflect this.
>
> Signed-off-by: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
> ---
> include/acpi/actbl2.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/include/acpi/actbl2.h b/include/acpi/actbl2.h
> index 4b306a6..389e91f 100644
> --- a/include/acpi/actbl2.h
> +++ b/include/acpi/actbl2.h
> @@ -805,6 +805,9 @@ struct acpi_iort_smmu_v3 {
> u32 pri_gsiv;
> u32 gerr_gsiv;
> u32 sync_gsiv;
> + u8 pxm;
> + u8 reserved1;
> + u16 reserved2;
Why add the padding if you're not also adding the following field that
it aligns? (side note: could it not just be a u8[3]?)
If the actual structure definition is changing, do there not need to be
corresponding IASL changes too?
> };
>
> /* Values for Model field above */
> @@ -817,6 +820,7 @@ struct acpi_iort_smmu_v3 {
>
> #define ACPI_IORT_SMMU_V3_COHACC_OVERRIDE (1)
> #define ACPI_IORT_SMMU_V3_HTTU_OVERRIDE (1<<1)
> +#define ACPI_IORT_SMMU_V3_PXM_VALID (1<<3)
Maybe it's just me, but "PXM" seems incredibly cryptic.
Robin.
>
> /*******************************************************************************
> *
>
next prev parent reply other threads:[~2017-06-19 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 4:44 [PATCH v3 0/2] acpi/iort, numa: Add numa node mapping for smmuv3 devices Ganapatrao Kulkarni
2017-06-08 4:44 ` [PATCH v3 1/2] acpica: iort: Update SMMUv3 header for proximity domain mapping Ganapatrao Kulkarni
2017-06-19 17:54 ` Robin Murphy [this message]
2017-06-20 2:27 ` Ganapatrao Kulkarni
2017-06-08 4:44 ` [PATCH v3 2/2] acpi/iort: numa: Add numa node mapping for smmuv3 devices Ganapatrao Kulkarni
2017-06-15 13:46 ` Lorenzo Pieralisi
2017-06-28 17:47 ` Robert Richter
2017-07-04 10:07 ` Lorenzo Pieralisi
2017-07-06 11:20 ` Robert Richter
2017-07-22 3:23 ` Hanjun Guo
2017-07-22 13:05 ` Ganapatrao Kulkarni
2017-06-08 9:04 ` [PATCH v3 0/2] acpi/iort, " John Garry
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=0d0d6cb6-7674-5751-d780-af5114ddd569@arm.com \
--to=robin.murphy@arm.com \
--cc=Will.Deacon@arm.com \
--cc=ganapatrao.kulkarni@cavium.com \
--cc=gpkulkarni@gmail.com \
--cc=hanjun.guo@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jnair@caviumnetworks.com \
--cc=joro@8bytes.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lv.zheng@intel.com \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).