From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
"moderated list:TPM DEVICE DRIVER"
<tpmdd-devel@lists.sourceforge.net>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [tpmdd-devel] [PATCH RFC 1/3] tpm_crb: expand struct crb_control_area to struct crb_regs
Date: Sun, 9 Oct 2016 21:26:50 -0600 [thread overview]
Message-ID: <20161010032650.GA26695@obsidianresearch.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B542F7497@hasmsx108.ger.corp.intel.com>
On Mon, Oct 10, 2016 at 12:25:11AM +0000, Winkler, Tomas wrote:
> I addition I believe it should be always on offset FED4_0xxxh by the
> Spec, so all this arithmetic is a bit of overkill.
We don't have any hard coded addresses in the drivers - that seems
very inappropriate these days..
Is that address really not discoverable via ACPI somehow?
Jason
next prev parent reply other threads:[~2016-10-10 3:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 0:15 [PATCH RFC 0/3] Locality support for the CRB driver Jarkko Sakkinen
[not found] ` <1475972112-2819-1-git-send-email-jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-10-09 0:15 ` [PATCH RFC 1/3] tpm_crb: expand struct crb_control_area to struct crb_regs Jarkko Sakkinen
[not found] ` <1475972112-2819-2-git-send-email-jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-10-09 1:42 ` Jason Gunthorpe
[not found] ` <20161009014256.GA8210-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-09 9:38 ` Jarkko Sakkinen
[not found] ` <20161009093818.GG31891-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-10-09 16:49 ` Jason Gunthorpe
[not found] ` <20161009164905.GA12551-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-09 18:06 ` Jarkko Sakkinen
2016-10-09 18:32 ` Jarkko Sakkinen
2016-10-09 18:33 ` Jarkko Sakkinen
[not found] ` <20161009183358.GB27764-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-10-09 23:07 ` Jason Gunthorpe
[not found] ` <20161009230737.GA23823-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-10 0:25 ` Winkler, Tomas
2016-10-10 3:26 ` Jason Gunthorpe [this message]
[not found] ` <5B8DA87D05A7694D9FA63FD143655C1B542F7497-Jy8z56yoSI8MvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-10-10 4:59 ` Jarkko Sakkinen
2016-10-10 4:45 ` Jarkko Sakkinen
2016-10-09 0:15 ` [PATCH RFC 2/3] tpm_crb: encapsulate crb_wait_for_reg_32 Jarkko Sakkinen
2016-10-09 0:15 ` [PATCH RFC 3/3] tpm_crb: request and relinquish locality 0 Jarkko Sakkinen
[not found] ` <1475972112-2819-4-git-send-email-jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-10-09 6:35 ` Winkler, Tomas
2016-10-09 9:25 ` [tpmdd-devel] " Jarkko Sakkinen
[not found] ` <20161009092522.GE31891-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-10-09 9:43 ` Winkler, Tomas
[not found] ` <5B8DA87D05A7694D9FA63FD143655C1B542F71A7-Jy8z56yoSI8MvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-10-09 10:47 ` Jarkko Sakkinen
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=20161010032650.GA26695@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.com \
--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 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).