All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/6] nand_spl: update udelay for Freescale boards
Date: Mon, 13 Aug 2012 18:35:46 -0500	[thread overview]
Message-ID: <50298F52.7050805@freescale.com> (raw)
In-Reply-To: <CAEsOVNdMANaSsXkRcMM4k0qsXSB2X1cmciCfDdMtAZO1CFOhVQ@mail.gmail.com>

On 08/13/2012 06:28 PM, McClintock Matthew-B29882 wrote:
> On Mon, Aug 13, 2012 at 6:22 PM, Scott Wood <scottwood@freescale.com> wrote:
>> On 08/13/2012 06:14 PM, McClintock Matthew-B29882 wrote:
>>> On Mon, Aug 13, 2012 at 5:56 PM, Scott Wood <scottwood@freescale.com> wrote:
>>>> On 08/13/2012 01:10 PM, Matthew McClintock wrote:
>>>>> Let's use the more appropriate udelay for the nand_spl. While we
>>>>> can't make use of u-boot's full udelay we can atl east use a for
>>>>> loop that won't get optimized away .Since we have the bus clock
>>>>> we can use the timebase to calculate wall time.
>>>>>
>>>>> Looked at reusing the u-boot udelay functions but it pulls in a lot
>>>>> of code as well as depends on the gd struct and would require a lot
>>>>> of rework
>>>>
>>>> What's wrong with depending on the gd struct?
>>>
>>> Perhaps the wording is wrong a bit off. It's just pulling in other
>>> stuff and as you know we are very space constrained.
>>
>> A struct definition doesn't take up space.  Maybe you meant a dependency
>> on certain specific code that puts things in the gd struct?
> 
> Correct.
> 
>>>>> @@ -123,6 +124,9 @@ ifneq ($(OBJTREE), $(SRCTREE))
>>>>>  $(obj)nand_boot.c:
>>>>>       @rm -f $(obj)nand_boot.c
>>>>>       ln -s $(SRCTREE)/nand_spl/board/$(BOARDDIR)/nand_boot.c $(obj)nand_boot.c
>>>>> +$(obj)../common.c:
>>>>> +     @rm -f $(obj)../common.c
>>>>> +     ln -s $(SRCTREE)/nand_spl/board/freescale/common.c $(obj)../common.c
>>>>>  endif
>>>>
>>>> Why are you creating a link in the parent directory?
>>>
>>> The typical build process picks out files needed for the build and
>>> symlinks them to nand_spl folder - or if building out of tree then it
>>> symlinks to the out of tree folder. This is true for all files in
>>> nand_spl as it currently exists not just this new file.
>>
>> This is the first time I've seen a link go in $(obj)../ rather than $(obj)
> 
> It's because that's where the includes reference it. When building in
> tree, it does nothing because it can just reference the C file in the
> parent directory. When it's out of tree - we need to install the
> symlink in the proper location in the build folder.

I'm not thrilled with it, but it shouldn't have long to live since
new-spl doesn't do the symlink thing.

-Scott

  reply	other threads:[~2012-08-13 23:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 18:10 [U-Boot] [PATCH 1/6] p1014rdb: set ddr bus width properly depending on SVR Matthew McClintock
2012-08-13 18:10 ` [U-Boot] [PATCH 2/6] p1010rdb: fix ddr values for p1014rdb (setting bus width to 16bit) Matthew McClintock
2012-08-13 18:10 ` [U-Boot] [PATCH 3/6] powerpc/p1010rdb: nandboot: compare SVR properly Matthew McClintock
2012-08-13 18:10 ` [U-Boot] [PATCH 4/6] nand_spl: update udelay for Freescale boards Matthew McClintock
2012-08-13 22:56   ` Scott Wood
2012-08-13 23:14     ` McClintock Matthew-B29882
2012-08-13 23:22       ` Scott Wood
2012-08-13 23:28         ` McClintock Matthew-B29882
2012-08-13 23:35           ` Scott Wood [this message]
2012-08-13 18:10 ` [U-Boot] [PATCH 5/6] nand_spl: p1023rds: wait before enabling DDR controller Matthew McClintock
2012-08-13 18:18   ` Scott Wood
2012-08-13 18:50     ` McClintock Matthew-B29882
2012-08-13 18:10 ` [U-Boot] [PATCH 6/6] nand_spl: change out_be32 to raw_writel and depend on subsequent sync Matthew McClintock
2012-08-13 23:23   ` Scott Wood
2012-08-13 23:31     ` McClintock Matthew-B29882
2012-08-13 23:34       ` Scott Wood
2012-08-13 23:37         ` McClintock Matthew-B29882
2012-08-18 19:05     ` Scott Wood
2012-08-20 16:11       ` Andy Fleming
2012-08-20 16:51         ` Scott Wood

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=50298F52.7050805@freescale.com \
    --to=scottwood@freescale.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 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.