public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix calculation of I2C clock for some 86xx chips
Date: Wed, 30 Apr 2008 22:52:52 +0200	[thread overview]
Message-ID: <20080430205252.5998424681@gemini.denx.de> (raw)
In-Reply-To: Your message of "Fri, 04 Apr 2008 11:16:11 CDT." <1207325771-1374-1-git-send-email-timur@freescale.com>

In message <1207325771-1374-1-git-send-email-timur@freescale.com> you wrote:
> Some 86xx chips use CCB as the base clock for the I2C, and others used CCB/2.
> There is no pattern that can be used to determine which chips use which
> frequency, so the only way to determine is to look up the actual SOC
> designation and use the right value for that SOC.
> 
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
> 
> Yes, this is ugly and stupid, but the only alternative is to update each
> board configuration file with another CONFIG_ option.  And yes, this does
> mean that as new 86xx variants are announced, cpu/mpc86xx/speed.c may need
> to be updated.
> 
>  cpu/mpc86xx/speed.c |   14 +++++++++++++-
>  1 files changed, 13 insertions(+), 1 deletions(-)

Applied, thanks.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
An expert is a person who avoids the small errors while  sweeping  on
to the grand fallacy.

      parent reply	other threads:[~2008-04-30 20:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 16:16 [U-Boot-Users] [PATCH] Fix calculation of I2C clock for some 86xx chips Timur Tabi
2008-04-18  4:14 ` Wolfgang Denk
2008-04-21 17:51   ` Jon Loeliger
2008-04-30 19:54     ` Timur Tabi
2008-04-30 20:53       ` Wolfgang Denk
2008-04-30 20:52 ` Wolfgang Denk [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=20080430205252.5998424681@gemini.denx.de \
    --to=wd@denx.de \
    --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