linux-kernel - Re: [PATCH 2.6.29.2] PXA I2C: Define log level for i2c PXA error report

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0905111314450.30347@venus.araneidae.co.uk>
Date:	Mon, 11 May 2009 13:16:38 +0100 (BST)
From:	Michael Abbott <michael@...neidae.co.uk>
To:	Mark Brown <broonie@...ena.org.uk>
cc:	???? <wxc200@...il.com>, linux-i2c@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2.6.29.2] PXA I2C: Define log level for i2c PXA error
 report

On Mon, 11 May 2009, Mark Brown wrote:
> 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 makes sense.

However, then, does it make sense for the PXA i2c bus prober to be calling 
the "scream blue murder" routine in this frankly routine case?  I guess it 
could just say "no device found at address xx"
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/