From: Wolfram Sang <wsa@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] soc: renesas: rcar-sysc: Optimize rcar_sysc_area struct sizes
Date: Thu, 9 Jun 2022 09:15:55 +0200 [thread overview]
Message-ID: <YqGeK5/iEt2kqiL9@shikoro> (raw)
In-Reply-To: <cbbc8f464743d636895c048de61aa610d75392de.1654701156.git.geert+renesas@glider.be>
[-- Attachment #1.1: Type: text/plain, Size: 654 bytes --]
On Wed, Jun 08, 2022 at 05:14:21PM +0200, Geert Uytterhoeven wrote:
> Reduce the sizes of the rcar_sysc_area and rcar_gen4_sysc_area
> structures:
> - parent is in the range [-1..32] or [-1..64], so s8 is sufficient,
> - flags needs just 3 bits (for now), so u8 is plenty.
>
> This reduces kernel size by:
> - 288 bytes for an R-Car Gen1+Gen2 kernel (arm32),
> - 1772 bytes for an R-Car Gen3+Gen4 kernel (arm64).
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Nice! Dunno how to verify the parent ranges, but my Spider board boots
fine with it. So
Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-09 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 15:14 [PATCH] soc: renesas: rcar-sysc: Optimize rcar_sysc_area struct sizes Geert Uytterhoeven
2022-06-09 7:15 ` Wolfram Sang [this message]
2022-06-10 11:21 ` Yoshihiro Shimoda
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=YqGeK5/iEt2kqiL9@shikoro \
--to=wsa@kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=yoshihiro.shimoda.uh@renesas.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