linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: nfont@linux.vnet.ibm.com, Michael Bringmann <mwb@linux.vnet.ibm.com>
Subject: [PATCH V2 4/4] powerpc: Enable support for ibm,drc-info devtree property
Date: Thu, 27 Jul 2017 11:10:37 -0500	[thread overview]
Message-ID: <21fa3cc3-7f56-61fa-38f8-6259543644ac@linux.vnet.ibm.com> (raw)
In-Reply-To: <e884f428-c76d-112a-aa2f-f57a94de55fb@linux.vnet.ibm.com>


prom_init.c: Enable support for new DRC device tree property
"ibm,drc-info" in initial handshake between the Linux kernel and
the front end processor.

Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
---
 arch/powerpc/kernel/prom_init.c |    1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/powerpc/kernel/prom_init.c b/arch/powerpc/kernel/prom_init.c
index 613f79f..1fd07aa 100644
--- a/arch/powerpc/kernel/prom_init.c
+++ b/arch/powerpc/kernel/prom_init.c
@@ -872,6 +872,7 @@ struct ibm_arch_vec __cacheline_aligned ibm_architecture_vec = {
 		.mmu = 0,
 		.hash_ext = 0,
 		.radix_ext = 0,
+		.byte22 = OV5_FEAT(OV5_DRC_INFO),
 	},
 
 	/* option vector 6: IBM PAPR hints */

      parent reply	other threads:[~2017-07-27 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 16:09 [PATCH V2 0/4] powerpc/devtree: Add support for 'ibm,drc-info' property Michael Bringmann
2017-07-27 16:09 ` [PATCH V2 1/4] powerpc/firmware: Add definitions for new drc-info firmware feature Michael Bringmann
2017-07-27 16:10 ` [PATCH 2/4] pseries/drc-info: Search DRC properties for CPU indexes Michael Bringmann
2017-07-27 18:25   ` Nathan Fontenot
2017-07-27 16:10 ` [PATCH V2 3/4] hotplug/drc-info: Add code to search ibm,drc-info property Michael Bringmann
2017-07-27 16:10 ` Michael Bringmann [this message]

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=21fa3cc3-7f56-61fa-38f8-6259543644ac@linux.vnet.ibm.com \
    --to=mwb@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nfont@linux.vnet.ibm.com \
    /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).