public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Lanttor <lanttor.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: i2c adapter scan device issue
Date: Wed, 25 Nov 2009 09:53:31 +0100	[thread overview]
Message-ID: <20091125095331.5cbdbae6@hyperion.delvare> (raw)
In-Reply-To: <4B0CEDDA.2000909-KZfg59tc24xl57MIdRCFDg@public.gmane.org>

On Wed, 25 Nov 2009 16:42:02 +0800, Lanttor wrote:
> >
> > Yes, you are correct. You can't predefine I2C devices with
> > i2c_register_board_info() if you don't also set I2C adapter numbers
> > with i2c_add_numbered_adapter(). Trying would be equivalent to sending a
> > letter to someone when you know the city and street number but not the
> > street name: unlikely to succeed.
> >   
> Thanks Jean.
> 
> In fact my bus driver used i2c_add_adapter() not i2c_add_numbered_adapter().
> Now I use i2c_add_numbered_adapter() to replace 2c_add_adapter() and set
> the bus number first.
> 
> In one word, you mean that i2c_add_adapter() can not work normally if
> useing i2c_register_board_info() to pre-declare the i2c device, right?

Yes, exactly.

> I really need track i2c-stack in detail.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

      parent reply	other threads:[~2009-11-25  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25  4:18 i2c adapter scan device issue Lanttor
     [not found] ` <4B0CAFFD.7030603-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2009-11-25  8:12   ` Jean Delvare
     [not found]     ` <20091125091218.518d47af-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-11-25  8:42       ` Lanttor
     [not found]         ` <4B0CEDDA.2000909-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2009-11-25  8:53           ` Jean Delvare [this message]

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=20091125095331.5cbdbae6@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=lanttor.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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