From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758491AbZEKNa2 (ORCPT ); Mon, 11 May 2009 09:30:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752772AbZEKNaJ (ORCPT ); Mon, 11 May 2009 09:30:09 -0400 Received: from qw-out-2122.google.com ([74.125.92.25]:2148 "EHLO qw-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752595AbZEKNaH convert rfc822-to-8bit (ORCPT ); Mon, 11 May 2009 09:30:07 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=Jrfq8CPQRc5wAZL+c4L8yyyzFU2g1EXjllAmGdXk1FdNZCe/jLA95QsKKAxD1kHwcm uCBNzU1u9xkYqqEvmXqdG8MSFJQZHa8beEekXFPo/npAcBbU3LlrNaqGaJBfZwInGqOK 2GptADLZmAw7lNufVCHmYRrbAau14imAZPuQM= MIME-Version: 1.0 In-Reply-To: <20090511112801.GA20283@sirena.org.uk> References: <20090506102202.73d6045d@hyperion.delvare> <20090511112801.GA20283@sirena.org.uk> From: =?GB2312?B?0sHU8w==?= Date: Mon, 11 May 2009 21:29:53 +0800 Message-ID: Subject: Re: [PATCH 2.6.29.2] PXA I2C: Define log level for i2c PXA error report To: Mark Brown Cc: Michael Abbott , linux-i2c@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2009/5/11 Mark Brown : > On Mon, May 11, 2009 at 11:31:51AM +0100, Michael Abbott wrote: > >> static struct i2c_pxa_platform_data xcep_i2c_platform_data  = { >>         .class = I2C_CLASS_HWMON >> }; > >> ... >>         pxa_set_i2c_info(&xcep_i2c_platform_data); > >> This is called in the .init_machine method, and the target system is a >> PXA255. > >> However, after the error messages on startup, all the sensors seem to be >> detected and seem to be operating normally. > > These errors occur when attempting to talk to non-existant devices which > is almost certainly going to happen with the class based device probing > since the kernel will probe for each device at each possible address on > each I2C bus. > that happen when the device driver registered but the hardware doesnot exist.i once met this when my camera driver could not find the hardware camera. thanks --wxc200