From: Riku Voipio <riku.voipio@movial.fi>
To: Dan Williams <dan.j.williams@intel.com>
Cc: David Brownell <david-b@pacbell.net>,
rtc-linux@googlegroups.com,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Alessandro Zummo <alessandro.zummo@towertech.it>,
i2c@lm-sensors.org, buytenh@wantstofly.org,
peter.milne@d-tacq.com
Subject: Re: [patch 2.6.19-git] rts-rs5c372 updates: more chips, alarm, 12hr mode, etc
Date: Tue, 12 Dec 2006 10:39:29 +0200 [thread overview]
Message-ID: <457E6AC1.3040303@movial.fi> (raw)
In-Reply-To: <e9c3a7c20612111533o75683c2j30dbf440696932a6@mail.gmail.com>
Executive summary for the new in CC list: Is it possible that i2c-iop3xx
driver in current mainline
Linux is buggy regarding repeated start conditions?
Dan Williams wrote:
> According to the latest specification update
> (http://www.intel.com/design/iio/specupdt/27351910.pdf) there are no
> known issues with the i2c. I looked through the thread and did not
> see what board you are using, can you send those details?
We are using Thecus n2100, which has a IOP 80219. The vendor
itself patched iq31244 board file, so presumably it's very similar.
http://www.debonaras.org/wiki/Info/ThecusN2100Internals
Any more specific information you want?
>
> I have not dealt with the i2c-iop3xx driver in the past. Have you
> tried contacting the last person to make functional changes to the
> driver?
Well, now we have :)
> Hi Riku, this is the first message I have received.
This what I sent then:
-snip-
We have an Ricoh 5c372 RTC [1] which uses "repeated start" for
internal register access. On a ixp-4xx device (Synology DS101),
the mainline linux driver suposedly worked fine. On our device,
a thecus n2100 with IOP 80219, the driver almost works.
See page 31 on the datasheet[1] for example read transfer.
After some debugging, it seems the RTC is ignoring the internal
address setting request. On iop, we allways get the contents of
beginning from internal register 0xF, which is the default internal
address it sets after a stop condition. I'm not equipped with a scope,
so I don't see what's happening on the wire..
I have a workaround for this specific case, but I don't like
it, and this could be problem with other chips as well.
-snip-
Since then I learned the same rtc is in use with Kuro Boxes, which
use a freescale ppc soc. There both mainline driver and my patched
driver works fine.
[1] http://www.ricoh.com/LSI/product_rtc/2wire/5c372/5c372a-e.pdf
[2]
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;hb=HEAD;f=drivers/rtc/rtc-rs5c372.c
next prev parent reply other threads:[~2006-12-12 8:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 2:59 [patch 2.6.19-git] rts-rs5c372 updates: more chips, alarm, 12hr mode, etc David Brownell
2006-12-09 9:38 ` [rtc-linux] " Alessandro Zummo
2006-12-11 6:27 ` Voipio Riku
2006-12-11 19:55 ` David Brownell
2006-12-11 22:23 ` Voipio Riku
2006-12-11 23:33 ` Dan Williams
2006-12-12 8:20 ` David Brownell
2006-12-12 8:39 ` Riku Voipio [this message]
2006-12-12 8:30 ` David Brownell
2007-01-03 3:07 ` David Brownell
2007-01-03 22:51 ` Voipio Riku
2007-01-04 4:23 ` David Brownell
2007-01-04 12:05 ` Alessandro Zummo
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=457E6AC1.3040303@movial.fi \
--to=riku.voipio@movial.fi \
--cc=alessandro.zummo@towertech.it \
--cc=buytenh@wantstofly.org \
--cc=dan.j.williams@intel.com \
--cc=david-b@pacbell.net \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.milne@d-tacq.com \
--cc=rtc-linux@googlegroups.com \
/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