All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Michael Bringmann <mwb@linux.vnet.ibm.com>, nfont@linux.vnet.ibm.com
Subject: Resend: [PATCH V5 4/4] powerpc: Enable support for ibm,drc-info devtree property
Date: Tue, 28 Nov 2017 17:07:54 -0600	[thread overview]
Message-ID: <22ab2888-fa59-9a5b-d9f0-144bdc80c26e@linux.vnet.ibm.com> (raw)
In-Reply-To: <7f95fe4c-fcf5-9263-5fe5-0ad140cbc078@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 02190e9..f962908 100644
--- a/arch/powerpc/kernel/prom_init.c
+++ b/arch/powerpc/kernel/prom_init.c
@@ -873,6 +873,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-11-28 23:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7f95fe4c-fcf5-9263-5fe5-0ad140cbc078@linux.vnet.ibm.com>
2017-11-28 23:07 ` Resend: [PATCH V5 1/4] powerpc/firmware: Add definitions for new drc-info firmware feature Michael Bringmann
2017-11-28 23:07 ` Resend: [PATCH V5 2/4] pseries/drc-info: Search DRC properties for CPU indexes Michael Bringmann
2017-11-30 19:28   ` Nathan Fontenot
2017-12-01 21:53     ` Michael Bringmann
2017-12-04 19:45     ` Michael Bringmann
2017-11-28 23:07 ` Resend: [PATCH V5 3/4] hotplug/drc-info: Add code to search ibm,drc-info property Michael Bringmann
2017-11-30 19:51   ` Nathan Fontenot
2017-12-01 21:53     ` Michael Bringmann
2017-12-04 19:47     ` Michael Bringmann
2017-11-28 23:07 ` 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=22ab2888-fa59-9a5b-d9f0-144bdc80c26e@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 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.