From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tpm_crb: Use the common ACPI definition of struct acpi_tpm2
Date: Sun, 6 Dec 2015 03:25:11 +0200 [thread overview]
Message-ID: <20151206012511.GA9367@intel.com> (raw)
In-Reply-To: <20151203170217.GB32175@obsidianresearch.com>
On Thu, Dec 03, 2015 at 10:02:17AM -0700, Jason Gunthorpe wrote:
> On Thu, Dec 03, 2015 at 10:27:53AM +0200, Jarkko Sakkinen wrote:
> > On Wed, Dec 02, 2015 at 12:19:00PM -0700, Jason Gunthorpe wrote:
> > > include/acpi/actbl2.h is the proper place for these definitions
> > > and the needed TPM2 ones have been there since
> > > commit 413d4a6defe0 ("ACPICA: Update TPM2 ACPI table")
> > >
> > > This also drops the le32_to_cpu for members of this table,
> > > consistent with other ACPI stuff.
> >
> > Why le32_to_cpu() is not needed?
>
> Why is it needed?
>
> None of the fields are marked le32 in the struct and no other ACPI
> thing I could find swaps.
>
> If swapping is needed then the struct fields must be declared as 'le'
I'm just puzzling with three things:
1. Does it do conversion to the CPU format internally if you use the
tables in a big-endian environment?
2. Isn't that code import from ACPICA? That would explains why it does
not have tagged fields.
3. Could the reason be for such conversions not widely applied in the
kernel that ACPI has been previously mostly used only in the PC/x86
ecosystem?
AFAIK ACPI exist also for ARM64 servers, which can be a big-endian
environment.
> Jason
/Jarkko
prev parent reply other threads:[~2015-12-06 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 19:19 [PATCH] tpm_crb: Use the common ACPI definition of struct acpi_tpm2 Jason Gunthorpe
2015-12-03 8:27 ` Jarkko Sakkinen
2015-12-03 17:02 ` Jason Gunthorpe
2015-12-06 1:25 ` Jarkko Sakkinen [this message]
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=20151206012511.GA9367@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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.