Linux I2C development
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Wen Wang <sickdoctor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: Question about i2c new style modle
Date: Sun, 12 Oct 2008 09:57:15 +0200	[thread overview]
Message-ID: <20081012075715.GA26683@pengutronix.de> (raw)
In-Reply-To: <56458e0810112335r529622dei4c6891465c6fdf88-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 990 bytes --]

Hello Wen,

On Sun, Oct 12, 2008 at 02:35:49PM +0800, Wen Wang wrote:

>    Can anyone please help to tell me if I have to upgrade my I2C client
>    driver from legacy binding model to new style binding model in 2.6.27
>    kernel or not?

It is not required yet, but it is always a good idea to move to the new
binding (which will be required somewhen, nevertheless).

>    If I have to :(, I don't know which part of code will
>    update the board info about I2C devices or this should be done by the
>    client driver?

I am not sure if I understood what you meant with "updating the board
info". You supply i2c_board_info in your board init code and when the
i2c adapter is initialized, it will call the client drivers
probe-function. Maybe the guide in Documentation/i2c/upgrading-clients
will further help you?

All the best,

   Wolfram

-- 
  Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

  parent reply	other threads:[~2008-10-12  7:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-12  6:35 Question about i2c new style modle Wen Wang
     [not found] ` <56458e0810112335r529622dei4c6891465c6fdf88-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-12  7:57   ` Wolfram Sang [this message]
     [not found]     ` <20081012075715.GA26683-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-10-12 11:52       ` Wen Wang
     [not found]         ` <56458e0810120452n2def8400n883ad46d0440e779-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-12 13:00           ` 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=20081012075715.GA26683@pengutronix.de \
    --to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
    --cc=sickdoctor-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