linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: CaT <cat@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-t1: i2c+sensors still whacky (hi Greg :)
Date: Tue, 15 Jul 2003 23:10:09 -0700	[thread overview]
Message-ID: <20030716061009.GA5037@kroah.com> (raw)
In-Reply-To: <20030716060443.GA784@zip.com.au>

On Wed, Jul 16, 2003 at 04:04:43PM +1000, CaT wrote:
> On Tue, Jul 15, 2003 at 09:11:27AM -0700, Greg KH wrote:
> > On Tue, Jul 15, 2003 at 07:07:27PM +1000, CaT wrote:
> > So, if you don't have any i2c code loaded, everything works?  How about
> 
> Yes.
> 
> > just loading the i2c driver and not the sensor driver?
> 
> All's fine.
> 
> > Oh, how about enabiling debugging in the i2c driver that you are using?
> 
> Well this is what I did:
> 
> 11 [15:53:38] root@theirongiant:/usr/src/linux/drivers/i2c>> grep 'define DEBUG' . -r
> ./i2c-core.c:#define DEBUG 1            /* needed to pick up the dev_dbg() calls */
> ./scx200_acb.c:#define DEBUG 0
> ./i2c-sensor.c:#define DEBUG 1
> ./i2c-algo-bit.c:/* #define DEBUG 1 */
> ./i2c-dev.c:#define DEBUG 1
> ./i2c-algo-pcf.c:/* #define DEBUG 1 */          /* to pick up dev_dbg calls */
> ./busses/i2c-amd756.c:/* #define DEBUG 1 */
> ./busses/i2c-ali15x3.c:/* #define DEBUG 1 */
> ./busses/i2c-i801.c:/* #define DEBUG 1 */
> ./busses/i2c-piix4.c:#define DEBUG 1
> ./busses/i2c-sis96x.c:/* #define DEBUG */
> ./busses/i2c-ali1535.c:/* #define DEBUG 1 */
> ./chips/adm1021.c:#define DEBUG 1
> ./chips/lm75.c:/* #define DEBUG 1 */
> 
> Did I do the right thing?

Looks good, but are you _really_ building all of those drivers into your
kernel?  Make them modules, that way booting will not require a small
nap :)

Then load only the i2c bus driver that you have.  See if that causes the
system to slow down, or cause any kernel log messages?

Only then try loading a i2c client driver, for your hardware.

Exactly what i2c hardware do you have anyway?

thanks,

greg k-h

  reply	other threads:[~2003-07-16  5:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15  9:07 CaT
2003-07-15 16:11 ` Greg KH
2003-07-16  6:04   ` CaT
2003-07-16  6:10     ` Greg KH [this message]
2003-07-16  6:29       ` CaT
2003-07-16  7:31         ` Greg KH
2003-07-16 22:47           ` CaT
2003-07-16 22:54             ` Greg KH
2003-07-17 15:33               ` 2.6.0-t1: i2c+sensors still whacky CaT
2003-07-18  2:33                 ` Greg KH
2003-07-21  7:37                   ` CaT
2003-07-21  7:58                     ` CaT

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=20030716061009.GA5037@kroah.com \
    --to=greg@kroah.com \
    --cc=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 2.6.0-t1: i2c+sensors still whacky (hi Greg :)' \
    /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

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).