From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751912AbbCUUKE (ORCPT ); Sat, 21 Mar 2015 16:10:04 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:51093 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751642AbbCUUKB (ORCPT ); Sat, 21 Mar 2015 16:10:01 -0400 Date: Sat, 21 Mar 2015 21:09:57 +0100 From: Pavel Machek To: kernel list , Sergey.Gerasimov@astrosoft-development.com, o.weber@gateware.de, a.zummo@towertech.it, rtc-linux@googlegroups.com, tomas@novotny.cz, matti.vaittinen@nsn.com, s.trumtrar@pengutronix.de Subject: tqm8315 + ds1337: problems Message-ID: <20150321200957.GA23161@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! Something is wrong with real time clock on tqm8315 board... or maybe with i2c on board, as I have trouble reading same information from u-boot using "i2c md" commands: Does rtc work for you on tqm8315? Any ideas how to debug this further? Thanks, Pavel [ 1.480289] i2c /dev entries driver [ 1.484371] mpc-i2c e0003000.i2c: initializing [ 1.489119] mpc-i2c e0003000.i2c: clock 378787 Hz (dfsrr=6 fdr=1) [ 1.495330] mpc-i2c e0003000.i2c: timeout 1000000 us [ 1.501640] mpc-i2c e0003000.i2c: Doing write 1 bytes to 0x68 - 1 of 2 messa ges [ 1.512126] mpc-i2c e0003000.i2c: Doing read 2 bytes to 0x68 - 2 of 2 messag es [ 1.519696] mpc-i2c e0003000.i2c: Doing write 2 bytes to 0x68 - 1 of 1 messa ges [ 1.527413] mpc-i2c e0003000.i2c: Doing write 1 bytes to 0x68 - 1 of 2 messa ges [ 1.534959] mpc-i2c e0003000.i2c: Doing read 8 bytes to 0x68 - 2 of 2 messag es [ 1.542951] mpc-i2c e0003000.i2c: Doing write 1 bytes to 0x68 - 1 of 2 messa ges [ 1.550552] mpc-i2c e0003000.i2c: Doing read 7 bytes to 0x68 - 2 of 2 messag es [ 1.558329] rtc-ds1307 0-0068: read: 07 39 00 06 00 81 01 [ 1.563868] rtc-ds1307 0-0068: read secs=7, mins=39, hours=0, mday=0, mon=0, year=101, wday=5 [ 1.572493] rtc (null): read_time: fail to read [ 1.577664] rtc-ds1307 0-0068: rtc core: registered ds1337 as rtc0 [ 1.584476] at24 0-0057: 32768 byte 24c256 EEPROM, writable, 64 bytes/write [ 1.592483] mpc-i2c e0003000.i2c: Doing write 1 bytes to 0x48 - 1 of 2 messa ges [ 1.602493] mpc-i2c e0003000.i2c: Doing read 1 bytes to 0x48 - 2 of 2 messag es [ 1.610538] lm75 0-0048: hwmon0: sensor 'lm75' [ 1.615870] TCP: cubic registered [ 1.619331] NET: Registered protocol family 17 [ 1.624127] Key type dns_resolver registered [ 1.633413] mpc-i2c e0003000.i2c: Doing write 1 bytes to 0x68 - 1 of 2 messa ges [ 1.641012] mpc-i2c e0003000.i2c: Doing read 7 bytes to 0x68 - 2 of 2 messag es [ 1.648787] rtc-ds1307 0-0068: read: 07 39 00 06 00 81 01 [ 1.654305] rtc-ds1307 0-0068: read secs=7, mins=39, hours=0, mday=0, mon=0, year=101, wday=5 [ 1.662921] rtc rtc0: read_time: fail to read [ 1.667375] rtc-ds1307 0-0068: hctosys: unable to read the hardware clock [ 1.739679] gianfar: not advertising gigabit [ 1.851232] ata2: No Device OR PHYRDY change,Hstatus = 0xa0000000 [ 1.857466] ata2: SATA link down (SStatus 0 SControl 300) [ 1.863072] ata1: Signature Update detected @ 508 msecs [ 2.039242] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html