From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Andrew Paprocki" <andrew@ishiboo.com>
Cc: linux-kernel@vger.kernel.org, "Jorge Boncompte" <jorge@dti2.net>,
"Jean Delvare" <khali@linux-fr.org>,
"Chris Gauthron" <chrisg@0-in.com>
Subject: Re: I/O collisions w/ hwmon/it87.c and watchdog/it8712f_wdt.c? (Super I/O chips in general..)
Date: Sun, 10 Feb 2008 23:05:38 +0000 [thread overview]
Message-ID: <20080210230538.3f5743f6@core> (raw)
In-Reply-To: <76366b180802101304j359e2873vd9dd974920bf6745@mail.gmail.com>
> Since these chips touch many different parts of traditionally separate
> driver areas, how should the drivers be structured so that they can
> all talk to the chip? Should the low level communications routines for
> the chip live in a library which all the drivers could use?
Probably yes. And that if possible should manage all the locking. Thats
roughly how the majority of drivers do it. Some export the lock from base
code and inline the accessors depending how complex it is.
next prev parent reply other threads:[~2008-02-10 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 21:04 I/O collisions w/ hwmon/it87.c and watchdog/it8712f_wdt.c? (Super I/O chips in general..) Andrew Paprocki
2008-02-10 23:05 ` Alan Cox [this message]
2008-02-10 23:32 ` Andrew Paprocki
2008-02-11 8:40 ` 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=20080210230538.3f5743f6@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andrew@ishiboo.com \
--cc=chrisg@0-in.com \
--cc=jorge@dti2.net \
--cc=khali@linux-fr.org \
--cc=linux-kernel@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.