From: Helge Deller <deller@gmx.de>
To: Colin Ian King <colin.i.king@gmail.com>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next][V2] video: fbdev: kyro: make some const read-only arrays static and reduce type size
Date: Thu, 20 Jul 2023 07:47:33 +0200 [thread overview]
Message-ID: <898d9b03-bcaf-ec1b-2539-a290ab89aead@gmx.de> (raw)
In-Reply-To: <20230712161123.465713-1-colin.i.king@gmail.com>
On 7/12/23 18:11, Colin Ian King wrote:
> Don't populate the const read-only arrays on the stack but instead
> make them static const. Use smaller types to use less storage for
> the arrays. Also makes the object code a little smaller.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
applied.
Thanks!
Helge
> ---
>
> V2: Use smaller int types, kudos to Helge Deller for suggesting this
>
> ---
> drivers/video/fbdev/kyro/STG4000InitDevice.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/video/fbdev/kyro/STG4000InitDevice.c b/drivers/video/fbdev/kyro/STG4000InitDevice.c
> index edfa0a04854d..79886a246638 100644
> --- a/drivers/video/fbdev/kyro/STG4000InitDevice.c
> +++ b/drivers/video/fbdev/kyro/STG4000InitDevice.c
> @@ -83,11 +83,11 @@ volatile u32 i,count=0; \
> static u32 InitSDRAMRegisters(volatile STG4000REG __iomem *pSTGReg,
> u32 dwSubSysID, u32 dwRevID)
> {
> - u32 adwSDRAMArgCfg0[] = { 0xa0, 0x80, 0xa0, 0xa0, 0xa0 };
> - u32 adwSDRAMCfg1[] = { 0x8732, 0x8732, 0xa732, 0xa732, 0x8732 };
> - u32 adwSDRAMCfg2[] = { 0x87d2, 0x87d2, 0xa7d2, 0x87d2, 0xa7d2 };
> - u32 adwSDRAMRsh[] = { 36, 39, 40 };
> - u32 adwChipSpeed[] = { 110, 120, 125 };
> + static const u8 adwSDRAMArgCfg0[] = { 0xa0, 0x80, 0xa0, 0xa0, 0xa0 };
> + static const u16 adwSDRAMCfg1[] = { 0x8732, 0x8732, 0xa732, 0xa732, 0x8732 };
> + static const u16 adwSDRAMCfg2[] = { 0x87d2, 0x87d2, 0xa7d2, 0x87d2, 0xa7d2 };
> + static const u8 adwSDRAMRsh[] = { 36, 39, 40 };
> + static const u8 adwChipSpeed[] = { 110, 120, 125 };
> u32 dwMemTypeIdx;
> u32 dwChipSpeedIdx;
>
prev parent reply other threads:[~2023-07-20 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 16:11 [PATCH][next][V2] video: fbdev: kyro: make some const read-only arrays static and reduce type size Colin Ian King
2023-07-20 5:47 ` Helge Deller [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=898d9b03-bcaf-ec1b-2539-a290ab89aead@gmx.de \
--to=deller@gmx.de \
--cc=colin.i.king@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).