From: Jake Magee <jakemagee@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: PPC405 RTC not working
Date: Mon, 31 Aug 2009 23:09:23 -0500 [thread overview]
Message-ID: <a8142e730908312109x7f49806duc35bb580051af2e8@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
I am currently trying to get a M41T65 sensor to work on a PPC405 based
board. I am using the 2.6.26 kernel with a backported version of
rtc-m41t80.c (from 2.6.30). Everything compiles and loads fine. However,
there is no /dev/rtc node created. "/proc/devices" returns "254 rtc" (which
I feel isn't correct). And "/sys/bus/i2c/devices/" list nothing for the
RTC. I do see the information from the device tree in
"/proc/device-tree/plb/opb/i2c@ef600400/rtc@68/"
Here is my dts information:
IIC0: i2c@ef600400 {
compatible = "ibm,iic-405exr", "ibm,iic";
reg = <ef600400 14>;
interrupt-parent = <&UIC0>;
interrupts = <2 4>;
index = <0>;
rtc@68 {
compatible = "m41t65";
reg = <68>;
};
};
Thanks!
Jake Magee
[-- Attachment #2: Type: text/html, Size: 1211 bytes --]
reply other threads:[~2009-09-01 4:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a8142e730908312109x7f49806duc35bb580051af2e8@mail.gmail.com \
--to=jakemagee@gmail.com \
--cc=linuxppc-dev@lists.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