public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] ARM926: compile cpu_init_crit function only if CONFIG_SKIP_LOWLEVEL_INIT is not defined
Date: Wed, 19 Dec 2007 09:58:58 +0100	[thread overview]
Message-ID: <4768DD52.2090403@googlemail.com> (raw)
In-Reply-To: <59A262E22379284C89D92D603B117F01019E75@blrexsr3.slti.sanyo.co.in>

Gururaja Hebbar K R wrote:
> Hi,
>  
> At present in "start.S" inside cpu\arm926ejs,   cpu_init_crit is called 
> only if "CONFIG_SKIP_LOWLEVEL_INIT" is not defined
>  
> #ifndef CONFIG_SKIP_LOWLEVEL_INIT
>  bl cpu_init_crit
> #endif
>  
> But "cpu_init_crit" function  doesnt have any if defs which means 
> cpu_init_crit function will compile irrespective of  
> "CONFIG_SKIP_LOWLEVEL_INIT". 

Yes, thats clear.

> Hence the patch. The same is done in other 
> processor files. Kindly check "cpu\arm920t\start.S"

So the only reason that you do this is because its done in other files 
this way as well?

To not execute cpu_init_crit the existing ifndef is sufficent. But my 
point is: When you want to decrease resulting binary size by excluding 
unnecessary code (cpu_init_crit), then you should also exclude the 
then unused board specific lowlevel_init called from cpu_init_crit as 
well.

Dirk

> ------------------------------------------------------------------------
> *From:* Dirk Behme [mailto:dirk.behme at googlemail.com]
> *Sent:* Wed 19-Dec-07 3:27 PM
> *To:* Gururaja Hebbar K R
> *Cc:* u-boot-users at lists.sourceforge.net
> *Subject:* Re: [U-Boot-Users] [PATCH] ARM926: compile cpu_init_crit 
> function only if CONFIG_SKIP_LOWLEVEL_INIT is not defined
> 
> Hebbar wrote:
>  > This patches allows cpu_init_crit function to be compilled only if
>  > CONFIG_SKIP_LOWLEVEL_INIT is not defined. At present irrespective of
>  > CONFIG_SKIP_LOWLEVEL_INIT, cpu_init_crit is always compilled. This is for
>  > arm926ejs module.
>  >
>  > Signed-off-by: K R Gururaja Hebbar <gururajakr@sanyo.co.in>
>  >
>  >
>  > --- u-boot-1.3.1/cpu/arm926ejs/start.S        2007-12-06 
> 01:21:19.000000000 -0800
>  > +++ uboot/cpu/arm926ejs/start.S       2007-12-19 08:40:37.296875000 -0800
>  > @@ -187,7 +187,7 @@ clbss_l:str       r2, [r0]                /* 
> clear loop... 
>  >  _start_armboot:
>  >       .word start_armboot
>  > 
>  > -
>  > +#ifndef CONFIG_SKIP_LOWLEVEL_INIT
>  >  /*
>  >   
> *************************************************************************
>  >   *
>  > @@ -225,6 +225,9 @@ cpu_init_crit:
>  >       bl      lowlevel_init   /* go setup pll,mux,memory */
>  >       mov     lr, ip          /* restore link */
>  >       mov     pc, lr          /* back to my caller */
>  > +    
>  > +#endif /* CONFIG_SKIP_LOWLEVEL_INIT */
>  > +    
>  >  /*
>  >   
> *************************************************************************
>  >   *
>  > I welcome comments, complaints, suggestions and advices.
> 
> The reason for this is to decrease resulting binary size? If so, all
> lowlevel_init() should be encapsulated as well to save even more space?
> 
> Dirk
> 

  reply	other threads:[~2007-12-19  8:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19  8:48 [U-Boot-Users] [PATCH] ARM926: compile cpu_init_crit function only if CONFIG_SKIP_LOWLEVEL_INIT is not defined Gururaja Hebbar K R
2007-12-19  8:58 ` Dirk Behme [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-18 23:52 Hebbar
2007-12-18 23:59 ` Hebbar
2007-12-19  6:27   ` Dirk Behme
2008-02-04 22:38   ` Wolfgang Denk
2008-02-05  1:32     ` Hebbar
2008-02-13 23:59       ` Wolfgang Denk
2008-02-14  0:19         ` Hebbar

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=4768DD52.2090403@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --cc=u-boot@lists.denx.de \
    /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