From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id BD97DDDE07 for ; Fri, 24 Oct 2008 11:20:01 +1100 (EST) Subject: Re: [PATCH] fix i2c on PPC linkstation / kurobox machines From: Benjamin Herrenschmidt To: Guennadi Liakhovetski In-Reply-To: References: <20081022191650.GA11406@weiser.dinsnail.net> <20081023213309.GA19777@weiser.dinsnail.net> Content-Type: text/plain Date: Fri, 24 Oct 2008 11:19:40 +1100 Message-Id: <1224807581.7654.424.camel@pasglop> Mime-Version: 1.0 Cc: Michael Weiser , =?ISO-8859-1?Q?Rog=E9rio?= Brito , linuxppc-dev@ozlabs.org, Scott Wood Reply-To: benh@kernel.crashing.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 2008-10-24 at 01:05 +0200, Guennadi Liakhovetski wrote: > i2c is broken on linkstation / kurobox machines since at least 2.6.27. Fix > it. Also remove CONFIG_SERIAL_OF_PLATFORM, which, if enabled, breaks the > serial console after the "console handover: boot [udbg0] -> real [ttyS1]" > message. > > Signed-off-by: Guennadi Liakhovetski You may want to use udbg_printf() to track down what's up. There's some fishy code there indeed, what happens is that the legacy serial code creates a platform device at boot time. Then, the of_serial attaches to the device node for the same device and tries to register it. It's supposed to "detect" that it's the same device but yeah, it may be buggy, I've seen problems with it in the past, among others, I think it can lose some state. In the meantime, removing SERIAL_OF_PLATFORM is a good solution. Ben.