tpmdd-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Azhar Shaikh <azhar.shaikh@intel.com>
Cc: jgunthorpe@obsidianresearch.com,
	tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH v4] tpm: Enable CLKRUN protocol for Braswell systems
Date: Sat, 10 Jun 2017 14:13:39 +0300	[thread overview]
Message-ID: <20170610111339.ggphrkwqiez35wer@intel.com> (raw)
In-Reply-To: <1496965593-187931-1-git-send-email-azhar.shaikh@intel.com>

On Thu, Jun 08, 2017 at 04:46:33PM -0700, Azhar Shaikh wrote:
> To overcome a hardware limitation on Intel Braswell systems,
> disable CLKRUN protocol during TPM transactions and re-enable
> once the transaction is completed.
> 
> Signed-off-by: Azhar Shaikh <azhar.shaikh@intel.com>
> ---
> Changes from v1:
> - Add CONFIG_X86 around disable_lpc_clk_run () and enable_lpc_clk_run() to avoid
> - build breakage on architectures which do not implement kmap_atomic_pfn()
> 
> Changes from v2:
> - Use ioremap()/iounmap() instead of kmap_atomic_pfn()/kunmap_atomic()
> - Move is_bsw() and all macros from tpm.h to tpm_tis.c file.
> - Add the is_bsw() check in disable_lpc_clk_run() and enable_lpc_clk_run()
> - instead of adding it in each read/write API.
> 
> Changes from v3:
> - Move the code under #ifdef CONFIG_X86 and create stub functions for everything else
> - Rename the functions disable_lpc_clk_run() -> tpm_platform_begin_xfer() and
> - enable_lpc_clk_run() -> tpm_platform_end_xfer()
> - Remove wmb()

The wrong parameter order in outb() is not worth of mentioning in your
opinion?

Related.

I looked again the kmap version of the patch and still cannot figure
out what could be wrong. Obviously the wrong outb() cause unexpected
behavior.

Do you have chances to grab klog from kmap version with correct outb?

/Jarkko

  reply	other threads:[~2017-06-10 11:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 19:13 [PATCH] tpm: Enable CLKRUN protocol for Braswell systems Azhar Shaikh
2017-06-01 23:56 ` kbuild test robot
2017-06-02  2:04 ` [PATCH v2] " Azhar Shaikh
     [not found]   ` <1496369044-38234-1-git-send-email-azhar.shaikh-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-06-05 13:32     ` Jarkko Sakkinen
2017-06-05 18:42       ` Shaikh, Azhar
2017-06-06 17:13         ` Jarkko Sakkinen
2017-06-07 21:23   ` [PATCH v3] " Azhar Shaikh
2017-06-07 21:44     ` Alan Cox
2017-06-08  1:11       ` Shaikh, Azhar
2017-06-08 12:38         ` Jarkko Sakkinen
2017-06-08 18:22         ` Alan Cox
2017-06-08 18:39           ` Jason Gunthorpe
2017-06-08 18:50             ` Alan Cox
2017-06-08 19:27               ` Shaikh, Azhar
2017-06-10 11:06             ` Jarkko Sakkinen
2017-06-08 19:02           ` Shaikh, Azhar
2017-06-08 23:46   ` [PATCH v4] " Azhar Shaikh
2017-06-10 11:13     ` Jarkko Sakkinen [this message]
2017-06-10 16:35       ` Shaikh, Azhar
2017-06-12  7:50         ` Jarkko Sakkinen
2017-06-14  0:51           ` Shaikh, Azhar
2017-06-14 14:46             ` Jarkko Sakkinen
2017-06-14 17:17               ` Shaikh, Azhar
2017-06-14 19:39   ` Azhar Shaikh
2017-06-18 23:52     ` Jarkko Sakkinen
     [not found]       ` <1497829956.2552.10.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-06-19  2:12         ` Shaikh, Azhar
2017-06-19  2:17   ` [PATCH v5] " Azhar Shaikh
2017-06-19 14:51     ` 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=20170610111339.ggphrkwqiez35wer@intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=azhar.shaikh@intel.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@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 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).