From: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
To: imunsie@au1.ibm.com, mikey@neuling.org,
linuxppc-dev@lists.ozlabs.org,
Frank Haverkamp <HAVERKAM@de.ibm.com>
Subject: Re: [PATCH] cxl: Increase timeout for detection of AFU mmio hang
Date: Wed, 20 Apr 2016 19:18:59 +0200 [thread overview]
Message-ID: <5717BA03.8090805@linux.vnet.ibm.com> (raw)
In-Reply-To: <1461083664-12283-1-git-send-email-fbarrat@linux.vnet.ibm.com>
Received privately:
Tested-by: Frank Haverkamp <haver@linux.vnet.ibm.com>
Le 19/04/2016 18:34, Frederic Barrat a écrit :
> PSL designers recommend a larger value for the mmio hang pulse, 256 us
> instead of 1 us. The CAIA architecture states that it needs to be
> smaller than 1/2 of the RTOS timeout set in the PHB for outbound
> non-posted transactions, which is still (easily) the case here.
>
> Signed-off-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
> ---
> Needs to be applied on top of http://patchwork.ozlabs.org/patch/604029/
>
>
> drivers/misc/cxl/pci.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/misc/cxl/pci.c b/drivers/misc/cxl/pci.c
> index 94fd3f7..0a9c15b 100644
> --- a/drivers/misc/cxl/pci.c
> +++ b/drivers/misc/cxl/pci.c
> @@ -375,8 +375,10 @@ static int init_implementation_adapter_regs(struct cxl *adapter, struct pci_dev
> return -ENODEV;
> }
>
> + psl_dsnctl = 0x0000900000000000ULL; /* pteupd ttype, scdone */
> + psl_dsnctl |= (0x2ULL << (63-38)); /* MMIO hang pulse: 256 us */
> /* Tell PSL where to route data to */
> - psl_dsnctl = 0x0000900002000000ULL | (chipid << (63-5));
> + psl_dsnctl |= (chipid << (63-5));
> psl_dsnctl |= (capp_unit_id << (63-13));
>
> cxl_p1_write(adapter, CXL_PSL_DSNDCTL, psl_dsnctl);
>
next prev parent reply other threads:[~2016-04-20 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 16:34 [PATCH] cxl: Increase timeout for detection of AFU mmio hang Frederic Barrat
2016-04-20 1:34 ` Ian Munsie
2016-04-20 17:18 ` Frederic Barrat [this message]
2016-04-20 17:39 ` Manoj Kumar
2016-04-22 12:12 ` Michael Ellerman
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=5717BA03.8090805@linux.vnet.ibm.com \
--to=fbarrat@linux.vnet.ibm.com \
--cc=HAVERKAM@de.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.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 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.