From: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
To: Ian Munsie <imunsie@au1.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>, mikey <mikey@neuling.org>,
linuxppc-dev@lists.ozlabs.org,
Frederic Barrat <frederic.barrat@fr.ibm.com>,
Huy Nguyen <huyn@mellanox.com>
Subject: Re: [PATCH 2/2] cxl: Workaround XSL bug that does not clear the RA bit after a reset
Date: Thu, 30 Jun 2016 13:05:30 +0200 [thread overview]
Message-ID: <5774FCFA.4030009@linux.vnet.ibm.com> (raw)
In-Reply-To: <1467226286-28547-2-git-send-email-imunsie@au.ibm.com>
Le 29/06/2016 20:51, Ian Munsie a écrit :
> From: Ian Munsie <imunsie@au1.ibm.com>
>
> An issue was noted in our debug logs where the XSL would leave the RA
> bit asserted after an AFU reset operation, which would effectively
> prevent further AFU reset operations from working.
>
> Workaround the issue by clearing the RA bit with an MMIO write if it is
> still asserted after any AFU control operation.
>
> Signed-off-by: Ian Munsie <imunsie@au1.ibm.com>
OK, should be safe and valid even on non-xsl hardware.
Reviewed-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
Fred
next prev parent reply other threads:[~2016-06-30 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 18:51 [PATCH 1/2] cxl: Fix bug where AFU disable operation had no effect Ian Munsie
2016-06-29 18:51 ` [PATCH 2/2] cxl: Workaround XSL bug that does not clear the RA bit after a reset Ian Munsie
2016-06-30 11:05 ` Frederic Barrat [this message]
2016-07-11 10:19 ` [2/2] " Michael Ellerman
2016-06-30 14:19 ` [PATCH 1/2] cxl: Fix bug where AFU disable operation had no effect Frederic Barrat
2016-06-30 15:32 ` Ian Munsie
2016-06-30 15:50 ` Frederic Barrat
2016-06-30 16:45 ` Ian Munsie
2016-06-30 16:50 ` [PATCH v2] " Ian Munsie
2016-07-01 8:09 ` Frederic Barrat
2016-07-11 10:19 ` [v2] " 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=5774FCFA.4030009@linux.vnet.ibm.com \
--to=fbarrat@linux.vnet.ibm.com \
--cc=frederic.barrat@fr.ibm.com \
--cc=huyn@mellanox.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
/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.