All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Peter Huewe <peterhuewe@gmx.de>,
	Marcel Selhorst <tpmdd@selhorst.net>,
	"moderated list:TPM DEVICE DRIVER" 
	<tpmdd-devel@lists.sourceforge.net>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] tpm_crb: map locality registers
Date: Tue, 11 Oct 2016 11:01:43 -0600	[thread overview]
Message-ID: <20161011170143.GC6881@obsidianresearch.com> (raw)
In-Reply-To: <1476177787-15003-3-git-send-email-jarkko.sakkinen@linux.intel.com>

On Tue, Oct 11, 2016 at 12:23:04PM +0300, Jarkko Sakkinen wrote:
> In order to provide access to locality registers, this commits adds
> mapping of the head of the CRB registers, which are located right
> before the control area.

I think you should squash this into the prior patch, no sense in
changing all these lines twice

But looks better to me.

> -	priv->cca = crb_map_res(dev, priv, &io_res, buf->control_address,
> -				sizeof(struct crb_control_area));
> -	if (IS_ERR(priv->cca))
> -		return PTR_ERR(priv->cca);
> +	if (priv->flags & CRB_FL_CRB_START) {
> +		priv->regs_h = crb_map_res(dev, priv, &io_res, io_res.start,
> +					   sizeof(struct crb_regs_head));
> +		if (IS_ERR(priv->regs_h))
> +			return PTR_ERR(priv->regs_h);
> +	}
> +
> +	priv->regs_t = crb_map_res(dev, priv, &io_res, buf->control_address,
> +				   sizeof(struct crb_regs_tail));
> +	if (IS_ERR(priv->regs_t))
> +		return PTR_ERR(priv->regs_t);

So.. The ACPI IO region starts at the head area and continues to
include the control area, as one nice sane region - except for some
older stuff that puts the control area outside the ACPI IO region?

That makes a lot more sense..

Maybe chuck in a

   if (priv->flags & CRB_FL_CRB_START) {
      if (buf->control_address != io_res.start + sizeof(struct
          crb_regs_head))
          dev_warn(dev, FIRMWARE_BUG "Bad ACPI memory layout")

Jason

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Jarkko Sakkinen
	<jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: "moderated list:TPM DEVICE DRIVER"
	<tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	open list <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/3] tpm_crb: map locality registers
Date: Tue, 11 Oct 2016 11:01:43 -0600	[thread overview]
Message-ID: <20161011170143.GC6881@obsidianresearch.com> (raw)
In-Reply-To: <1476177787-15003-3-git-send-email-jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>

On Tue, Oct 11, 2016 at 12:23:04PM +0300, Jarkko Sakkinen wrote:
> In order to provide access to locality registers, this commits adds
> mapping of the head of the CRB registers, which are located right
> before the control area.

I think you should squash this into the prior patch, no sense in
changing all these lines twice

But looks better to me.

> -	priv->cca = crb_map_res(dev, priv, &io_res, buf->control_address,
> -				sizeof(struct crb_control_area));
> -	if (IS_ERR(priv->cca))
> -		return PTR_ERR(priv->cca);
> +	if (priv->flags & CRB_FL_CRB_START) {
> +		priv->regs_h = crb_map_res(dev, priv, &io_res, io_res.start,
> +					   sizeof(struct crb_regs_head));
> +		if (IS_ERR(priv->regs_h))
> +			return PTR_ERR(priv->regs_h);
> +	}
> +
> +	priv->regs_t = crb_map_res(dev, priv, &io_res, buf->control_address,
> +				   sizeof(struct crb_regs_tail));
> +	if (IS_ERR(priv->regs_t))
> +		return PTR_ERR(priv->regs_t);

So.. The ACPI IO region starts at the head area and continues to
include the control area, as one nice sane region - except for some
older stuff that puts the control area outside the ACPI IO region?

That makes a lot more sense..

Maybe chuck in a

   if (priv->flags & CRB_FL_CRB_START) {
      if (buf->control_address != io_res.start + sizeof(struct
          crb_regs_head))
          dev_warn(dev, FIRMWARE_BUG "Bad ACPI memory layout")

Jason

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

  parent reply	other threads:[~2016-10-11 17:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11  9:23 [PATCH 0/3] Locality support for the CRB driver Jarkko Sakkinen
2016-10-11  9:23 ` Jarkko Sakkinen
2016-10-11  9:23 ` [PATCH RFC 1/3] tpm_crb: expand struct crb_control_area to struct crb_regs Jarkko Sakkinen
2016-10-11  9:23   ` Jarkko Sakkinen
2016-10-11  9:23 ` [PATCH 1/3] tpm_crb: map locality registers Jarkko Sakkinen
2016-10-11  9:23   ` Jarkko Sakkinen
2016-10-11 11:25   ` Jarkko Sakkinen
2016-10-11 11:25     ` Jarkko Sakkinen
2016-10-11 17:01   ` Jason Gunthorpe [this message]
2016-10-11 17:01     ` Jason Gunthorpe
2016-10-11 18:21     ` Jarkko Sakkinen
2016-10-11 18:21       ` Jarkko Sakkinen
2016-10-11 18:29       ` Jason Gunthorpe
2016-10-11 18:29         ` Jason Gunthorpe
2016-10-11 19:48         ` Jarkko Sakkinen
2016-10-11 19:48           ` Jarkko Sakkinen
2016-10-11  9:23 ` [PATCH 2/3] tpm_crb: encapsulate crb_wait_for_reg_32 Jarkko Sakkinen
2016-10-11  9:23   ` Jarkko Sakkinen
2016-10-11 10:21   ` [tpmdd-devel] " Winkler, Tomas
2016-10-11 10:21     ` Winkler, Tomas
2016-10-11 11:29     ` [tpmdd-devel] " Jarkko Sakkinen
2016-10-11 11:29       ` Jarkko Sakkinen
2016-10-11  9:23 ` [PATCH 3/3] tpm_crb: request and relinquish locality 0 Jarkko Sakkinen
2016-10-11  9:23   ` 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=20161011170143.GC6881@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --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 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.