From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
LM Sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [ patch .24-rc0 0/5 ] SuperIO locks coordinator
Date: Mon, 15 Oct 2007 06:56:22 +0000 [thread overview]
Message-ID: <47130F16.3000706@hhs.nl> (raw)
In-Reply-To: <4712F4D4.4050707@gmail.com>
Jim Cromie wrote:
> this patchset (on hwmon-git) re-introduces superio_locks module,
> previously RFC'd here, where I 'borrowed' another thread..
>
> http://marc.info/?l=linux-kernel&m\x115821759424601&w=2
>
> The module shares out slots/shared-reservations containing
> a mutex, so that multiple modules can coordinate access to
> the sio-port.
>
> Im crossposting - LKML for more reviewers, lm-sensors for
> folks with the hardware and (perhaps) more interest.
>
> If its not too late, please consider for 2.6.24-rc0
>
> 01 - adds superio_locks module
>
> User-drivers specify the sio-port characteristics they can support
> device-ids, sio-port-addrs, enter & exit sequences, etc in
> a struct superio_search (in __devinit, preferably).
>
> superio_find() then searches existing slots/shared-reservations
> for a matching sio-port, and returns it if found.
> Otherwize it probes port-addrs, specified by find() user,
> and makes and returns a new reservation.
>
> superio_find() finds and reserves the slot,
> returned as ptr or null
> superio_release() relinguishes the slot (ref-counted)
>
> Once theyve got the reservation in struct superio * gate
> (as named in patches 2-5) they *may* use
>
> superio_lock(gate)
> superio_enter/exit(gate)
> superio_inb/w(gate, regaddr),
> superio_outb/w(gate, regaddr, val)
>
> or they can do it themselves with inb/outb, by using gate->sioaddr, etc.
>
<snip>
>
> - Hans, I think Ive added all your suggestions, thanks.
>
Your welcome, at a first look over things look pretty sane now. I'm willing to
do a full review of this, but first I would like to see some more input from
others.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
LM Sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [ patch .24-rc0 0/5 ] SuperIO locks coordinator
Date: Mon, 15 Oct 2007 08:56:22 +0200 [thread overview]
Message-ID: <47130F16.3000706@hhs.nl> (raw)
In-Reply-To: <4712F4D4.4050707@gmail.com>
Jim Cromie wrote:
> this patchset (on hwmon-git) re-introduces superio_locks module,
> previously RFC'd here, where I 'borrowed' another thread..
>
> http://marc.info/?l=linux-kernel&m=115821759424601&w=2
>
> The module shares out slots/shared-reservations containing
> a mutex, so that multiple modules can coordinate access to
> the sio-port.
>
> Im crossposting - LKML for more reviewers, lm-sensors for
> folks with the hardware and (perhaps) more interest.
>
> If its not too late, please consider for 2.6.24-rc0
>
> 01 - adds superio_locks module
>
> User-drivers specify the sio-port characteristics they can support
> device-ids, sio-port-addrs, enter & exit sequences, etc in
> a struct superio_search (in __devinit, preferably).
>
> superio_find() then searches existing slots/shared-reservations
> for a matching sio-port, and returns it if found.
> Otherwize it probes port-addrs, specified by find() user,
> and makes and returns a new reservation.
>
> superio_find() finds and reserves the slot,
> returned as ptr or null
> superio_release() relinguishes the slot (ref-counted)
>
> Once theyve got the reservation in struct superio * gate
> (as named in patches 2-5) they *may* use
>
> superio_lock(gate)
> superio_enter/exit(gate)
> superio_inb/w(gate, regaddr),
> superio_outb/w(gate, regaddr, val)
>
> or they can do it themselves with inb/outb, by using gate->sioaddr, etc.
>
<snip>
>
> - Hans, I think Ive added all your suggestions, thanks.
>
Your welcome, at a first look over things look pretty sane now. I'm willing to
do a full review of this, but first I would like to see some more input from
others.
Regards,
Hans
next prev parent reply other threads:[~2007-10-15 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 5:04 [lm-sensors] [ patch .24-rc0 0/5 ] SuperIO locks coordinator Jim Cromie
2007-10-15 5:04 ` Jim Cromie
2007-10-15 6:56 ` Hans de Goede [this message]
2007-10-15 6:56 ` [lm-sensors] " Hans de Goede
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=47130F16.3000706@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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.