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] [RFC] PPC: post_word_{load/store} - eliminate redundant code
Date: Wed, 21 Apr 2010 15:59:16 +0200	[thread overview]
Message-ID: <20100421135916.ECA0111356CB@gemini.denx.de> (raw)
In-Reply-To: <x2h660c0f821004210624y32636405j7746304a059def4a@mail.gmail.com>

Dear Michael Zaidman,

In message <x2h660c0f821004210624y32636405j7746304a059def4a@mail.gmail.com> you wrote:
>
> Meanwhile the  post_word_{load/store} are located in the commproc.c
> files for the following architectures:
> mpc8260,
> mpc85xx,
> mpc8xx,
> ppc4xx.
> 
> Looking for the way to add POST functionality for the mpc83xx family I
> realized that the post_word_{load/store} can be generalized for all
> ppc architectures.
> 
> Could you point please to the file where such kind of things - common
> for all CPU families of particular architecture should be located?

Actually there are two parts to it:

bootcount_store() and bootcount_load() are needed for the boot
counter, a generic feature; I tend to move these into
arch/powerpc/lib/bootcount.c; the code also needs to be rewritten to
use I/O accessors.

post_word_store() and post_word_load() is architecture specific,
common POST code that unfortunately also gets used by the logbuffer
code. This should be split. Then we would have
arch/powerpc/lib/logbuf.c and post/arch/powerpc/post_io.c or such.

Please also note that there are more files implementing such code -
see for example here:

	board/cm5200/cm5200.c
	board/bf537-stamp/post.c
	board/barco/barco.c
	board/bc3450/bc3450.c
	board/ssv/common/post.c
	board/tqc/tqm5200/tqm5200.c
	board/xes/xpedite1000/xpedite1000.c


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
Without facts, the decision cannot be made logically. You  must  rely
on your human intuition.
	-- Spock, "Assignment: Earth", stardate unknown

  parent reply	other threads:[~2010-04-21 13:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 16:44 [U-Boot] [RFC] PPC: post_word_{load/store} - eliminate redundant code Michael Zaidman
2010-04-20 19:55 ` Michael Zaidman
2010-04-20 21:39 ` Wolfgang Denk
2010-04-21  4:30   ` Stefan Roese
2010-04-21  7:05   ` Michael Zaidman
2010-04-21 13:24   ` Michael Zaidman
2010-04-21 13:51     ` Stefan Roese
2010-04-21 14:07       ` Michael Zaidman
2010-04-21 13:59     ` Wolfgang Denk [this message]
2010-04-21 14:29       ` Michael Zaidman
2010-04-21 21:40         ` Wolfgang Denk
2010-04-22  0:16           ` Mike Frysinger
2010-04-22  6:41           ` Michael Zaidman
2010-04-22  9:03             ` Wolfgang Denk
2010-04-22  9:27               ` Michael Zaidman

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=20100421135916.ECA0111356CB@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