From: "Pádraig Brady" <P@draigBrady.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] w83627hf hardware sharing
Date: Thu, 12 Apr 2007 12:26:55 +0000 [thread overview]
Message-ID: <461E258F.2080409@draigBrady.com> (raw)
In-Reply-To: <20070412121527.GA3132@sirena.org.uk>
Mark Brown wrote:
> While looking at the w83627hf driver I noticed that there are currently
> two drivers in the kernel controlling these devices: w83627hf providing
> lm_sensors support and the w83627hf_wdt driver providing watchdog
> support. Due to the hardware interface provided by the chip with many
> functions multiplexed via two registers this can't be done safely:
> concurrent access. This is unlikely to happen at present but it is
> possible and I'm currently looking at an application which uses some
> additional functionality on the chip and would run into trouble much
> more readily.
>
> The most straightforward fix appears to be to provide a multiplexing
> driver for the chip. Does this sound like a reasonable approach to
> take? I'm particularly worried about the possible effects of changing
> the lm_sensors driver, causing the device to move in sysfs, though as
> far as I can tell current versions of lm-sensors should not be affected
> due to the sysfs class.
>
You're right.
Some work has been done wrt this, but I've not tried it:
http://marc.info/?l=linux-kernel&m\x115821759424601&w=2
cheers,
Pádraig.
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-04-12 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 12:15 [lm-sensors] w83627hf hardware sharing Mark Brown
2007-04-12 12:26 ` Pádraig Brady [this message]
2007-04-12 12:45 ` Mark Brown
2007-04-20 4:51 ` Jim Cromie
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=461E258F.2080409@draigBrady.com \
--to=p@draigbrady.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.