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] TI DaVinci DM646x: Adding initial support for DM6467 EVM
Date: Fri, 02 Oct 2009 09:34:33 -0500	[thread overview]
Message-ID: <4AC60F79.7040404@windriver.com> (raw)
In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D92F443FC@dlee01.ent.ti.com>

Paulraj, Sandeep wrote:
> 

<snip>

> 
>>> +
>>> +/* SoC Configuration */
>>> +#define CONFIG_ARM926EJS				/* arm926ejs CPU */
>>> +#define CONFIG_SYS_TIMERBASE		0x01c21400	/* use timer 0 */
>> Is there a logical register #define you could use instead of the magic
>> number?
> 
> I can include the hardware.h and get the value from there, but the way the hardware.h for DaVinci has evolved over the years, including it in the config will result in compilation failure.
> I'll add this to my TODO list and send in a patch to clean up for all DaVinci SOC's the moment I get some free cycles.
> 

That is fine.

>>> +
>>> +/* I2C Configuration */
>>> +#define CONFIG_HARD_I2C
>>> +#define CONFIG_DRIVER_DAVINCI_I2C
>>> +#define CONFIG_SYS_I2C_SPEED		80000
>> This speed is unusual.
> 
> The same speed has been used with a slightly older version of U-boot and has worked fine
> 
>> davinci_sonata.h has a comment that it had a silicon bug with 100k
>> Could the same comment be applied here ?
> 
> I don't believe so

Ok fine as-is.

Tom

  reply	other threads:[~2009-10-02 14:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02  0:29 [U-Boot] [PATCH] TI DaVinci DM646x: Adding initial support for DM6467 EVM s-paulraj at ti.com
2009-10-02 12:16 ` Tom
2009-10-02 13:50   ` Paulraj, Sandeep
2009-10-02 14:34     ` Tom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-10 16:10 s-paulraj at ti.com
     [not found] <1255277911-8518-1-git-send-email-s-paulraj@ti.com>
2009-10-11 18:36 ` Tom Rix

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=4AC60F79.7040404@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