public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Chuck Kamas <ckamas-mizZ2TCXIxVBDgjK7y7TUQ@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: How to manually call i2c_client's probe from i2c-dev.c ioctl
Date: Thu, 17 Sep 2009 18:04:07 +0200	[thread overview]
Message-ID: <20090917180407.5460bf33@hyperion.delvare> (raw)
In-Reply-To: <C62896630644CE43BF64B0FF0AC27F0E1815EC-RKsfjrak5bi0VCHWTNMfawC/G2K4zDHf@public.gmane.org>

Hi Chuck,

On Thu, 17 Sep 2009 08:45:57 -0700, Chuck Kamas wrote:
> Thanks for the reply.  I see now that I was not clear.  In the patch
> that I mentioned, Michael used a call i2c_new_device(client->adapter,
> &bInfo).  This is from the new model.  What would be the equivalent call
> from the old model?  I.e. what function do I call so that a chip driver
> will issue a probe and if a chip is found it will be properly
> registered?

You keep referring to Michael's patch, while this patch was never
merged, for a reason.

Please let's start all over again. Michael's patch does not exist.
Trying to inject pieces of the new binding model into the old one will
never work, both models are simply too different.

What functional problem are you trying to solve? What's your platform,
what's your I2C bus, what's your I2C device, and which drivers are you
using?

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

  parent reply	other threads:[~2009-09-17 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 16:56 How to manually call i2c_client's probe from i2c-dev.c ioctl Chuck Kamas
     [not found] ` <C62896630644CE43BF64B0FF0AC27F0E18153F-RKsfjrak5bi0VCHWTNMfawC/G2K4zDHf@public.gmane.org>
2009-09-16 20:52   ` Jean Delvare
     [not found]     ` <20090916225247.2094619b-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-09-16 23:25       ` Chuck Kamas
     [not found]         ` <C62896630644CE43BF64B0FF0AC27F0E1815B9-RKsfjrak5bi0VCHWTNMfawC/G2K4zDHf@public.gmane.org>
2009-09-17  7:26           ` Jean Delvare
     [not found]             ` <20090917092612.53327f80-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-09-17 15:45               ` Chuck Kamas
     [not found]                 ` <C62896630644CE43BF64B0FF0AC27F0E1815EC-RKsfjrak5bi0VCHWTNMfawC/G2K4zDHf@public.gmane.org>
2009-09-17 16:04                   ` Jean Delvare [this message]
     [not found]                     ` <20090917180407.5460bf33-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-09-17 16:38                       ` Chuck Kamas

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=20090917180407.5460bf33@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=ckamas-mizZ2TCXIxVBDgjK7y7TUQ@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