From: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
To: Ian Munsie <imunsie@au1.ibm.com>
Cc: mikey <mikey@neuling.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Huy Nguyen <huyn@mellanox.com>,
Frederic Barrat <frederic.barrat@fr.ibm.com>
Subject: Re: [PATCH 1/2] cxl: Fix bug where AFU disable operation had no effect
Date: Thu, 30 Jun 2016 17:50:00 +0200 [thread overview]
Message-ID: <57753FA8.1080306@linux.vnet.ibm.com> (raw)
In-Reply-To: <1467298239-sup-4306@x230.ozlabs.ibm.com>
Le 30/06/2016 17:32, Ian Munsie a écrit :
>> For dedicated mode, the CAIA recommends an explicit reset of the AFU
>> >(section 2.1.1).
> True, I had forgotten that procedure was added to the document before it
> was made public - I'll update the comment and resend.
>
Actually, my point was that for dedicated mode, we shouldn't have the
"if" and always reset. It's only for dedicated mode, so it wouldn't
impact cx4 and we would stay CAIA-compliant. If one day, there's a xsl
with a dedicated mode AFU, they are expected to follow the spec.
Fred
next prev parent reply other threads:[~2016-06-30 15:50 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
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 [this message]
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=57753FA8.1080306@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 \
/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.