From: Matt Porter <mporter@embeddedalley.com>
To: Chun Chung Lo <cclo@astri.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: DS1302 driver for powerpc
Date: Wed, 30 Aug 2006 08:55:07 -0500 [thread overview]
Message-ID: <20060830135507.GA19477@gate.crashing.org> (raw)
In-Reply-To: <A7B1E4DD46AA7046A4398F745240F29402737D5B@ASPROEXG.astri.local>
On Wed, Aug 30, 2006 at 07:54:16PM +0800, Chun Chung Lo wrote:
>
> Hi all,
>
> I am now doing a STB project and the development board uses a DS1302
> (trickle charge timekeeping chip) as a RTC. Our board is a IBM PPC405EP
> with a linux kernel 2.4.20 running on it. And the DS1302 is controlled
> by 2 GPIO pins instead of I2C.
>
> I would like to ask are there any porting of DS1302 support under ppc
> architecture? (I can only find DS1302 is supported under cris
> architecture.)
There doesn't seem to be any DS1302 support "for ppc" available. However,
even if there were a platform with DS1302 support you'd be in the same
boat as the low-level support for cris. Support for DS1302 has a glue
layer that's board-specific based on what GPIO pins are used to drive
it. So if you had this driver for another PPC system like 83xx you'd
still have no better starting point than the cris ds1302 driver glue
since the GPIO mechanism/connection is different. Porting the
board-specific glue from arch/cris/drivers/ds1302.c to 4xx GPIO is
trivial to do though.
-Matt
next prev parent reply other threads:[~2006-08-30 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 11:54 DS1302 driver for powerpc Chun Chung Lo
2006-08-30 13:55 ` Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-31 0:51 Chun Chung Lo
2006-08-31 1:11 ` Matt Porter
2006-08-31 1:03 Chun Chung Lo
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=20060830135507.GA19477@gate.crashing.org \
--to=mporter@embeddedalley.com \
--cc=cclo@astri.org \
--cc=linuxppc-embedded@ozlabs.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).