All of lore.kernel.org
 help / color / mirror / Atom feed
From: chunrong.guo@nxp.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] tune-ppce500v1: Add a tune file for PowerPC e500v1 cores
Date: Thu, 14 Jun 2018 17:25:01 +0800	[thread overview]
Message-ID: <1528968301-3209-1-git-send-email-chunrong.guo@nxp.com> (raw)

From: Chunrong Guo <chunrong.guo@nxp.com>

Signed-off-by: Chunrong Guo <chunrong.guo@nxp.com>
---
 meta/conf/machine/include/tune-ppce500v1.inc | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
 create mode 100644 meta/conf/machine/include/tune-ppce500v1.inc

diff --git a/meta/conf/machine/include/tune-ppce500v1.inc b/meta/conf/machine/include/tune-ppce500v1.inc
new file mode 100644
index 0000000..509c81b
--- /dev/null
+++ b/meta/conf/machine/include/tune-ppce500v1.inc
@@ -0,0 +1,20 @@
+DEFAULTTUNE ?= "ppce500v1"
+
+require conf/machine/include/powerpc/arch-powerpc.inc
+
+TUNEVALID[ppce500v1] = "Enable ppce500v1 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'ppce500v1', ' -mcpu=8540', '', d)}"
+
+TUNEVALID[spe] = "Enable SPE ABI extensions"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', [ 'ppce500v1', 'spe' ], ' -mabi=spe -mspe -mfloat-gprs=double', '', d)}"
+TARGET_FPU .= "${@bb.utils.contains('TUNE_FEATURES', [ 'ppce500v1' , 'spe' ], 'ppc-efd', '', d)}"
+
+# spe is defined potentially in two places, so we want to be sure it will
+# only write spe once to the ABIEXTENSIONS field.
+SPEABIEXTENSION = "${@bb.utils.filter('TUNE_FEATURES', 'spe', d)}"
+ABIEXTENSION .= "${SPEABIEXTENSION}"
+
+AVAILTUNES += "ppce500v1"
+TUNE_FEATURES_tune-ppce500v1 = "m32 spe ppce500v1"
+TUNE_PKGARCH_tune-ppce500v1 = "ppce500v1"
+PACKAGE_EXTRA_ARCHS_tune-ppce500v1 = "ppce500v1"
-- 
2.7.4



             reply	other threads:[~2018-06-14  9:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-14  9:25 chunrong.guo [this message]
2018-06-14 16:36 ` [PATCH] tune-ppce500v1: Add a tune file for PowerPC e500v1 cores Khem Raj

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=1528968301-3209-1-git-send-email-chunrong.guo@nxp.com \
    --to=chunrong.guo@nxp.com \
    --cc=openembedded-core@lists.openembedded.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.