Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754061AbcJKSVN (ORCPT ); Tue, 11 Oct 2016 14:21:13 -0400 Received: from mga03.intel.com ([134.134.136.65]:59245 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753645AbcJKSVL (ORCPT ); Tue, 11 Oct 2016 14:21:11 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,330,1473145200"; d="scan'208";a="771442300" Date: Tue, 11 Oct 2016 21:21:00 +0300 From: Jarkko Sakkinen To: Jason Gunthorpe , g@intel.com Cc: Peter Huewe , Marcel Selhorst , "moderated list:TPM DEVICE DRIVER" , open list Subject: Re: [PATCH 1/3] tpm_crb: map locality registers Message-ID: <20161011182100.GC6900@intel.com> References: <1476177787-15003-1-git-send-email-jarkko.sakkinen@linux.intel.com> <1476177787-15003-3-git-send-email-jarkko.sakkinen@linux.intel.com> <20161011170143.GC6881@obsidianresearch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161011170143.GC6881@obsidianresearch.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1960 Lines: 55 On Tue, Oct 11, 2016 at 11:01:43AM -0600, Jason Gunthorpe wrote: > 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. So... do you suggest to squash with request/reliquish locality stuff? Just checking because this is 1/3 :) > > - 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? Yes. The old hardware triggered SMM to do a DMA transfer (those that so called ACPI start). As a workaround for some of the hardware the driver always sets the CRB start flag also in the control area. That's why I also propose that we replace them with a single flag. > 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 As a sanity check this would probably make sense. /Jarkko