public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Wolfram Sang <wsa@kernel.org>,
	Seth Heasley <seth.heasley@intel.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: ismt: Provide a DMA buffer for Interrupt Cause Logging
Date: Wed, 27 Apr 2022 18:19:18 +0300	[thread overview]
Message-ID: <Ymle9oNOCFM83KSS@smile.fi.intel.com> (raw)
In-Reply-To: <20220427101910.47438-1-mika.westerberg@linux.intel.com>

On Wed, Apr 27, 2022 at 01:19:10PM +0300, Mika Westerberg wrote:
> Before sending a MSI the hardware writes information pertinent to the
> interrupt cause to a memory location pointed by SMTICL register. This
> memory holds three double words where the least significant bit tells
> whether the interrupt cause of master/target/error is valid. The driver
> does not use this but we need to set it up because otherwise it will
> perform DMA write to the default address (0) and this will cause an
> IOMMU fault such as below:
> 
>   DMAR: DRHD: handling fault status reg 2
>   DMAR: [DMA Write] Request device [00:12.0] PASID ffffffff fault addr 0
>         [fault reason 05] PTE Write access is not set
> 
> To prevent this from happening, provide a proper DMA buffer for this
> that then gets mapped by the IOMMU accordingly.

Reviewed-by: From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> ---
>  drivers/i2c/busses/i2c-ismt.c | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/drivers/i2c/busses/i2c-ismt.c b/drivers/i2c/busses/i2c-ismt.c
> index c0364314877e..c16157ee8c52 100644
> --- a/drivers/i2c/busses/i2c-ismt.c
> +++ b/drivers/i2c/busses/i2c-ismt.c
> @@ -82,6 +82,7 @@
>  
>  #define ISMT_DESC_ENTRIES	2	/* number of descriptor entries */
>  #define ISMT_MAX_RETRIES	3	/* number of SMBus retries to attempt */
> +#define ISMT_LOG_ENTRIES	3	/* number of interrupt cause log entries */
>  
>  /* Hardware Descriptor Constants - Control Field */
>  #define ISMT_DESC_CWRL	0x01	/* Command/Write Length */
> @@ -175,6 +176,8 @@ struct ismt_priv {
>  	u8 head;				/* ring buffer head pointer */
>  	struct completion cmp;			/* interrupt completion */
>  	u8 buffer[I2C_SMBUS_BLOCK_MAX + 16];	/* temp R/W data buffer */
> +	dma_addr_t log_dma;
> +	u32 *log;
>  };
>  
>  static const struct pci_device_id ismt_ids[] = {
> @@ -411,6 +414,9 @@ static int ismt_access(struct i2c_adapter *adap, u16 addr,
>  	memset(desc, 0, sizeof(struct ismt_desc));
>  	desc->tgtaddr_rw = ISMT_DESC_ADDR_RW(addr, read_write);
>  
> +	/* Always clear the log entries */
> +	memset(priv->log, 0, ISMT_LOG_ENTRIES * sizeof(u32));
> +
>  	/* Initialize common control bits */
>  	if (likely(pci_dev_msi_enabled(priv->pci_dev)))
>  		desc->control = ISMT_DESC_INT | ISMT_DESC_FAIR;
> @@ -708,6 +714,8 @@ static void ismt_hw_init(struct ismt_priv *priv)
>  	/* initialize the Master Descriptor Base Address (MDBA) */
>  	writeq(priv->io_rng_dma, priv->smba + ISMT_MSTR_MDBA);
>  
> +	writeq(priv->log_dma, priv->smba + ISMT_GR_SMTICL);
> +
>  	/* initialize the Master Control Register (MCTRL) */
>  	writel(ISMT_MCTRL_MEIE, priv->smba + ISMT_MSTR_MCTRL);
>  
> @@ -795,6 +803,12 @@ static int ismt_dev_init(struct ismt_priv *priv)
>  	priv->head = 0;
>  	init_completion(&priv->cmp);
>  
> +	priv->log = dmam_alloc_coherent(&priv->pci_dev->dev,
> +					ISMT_LOG_ENTRIES * sizeof(u32),
> +					&priv->log_dma, GFP_KERNEL);
> +	if (!priv->log)
> +		return -ENOMEM;
> +
>  	return 0;
>  }
>  
> -- 
> 2.35.1
> 

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2022-04-27 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 10:19 [PATCH] i2c: ismt: Provide a DMA buffer for Interrupt Cause Logging Mika Westerberg
2022-04-27 15:19 ` Andy Shevchenko [this message]
2022-05-21 10:53 ` Wolfram Sang
2022-05-22  9:37   ` Andy Shevchenko
2022-05-23  8:51   ` Mika Westerberg

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=Ymle9oNOCFM83KSS@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=nhorman@tuxdriver.com \
    --cc=seth.heasley@intel.com \
    --cc=wsa@kernel.org \
    /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