From: Mark Brown <broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
To: Michael Abbott <michael-W/Bzo8D1sxa8qtKVGud/9w@public.gmane.org>
Cc: ???? <wxc200-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 2.6.29.2] PXA I2C: Define log level for i2c PXA error report
Date: Mon, 11 May 2009 12:28:01 +0100 [thread overview]
Message-ID: <20090511112801.GA20283@sirena.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0905111126020.20970-EMtNTEpPrk39UE2ag0LVtCp2UmYkHbXO@public.gmane.org>
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.
next prev parent reply other threads:[~2009-05-11 11:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 7:32 [PATCH 2.6.29.2] PXA I2C: Define log level for i2c PXA error report Michael Abbott
[not found] ` <Pine.LNX.4.64.0905060829580.24668-EMtNTEpPrk39UE2ag0LVtCp2UmYkHbXO@public.gmane.org>
2009-05-06 8:22 ` Jean Delvare
[not found] ` <20090506102202.73d6045d-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-05-11 6:38 ` Michael Abbott
[not found] ` <Pine.LNX.4.64.0905081102060.14384-EMtNTEpPrk39UE2ag0LVtCp2UmYkHbXO@public.gmane.org>
2009-05-11 8:56 ` Jean Delvare
2009-05-11 10:11 ` 伊泽
[not found] ` <fd6b62c10905110311w6350828tf90d9c699b73fe30-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-11 10:31 ` Michael Abbott
[not found] ` <Pine.LNX.4.64.0905111126020.20970-EMtNTEpPrk39UE2ag0LVtCp2UmYkHbXO@public.gmane.org>
2009-05-11 11:28 ` Mark Brown [this message]
[not found] ` <20090511112801.GA20283-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2009-05-11 12:16 ` Michael Abbott
[not found] ` <Pine.LNX.4.64.0905111314450.30347-EMtNTEpPrk39UE2ag0LVtCp2UmYkHbXO@public.gmane.org>
2009-05-11 12:23 ` Mark Brown
2009-05-11 13:29 ` 伊泽
[not found] ` <fd6b62c10905110629w6c9a641fr878351fb9217a32e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-11 14:01 ` Michael Abbott
[not found] ` <Pine.LNX.4.64.0905111458290.6308-EMtNTEpPrk39UE2ag0LVtCp2UmYkHbXO@public.gmane.org>
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=20090511112801.GA20283@sirena.org.uk \
--to=broonie-gfdadszt00ze9xe1eozjha@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michael-W/Bzo8D1sxa8qtKVGud/9w@public.gmane.org \
--cc=wxc200-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).