linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "David Müller (ELSOFT AG)" <d.mueller@elsoft.ch>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Registering RTC access methods in platform_init()
Date: Wed, 24 Oct 2001 11:35:12 +0200	[thread overview]
Message-ID: <3BD68B50.8090904@elsoft.ch> (raw)


Hello

I have a question regarding the registering of the RTC access methods in
platform_init() in ppc4xx_setup.c.
The problem is quite similar to the one i stated in
one of my previous e-mails "Additional IRQ handlers in ppc4xx_init_IRQ()".

Currently this is done in this way:

#ifdef CONFIG_PPC_RTC
/* new timer stuff */
	ppc_md.time_init = todc_time_init;
	ppc_md.set_rtc_time = todc_set_rtc_time;
	ppc_md.get_rtc_time = todc_get_rtc_time;

#if !defined(CONFIG_PIP405) && !defined(CONFIG_MIP405)
	ppc_md.nvram_read_val = todc_direct_read_val;
	ppc_md.nvram_write_val = todc_direct_write_val;
#else
	ppc_md.nvram_read_val = todc_mc146818_read_val;
	ppc_md.nvram_write_val = todc_mc146818_write_val;
#endif
#endif


All other ports using a MC146818 RTC have their own xxx_setup.c file
(Sandpoint, Adirondack, ...).

I suppose the preferred way to solve this is to replace this whole init
code by a call to a board specific init routine?




Dave


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-10-24  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-24  9:35 David Müller (ELSOFT AG) [this message]
2001-10-24 15:23 ` Registering RTC access methods in platform_init() Armin Kuster

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=3BD68B50.8090904@elsoft.ch \
    --to=d.mueller@elsoft.ch \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).