Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] tune-cortexa72-cortexa53: Add tune
Date: Fri, 13 Dec 2019 16:05:24 -0600	[thread overview]
Message-ID: <1370d17b-c688-ef9a-3bdf-bfa4857d4666@kernel.crashing.org> (raw)
In-Reply-To: <20191213220309.3964324-1-JPEWhacker@gmail.com>



On 12/13/19 4:03 PM, Joshua Watt wrote:
> Adds a tune for Cortex-A72 Cortex-A53 big.LITTLE SoCs, e.g.  Rockchip
> RK3399
> 
> Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
> ---
>  .../include/tune-cortexa72-cortexa53.inc       | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
>  create mode 100644 meta/conf/machine/include/tune-cortexa72-cortexa53.inc
> 
> diff --git a/meta/conf/machine/include/tune-cortexa72-cortexa53.inc b/meta/conf/machine/include/tune-cortexa72-cortexa53.inc
> new file mode 100644
> index 00000000000..30e49d20769
> --- /dev/null
> +++ b/meta/conf/machine/include/tune-cortexa72-cortexa53.inc
> @@ -0,0 +1,18 @@
> +DEFAULTTUNE ?= "cortexa72-cortexa53"
> +require conf/machine/include/arm/arch-armv8a.inc
> +
> +TUNEVALID[cortexa72-cortexa53] = "Enable big.LITTLE Cortex-A72.Cortex-A53 specific processor optimizations"
> +TUNECONFLICTS[aarch64] = "armv4 armv5 armv6 armv7 armv7a"
> +
> +TUNE_CCARGS .= "${@bb.utils.contains("TUNE_FEATURES", "aarch64", " -march=armv8-a", "" ,d)}"
> +
> +MACHINEOVERRIDES =. "${@bb.utils.contains("TUNE_FEATURES", "cortexa72-cortexa53", "cortexa72-cortexa53:", "" ,d)}"
> +
> +TUNE_CCARGS .= "${@bb.utils.contains("TUNE_FEATURES", "cortexa72-cortexa53", " -mtune=cortex-a72.cortex-a53", "", d)}"
> +
> +# Little Endian base configs
> +AVAILTUNES += "cortexa72-cortexa53"
> +ARMPKGARCH_tune-cortexa72-cortexa53 = "cortexa72-cortexa53"

I'm wondering if the pkgarch should be shorter.. This really does make package
names very long.  (I don't know offhand if that is an actual problem or not.)

Also a similar tune has been used by NXP and Wind River.  So hopefully we don't
end up with conflicts.

--Mark

> +TUNE_FEATURES_tune-cortexa72-cortexa53 = "${TUNE_FEATURES_tune-aarch64} cortexa72-cortexa53"
> +PACKAGE_EXTRA_ARCHS_tune-cortexa72-cortexa53 = "${PACKAGE_EXTRA_ARCHS_tune-aarch64} cortexa72-cortexa53"
> +BASE_LIB_tune-cortexa72-cortexa53 = "lib64"
> 


  reply	other threads:[~2019-12-13 22:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 22:03 [PATCH] tune-cortexa72-cortexa53: Add tune Joshua Watt
2019-12-13 22:05 ` Mark Hatle [this message]
2019-12-13 22:08   ` Joshua Watt
2019-12-13 23:10 ` Adrian Bunk
2019-12-14  0:47   ` Joshua Watt
2019-12-14  1:22     ` Adrian Bunk
2019-12-14  1:28       ` Joshua Watt
2019-12-14  1:41         ` Adrian Bunk
2019-12-14  1:48           ` Joshua Watt
2019-12-14  0:54 ` [PATCH v2] tune-cortexa72-cortexa53: Add tunes Joshua Watt
2019-12-14  1:21   ` Andre McCurdy
2019-12-14  1:29     ` Joshua Watt
2019-12-14 16:06   ` [PATCH v3] " Joshua Watt

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=1370d17b-c688-ef9a-3bdf-bfa4857d4666@kernel.crashing.org \
    --to=mark.hatle@kernel.crashing.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox