public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Haris Okanovic <haris.okanovic@ni.com>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	tpmdd-devel@lists.sourceforge.net, harisokn@gmail.com,
	julia.cartwright@ni.com, gratian.crisan@ni.com,
	scott.hartman@ni.com, chris.graf@ni.com, brad.mouring@ni.com,
	jonathan.david@ni.com, peterhuewe@gmx.de, tpmdd@selhorst.net,
	jarkko.sakkinen@linux.intel.com, jgunthorpe@obsidianresearch.com,
	eric.gardiner@ni.com
Subject: Re: [PATCH] tpm_tis: fix stall after iowrite*()s
Date: Tue, 15 Aug 2017 08:11:07 +0200	[thread overview]
Message-ID: <1619753.FtnHesjV4E@ws-stein> (raw)
In-Reply-To: <20170814225347.30670-1-haris.okanovic@ni.com>

On Monday 14 August 2017 17:53:47, Haris Okanovic wrote:
> --- a/drivers/char/tpm/tpm_tis.c
> +++ b/drivers/char/tpm/tpm_tis.c
> @@ -52,6 +52,22 @@ static inline struct tpm_tis_tcg_phy
> *to_tpm_tis_tcg_phy(struct tpm_tis_data *da return container_of(data,
> struct tpm_tis_tcg_phy, priv);
>  }
> 
> +static inline void tpm_tis_iowrite8(u8 b, void __iomem *iobase, u32 addr)
> +{
> +	iowrite8(b, iobase + addr);
> +#ifdef CONFIG_PREEMPT_RT_FULL
> +	ioread8(iobase + TPM_ACCESS(0));
> +#endif
> +}

Maybe add some comment why an iorad8 is actually requried after each write on 
RT. Currently it is rather obvious why this additional read is necessary. But 
is this still the case in a year?

> +static inline void tpm_tis_iowrite32(u32 b, void __iomem *iobase, u32 addr)
> +{
> +	iowrite32(b, iobase + addr);
> +#ifdef CONFIG_PREEMPT_RT_FULL
> +	ioread8(iobase + TPM_ACCESS(0));
> +#endif
> +}

Same applies here. Or add a comment above both functions describing their 
purpose.

Just my 2 cents

Best regards,
Alexander

  reply	other threads:[~2017-08-15  6:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 21:56 [PATCH] [RFC] tpm_tis: tpm_tcg_flush() after iowrite*()s Haris Okanovic
2017-08-07 14:59 ` Julia Cartwright
2017-08-08 21:58   ` Jarkko Sakkinen
2017-08-14 22:53     ` Haris Okanovic
2017-08-14 22:52   ` Haris Okanovic
2017-08-14 22:53 ` [PATCH] tpm_tis: fix stall " Haris Okanovic
2017-08-15  6:11   ` Alexander Stein [this message]
2017-08-15 20:10     ` Haris Okanovic
2017-08-15 20:13 ` [PATCH v2] " Haris Okanovic
2017-08-16 21:15   ` [tpmdd-devel] " Ken Goldman
2017-08-17  5:57     ` Alexander Stein
2017-08-17 10:38     ` Sebastian Andrzej Siewior
2017-08-17 17:17       ` Jason Gunthorpe
2017-08-17 20:12         ` Haris Okanovic
2017-08-19 17:03         ` 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=1619753.FtnHesjV4E@ws-stein \
    --to=alexander.stein@systec-electronic.com \
    --cc=brad.mouring@ni.com \
    --cc=chris.graf@ni.com \
    --cc=eric.gardiner@ni.com \
    --cc=gratian.crisan@ni.com \
    --cc=haris.okanovic@ni.com \
    --cc=harisokn@gmail.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=jonathan.david@ni.com \
    --cc=julia.cartwright@ni.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=scott.hartman@ni.com \
    --cc=tpmdd-devel@lists.sourceforge.net \
    --cc=tpmdd@selhorst.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