All of lore.kernel.org
 help / color / mirror / Atom feed
From: mhoffman@lightlink.com (Mark M. Hoffman)
To: lm-sensors@vger.kernel.org
Subject: Call for 2.9.0
Date: Thu, 19 May 2005 06:25:26 +0000	[thread overview]
Message-ID: <20041209173235.GD3775@jupiter.solarsys.private> (raw)
In-Reply-To: <20041208224836.7794b56c.khali@linux-fr.org>

Hi Mark:

(cc'ed Brian also)

* Mark D. Studebaker <mds4@verizon.net> [2004-12-09 11:01:36 -0500]:
> What Brian discovered is that an i2c bus mux implementation requires a 
> nolock version
> of some functions. Think about how the bootstrap works:
> 	Bus gets added
> 	Mux chip found
> 	Sub busses get added (but can't because lock still held - hang)
> So that's what the (first half of) i2c-core patch does. Get rid of the 
> leading '__', rename to xxx_nolock,
> and export them so that the virtual driver can implement the bootstrap.
> 
> It's not a big change. Maybe there's a way to avoid it, though... I don't 
> know.

Well... why can't you do the sub-bus creation in pca954x_attach_adapter()
(after the call to i2c_detect) ?  This gets rid of all the locking problems,
and IMHO makes more sense w.r.t. the respective function names anyway.

Regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:25 Call for 2.9.0 Jean Delvare
2005-05-19  6:25 ` Mark Studebaker
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Mark Studebaker
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Mark M. Hoffman [this message]
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Philip Edelbrock
2005-05-19  6:25 ` Mark Studebaker
2005-05-19  6:25 ` Philip Pokorny
2005-05-19  6:25 ` 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=20041209173235.GD3775@jupiter.solarsys.private \
    --to=mhoffman@lightlink.com \
    --cc=lm-sensors@vger.kernel.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.