From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Philippe Bergheaud <felix@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: Philippe Bergheaud <felix@linux.vnet.ibm.com>,
benh@au1.ibm.com, clombard@linux.vnet.ibm.com,
fbarrat@linux.vnet.ibm.com
Subject: Re: [PATCH v9 1/2] powerpc/powernv: Enable tunneled operations
Date: Wed, 21 Feb 2018 15:56:06 +1100 [thread overview]
Message-ID: <87sh9vuejd.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180220155111.20459-1-felix@linux.vnet.ibm.com>
Philippe Bergheaud <felix@linux.vnet.ibm.com> writes:
> diff --git a/arch/powerpc/include/asm/opal-api.h b/arch/powerpc/include/asm/opal-api.h
> index 94bd1bf2c873..07b5e2240ecc 100644
> --- a/arch/powerpc/include/asm/opal-api.h
> +++ b/arch/powerpc/include/asm/opal-api.h
> @@ -204,7 +204,9 @@
> #define OPAL_NPU_SPA_SETUP 159
> #define OPAL_NPU_SPA_CLEAR_CACHE 160
> #define OPAL_NPU_TL_SET 161
> -#define OPAL_LAST 161
> +#define OPAL_PCI_GET_PBCQ_TUNNEL_BAR 162
> +#define OPAL_PCI_SET_PBCQ_TUNNEL_BAR 163
> +#define OPAL_LAST 163
These numbers will change as other calls have gone in with those OPAL
API ids.
Feel free to send a tiny patch to skiboot reserving some though.
I should probably encourage people to do that when they start working on
new API calls.
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2018-02-21 4:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 15:51 [PATCH v9 1/2] powerpc/powernv: Enable tunneled operations Philippe Bergheaud
2018-02-20 15:51 ` [PATCH v9 2/2] cxl: read PHB indications from the device tree Philippe Bergheaud
2018-02-21 9:47 ` Frederic Barrat
2018-02-21 4:56 ` Stewart Smith [this message]
2018-02-21 9:46 ` [PATCH v9 1/2] powerpc/powernv: Enable tunneled operations Frederic Barrat
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=87sh9vuejd.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=benh@au1.ibm.com \
--cc=clombard@linux.vnet.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=felix@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).