public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Baurzhan Ismagulov <ibr-Y2X99Y6vBNTR7s880joybQ@public.gmane.org>
Cc: Jochen Friedrich <jochen-NIgtFMG+Po8@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: status of i2c-cpm and ds2482
Date: Sat, 9 Jan 2010 09:12:25 +0100	[thread overview]
Message-ID: <20100109091225.59746b62@hyperion.delvare> (raw)
In-Reply-To: <20100108231942.GA3699-Y2X99Y6vBNTR7s880joybQ@public.gmane.org>

Hi Baurzhan,

On Sat, 9 Jan 2010 00:19:43 +0100, Baurzhan Ismagulov wrote:
> On Fri, Jan 08, 2010 at 03:06:06PM +0100, Jochen Friedrich wrote:
> > 	I2C0: i2c@860 {
> ...
> > 		w1@aa {
> > 			reg = <0xaa>;
> > 			compatible = "dallas,ds2482";
> > 		};
> > 	};
> 
> This worked, thanks much Jochen and Jean!
> 
> I had to use "reg = <18>;", it didn't build with "0x".
> 
> FWIW, I've also tried restoring 0x18 in normal_i2c in ds2482.c, and
> i2c-core complained about quick not being supported.

Restoring? 0x18 has never been in ds2482's normal_i2c list.

> Where can I read about what it is?

As I2C doesn't offer any standard way to detect device presence at a
given address, we (ab)use the SMBus "Quick command" (0-byte message)
for this purpose. Not all adapters support this type of transaction.

> Why is it now required, whereas this worked in 2.6.25.7?

The i2c-cpm driver was not present in kernel 2.6.25.7, so you must have
been using an out-of-tree driver. Maybe that driver had (possibly fake)
support for the SMBus quick command.

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

  parent reply	other threads:[~2010-01-09  8:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08  2:02 status of i2c-cpm and ds2482 Baurzhan Ismagulov
     [not found] ` <20100108020253.GJ3388-Y2X99Y6vBNTR7s880joybQ@public.gmane.org>
2010-01-08 11:25   ` Jochen Friedrich
     [not found]     ` <4B471647.8050806-NIgtFMG+Po8@public.gmane.org>
2010-01-08 12:17       ` Baurzhan Ismagulov
     [not found]         ` <20100108121723.GD4004-Y2X99Y6vBNTR7s880joybQ@public.gmane.org>
2010-01-08 12:36           ` Jochen Friedrich
     [not found]             ` <4B4726CF.9020605-NIgtFMG+Po8@public.gmane.org>
2010-01-08 13:43               ` Baurzhan Ismagulov
2010-01-08 12:52           ` Jean Delvare
     [not found]             ` <20100108135222.49d7b834-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2010-01-08 14:01               ` Baurzhan Ismagulov
     [not found]                 ` <20100108140111.GF4004-Y2X99Y6vBNTR7s880joybQ@public.gmane.org>
2010-01-08 14:06                   ` Jochen Friedrich
     [not found]                     ` <4B473BCE.8060803-NIgtFMG+Po8@public.gmane.org>
2010-01-08 23:19                       ` Baurzhan Ismagulov
     [not found]                         ` <20100108231942.GA3699-Y2X99Y6vBNTR7s880joybQ@public.gmane.org>
2010-01-09  8:12                           ` Jean Delvare [this message]
2010-01-08 14:11                   ` Jochen Friedrich
2010-01-08 17:54                   ` Jean Delvare

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=20100109091225.59746b62@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=ibr-Y2X99Y6vBNTR7s880joybQ@public.gmane.org \
    --cc=jochen-NIgtFMG+Po8@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