From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 43834DDDDF for ; Tue, 2 Dec 2008 06:48:23 +1100 (EST) Message-ID: <49343F76.3060802@freescale.com> Date: Mon, 01 Dec 2008 13:48:06 -0600 From: Timur Tabi MIME-Version: 1.0 To: =?ISO-8859-1?Q?Andr=E9_Schwarz?= Subject: Re: i2c-mpc clocking scheme References: <492EB606.9020703@matrix-vision.de> <492EC031.9000802@matrix-vision.de> <4933FBC6.50100@freescale.com> <49343DC2.3070601@matrix-vision.de> In-Reply-To: <49343DC2.3070601@matrix-vision.de> Content-Type: text/plain; charset=ISO-8859-1 Cc: linuxppc-dev@ozlabs.org, Trent Piepho List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , André Schwarz wrote: > Wouldn't it be easier to omit frequency re-programming at all ? > Maybe configurable for non U-Boot users ... Well, the real problem is that Linux is ignoring what the boot loader has done. This is bad, regardless as to which boot loader you're using. The question is, do we give Linux the capability to program the I2C bus speed, or is this something that the boot loader should do? Unfortunately, the current Linux code means that this issue is not properly architected. You mentioned people who don't use U-Boot. Do they use some other boot loader? Or no boot loader at all? Do other boot loaders program the I2C bus speed? The reason I ask is that I want to know whether it's okay for Linux to ignore the FDR and DFSRR registers. -- Timur Tabi Linux kernel developer at Freescale