All of lore.kernel.org
 help / color / mirror / Atom feed
From: jonsmirl@gmail.com (Jon Smirl)
To: Michael Hunold <hunold-ml@web.de>
Cc: Greg KH <greg@kroah.com>, Michael Hunold <hunold@linuxtv.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	sensors@stimpy.netroedge.com
Subject: [PATCH][2.6] Add command function to struct i2c_adapter
Date: Thu, 19 May 2005 06:25:16 +0000	[thread overview]
Message-ID: <9e4733910409211039273d5a2f@mail.gmail.com> (raw)
In-Reply-To: <41506099.8000307@web.de>

There is a related I2C problem with EEPROMs and DDC monitors. DDC
monitors look just like EEPROMs, the EEPROM driver can even read most
of them. But there are DDC monitors that need special wakeup sequences
before their ROMs will appear.

EEPROM and DDC are both algo_bit clients. When you attach a bus to
algo_bit both clients will run. There is concern that sending the
special DDC wake up sequence down non-DDC buses might mess up the bus.

A proposal was made to implement different classes of algo_bit clients
but this was never implemented. Would a class solution help with the
dvb problem too?


-- 
Jon Smirl
jonsmirl@gmail.com

WARNING: multiple messages have this Message-ID (diff)
From: Jon Smirl <jonsmirl@gmail.com>
To: Michael Hunold <hunold-ml@web.de>
Cc: Greg KH <greg@kroah.com>, Michael Hunold <hunold@linuxtv.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	sensors@stimpy.netroedge.com
Subject: Re: [PATCH][2.6] Add command function to struct i2c_adapter
Date: Tue, 21 Sep 2004 13:39:33 -0400	[thread overview]
Message-ID: <9e4733910409211039273d5a2f@mail.gmail.com> (raw)
In-Reply-To: <41506099.8000307@web.de>

There is a related I2C problem with EEPROMs and DDC monitors. DDC
monitors look just like EEPROMs, the EEPROM driver can even read most
of them. But there are DDC monitors that need special wakeup sequences
before their ROMs will appear.

EEPROM and DDC are both algo_bit clients. When you attach a bus to
algo_bit both clients will run. There is concern that sending the
special DDC wake up sequence down non-DDC buses might mess up the bus.

A proposal was made to implement different classes of algo_bit clients
but this was never implemented. Would a class solution help with the
dvb problem too?


-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 17:19 [PATCH][2.6] Add command function to struct i2c_adapter Michael Hunold
2004-09-21 15:41 ` Greg KH
2005-05-19  6:25   ` Greg KH
2004-09-21 17:10   ` Michael Hunold
2005-05-19  6:25     ` Michael Hunold
2004-09-21 17:39     ` Jon Smirl [this message]
2005-05-19  6:25       ` Jon Smirl
2004-09-21 18:05       ` Michael Hunold
2005-05-19  6:25         ` Michael Hunold
2004-09-22  8:56         ` Adrian Cox
2005-05-19  6:25           ` Adrian Cox
2004-09-22 12:08           ` Jean Delvare
2005-05-19  6:25             ` Jean Delvare
2004-09-22 11:54             ` Adrian Cox
2005-05-19  6:25               ` Adrian Cox
2004-09-22 13:38               ` Jean Delvare
2005-05-19  6:25                 ` Jean Delvare
2004-09-22 13:13                 ` Adrian Cox
2005-05-19  6:25                   ` Adrian Cox
2004-09-22 15:40                 ` Jon Smirl
2005-05-19  6:25                   ` Jon Smirl
2004-09-22 15:56                   ` Adrian Cox
2005-05-19  6:25                     ` Adrian Cox
2004-09-22 16:07                     ` Jon Smirl
2005-05-19  6:25                       ` Jon Smirl
2004-09-22 16:51                       ` Adrian Cox
2005-05-19  6:25                         ` Adrian Cox
2004-09-22 17:17                         ` Jon Smirl
2005-05-19  6:25                           ` Jon Smirl
2004-09-22 18:55                         ` Jean Delvare
2005-05-19  6:25                           ` Jean Delvare
2004-09-22 18:32                 ` Adrian Cox
2005-05-19  6:25                   ` Adrian Cox
2004-09-22 20:04                   ` Mark M. Hoffman
2005-05-19  6:25                     ` Mark M. Hoffman
2004-09-23  7:41                   ` Michael Hunold
2005-05-19  6:25                     ` Michael Hunold
2004-09-23  7:48                   ` Michael Hunold
2005-05-19  6:25                     ` Michael Hunold
2004-09-23  7:09               ` Michael Hunold
2005-05-19  6:25                 ` Michael Hunold
2004-09-23 20:18                 ` Adrian Cox
2005-05-19  6:25                   ` Adrian Cox
2004-09-21 20:33       ` Jean Delvare
2005-05-19  6:25         ` Jean Delvare
2004-09-21 21:02         ` Jon Smirl
2005-05-19  6:25           ` Jon Smirl
2004-09-24 17:06   ` Michael Hunold
2005-05-19  6:25     ` Michael Hunold
2004-09-24 18:05     ` Jean Delvare
2005-05-19  6:25       ` Jean Delvare
2004-09-24 20:21       ` Michael Hunold
2005-05-19  6:25         ` Michael Hunold
2004-10-01  6:52         ` Greg KH
2005-05-19  6:25           ` Greg KH
2004-10-01 12:22           ` Adrian Cox
2005-05-19  6:25             ` Adrian Cox
2004-10-01 13:57             ` Jean Delvare
2005-05-19  6:25               ` Jean Delvare
2004-10-01 23:41             ` Greg KH
2005-05-19  6:25               ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2005-05-19  6:25 [Fwd: [PATCH][2.6] Add command function to struct i2c_adapter] Michael Hunold
2004-09-21 13:28 ` [PATCH][2.6] Add command function to struct i2c_adapter Jean Delvare
2005-05-19  6:25   ` Jean Delvare
2004-09-21 14:38   ` Michael Hunold
2005-05-19  6:25     ` Michael Hunold

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=9e4733910409211039273d5a2f@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=hunold-ml@web.de \
    --cc=hunold@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@stimpy.netroedge.com \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.