From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH 1/3] lm78: No longer use i2c-isa
Date: Mon, 19 Mar 2007 19:02:40 +0000 [thread overview]
Message-ID: <20070319200240.76d35d80.khali@linux-fr.org> (raw)
In-Reply-To: <20070319133231.b2a2a2a0.khali@linux-fr.org>
On Mon, 19 Mar 2007 15:20:46 +0100, Hans de Goede wrote:
> Jean Delvare wrote:
> > Contrary to the LM78 / W83781D, which were dedicated hardware
> > monitoring chips, the PC8374L is a Super-I/O, so it is very unlikely to
> > be ever found on a daughter board (while for example the W83781D was
> > used on graphics adapters). So it is rather unlikely that the ISA
> > (actually LPC) access will not be available. If I were you, I'd write
> > an ISA/LPC-only driver to start with, and only think of adding I2C
> > support later if really needed.
>
> Well unfortunately the person who brought PC8374L support up on the list and
> who is willing todo the testing for me has an intel motherboard and intel loves
> smbus, iow the hwmon logical device is disabled through the superio config
> registers, this doesn't actually disable the device, but does disable isa
> access, so I need to go i2c there, now I could force the logical device to on
> (assuming the config isn't locked by the bios) but that might interfere with
> any ACPI / other bios code accessing it (which doesn't seem to be the case but
> could be) and would require assigning ioports to it. To make things even more
> interesting the chip can be configured for memorymapped access too, now mmap
> access would be ideal, but as said I don't like the idea of changing the
> superio config. Thus the plan is to write a driver with supports all 3, and
> decides which one to use based on the superio config. This is actually easier
> then it sounds, because the only code that needs to take this into account is
> the probe code and the writebyte / readbyte functions.
>
> I'm also thinking about adding a force ioport / mmap io options, so that those
> modes can be actually tested.
>
> Any input/advice on this is much appreciated.
Your plan sounds good.
--
Jean Delvare
prev parent reply other threads:[~2007-03-19 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 12:32 [lm-sensors] [PATCH 1/3] lm78: No longer use i2c-isa Jean Delvare
2007-03-19 12:44 ` Hans de Goede
2007-03-19 14:02 ` Jean Delvare
2007-03-19 14:20 ` Hans de Goede
2007-03-19 19:02 ` Jean Delvare [this message]
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=20070319200240.76d35d80.khali@linux-fr.org \
--to=khali@linux-fr.org \
--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.