mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: 伊泽 <wxc200@gmail.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Michael Abbott <michael@araneidae.co.uk>,
	linux-i2c@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.29.2] PXA I2C: Define log level for i2c PXA error  report
Date: Mon, 11 May 2009 21:29:53 +0800	[thread overview]
Message-ID: <fd6b62c10905110629w6c9a641fr878351fb9217a32e@mail.gmail.com> (raw)
In-Reply-To: <20090511112801.GA20283@sirena.org.uk>

2009/5/11 Mark Brown <broonie@sirena.org.uk>:
> 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

  parent reply	other threads:[~2009-05-11 13:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06  7:32 Michael Abbott
2009-05-06  8:22 ` Jean Delvare
2009-05-11  6:38   ` Michael Abbott
2009-05-11  8:56     ` Jean Delvare
2009-05-11 10:11     ` 伊泽
2009-05-11 10:31       ` Michael Abbott
2009-05-11 11:28         ` Mark Brown
2009-05-11 12:16           ` Michael Abbott
2009-05-11 12:23             ` Mark Brown
2009-05-11 13:29           ` 伊泽 [this message]
2009-05-11 14:01             ` Michael Abbott
2009-05-11 14:15               ` Wolfram Sang

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=fd6b62c10905110629w6c9a641fr878351fb9217a32e@mail.gmail.com \
    --to=wxc200@gmail.com \
    --cc=broonie@sirena.org.uk \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@araneidae.co.uk \
    /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

all inboxes | Powered by JetHome®