public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 02/12] SPEAr : Adding basic SPEAr architecture support.
Date: Thu, 14 Jan 2010 09:18:26 -0600	[thread overview]
Message-ID: <4B4F35C2.8090501@windriver.com> (raw)
In-Reply-To: <83d1d72b1001132220m2f9ce8a8xc6178cc4e397e0e0@mail.gmail.com>

Vipin Kumar wrote:
> Hello Tom,
> 
>> +
>> +#include <common.h>
>> +#include <asm/io.h>
>> +#include <asm/arch/spr_syscntl.h>
>> +
>> +void reset_cpu(ulong ignored)
>> +{
>> +       struct syscntl_regs *syscntl_regs_p =
>> +           (struct syscntl_regs *)CONFIG_SPEAR_SYSCNTLBASE;
>> +
>> This is not bi-sect able
>>
>> CONFIG_SPEAR_SYSCNTLBASE is not defined until #7.
>> This looks like a register base address.
>> This should be defined in spr_syscntl.h
>>
>> This also applies to CONFIG_SPEAR_MISCBASE.
>> Should be in spr_misc.h
>>
> 
> I intentionally used include/configs/spear.h as the location to define
> base addresses. The reason is that same IP can be embedded in more
> than one SoCs. Offcourse, the IP can lie at a different base address
> in each of them. In that case,we pick base address from
> include/configs/spear.h
> 
> Also, other architectures use configs/xxx.h for defining base addresses
> 
> Now, because spear.h is not added until the support for spear600
> board is added, it leads to the problem you described above.
> Offcourse, a build is not possible before adding first board support
> 
> So how should we prcoceed,
>  1. keep it as it is bacause build in not possible OR
No

>  2. reorder the patch
I do not think simple reording of the patches ok either.
As I want the SOC support first, then boards.

You are using the spear.h file as if it was in include/asm/arch/spear.h
not in include/configs.

There are other problems with spear.h
At the least it will need to be a version of this per board.

To be bisectable.
1. You need to define register offsets in asm/arch file or
2. Move the non bisectable code to a later patch

I prefer 1.

Tom

> 
> Best Regards,
> Vipin

  reply	other threads:[~2010-01-14 15:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 13:06 [U-Boot] [PATCH v4 02/12] SPEAr : Adding basic SPEAr architecture support Tom
2010-01-14  6:20 ` Vipin Kumar
2010-01-14 15:18   ` Tom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-11 11:15 [U-Boot] [PATCH v4 00/12] Support for SPEAr SoCs Vipin KUMAR
2010-01-11 11:15 ` [U-Boot] [PATCH v4 01/12] SPEAr : Adding README.spear in doc Vipin KUMAR
2010-01-11 11:15   ` [U-Boot] [PATCH v4 02/12] SPEAr : Adding basic SPEAr architecture support Vipin KUMAR

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=4B4F35C2.8090501@windriver.com \
    --to=tom.rix@windriver.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