All of lore.kernel.org
 help / color / mirror / Atom feed
From: tandrews@grok.co.za (Thomas Andrews)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Address configuration for scx200_acb
Date: Thu, 04 May 2006 06:32:05 +0000	[thread overview]
Message-ID: <20060504063205.GG19375@grok.co.za> (raw)
In-Reply-To: <20060427234114.941c9657.khali@linux-fr.org>

Hi Jim,

On Wed, May 03, 2006 at 11:24:23PM -0400, Jim Cromie wrote:

> This is premature, and hugely incomplete - (basically one observation)

Even so I really appreciate it! :)
 
> >+	// Select ACB0 (LDN 5)
> >+	outb(0x07,sio); // LDN select register
> >+	outb(0x05,val); // Choose LDN 5 ie ACCESS.bus 1
> >+	outb(0x60,sio); // Select I/O port 0 base addr
> >+	h1 = inb(val);
> >+	outb(0x61,sio);
> >+	l1 = inb(val);
> >  
> 
> please use these helper functions - lifted verbatim from another patch.
> These show up in various superio drivers in lm-sensors, consistency is good,
> and will help later if we need to mediate access to the SIO port,
> to share it amongst multiple drivers.
> 
> +
> +static inline void superio_outb(int reg, int val)
> +{
> +	outb(reg, SIO_REG_CIP);
> +	outb(val, SIO_REG_DIP);
> +}
> +
> +static inline int superio_inb(int reg)
> +{
> +	outb(reg, SIO_REG_CIP);
> +	return inb(SIO_REG_DIP);
> +}
> +
> +static inline void superio_select(int ldn)
> +{
> +	outb(SIO_VT1211_LDN, SIO_REG_CIP);
> +	outb(ldn, SIO_REG_DIP);
> +}
> +
> +static inline void superio_enter(void)
> +{
> +	outb(0x87, SIO_REG_CIP);
> +	outb(0x87, SIO_REG_CIP);
> +}
> +
> +static inline void superio_exit(void)
> +{
> +	outb(0xaa, SIO_REG_CIP);
> +}

I can't use those helper functions as is, because the whole purpose of
my patch is so that you can move away from using a #define for
SIO_REG_CIP. I'll write some equivalents for this module which use a
parameter instead.

> I havent actually checked, but it would be nice if you used the -p option
>   -p     Show which C function each change is in.

Thanks, I will use -p in future.

> and eventually, you'll probly need to do something about the nesting level.
> // and the c++ comments. :-(

I've changed all the comments to /* */ style.

Regards,
Thomas


  parent reply	other threads:[~2006-05-04  6:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 21:41 [lm-sensors] Address configuration for scx200_acb Jean Delvare
2006-04-28  6:47 ` Thomas Andrews
2006-04-30  7:43 ` Jean Delvare
2006-04-30 10:12 ` Thomas Andrews
2006-04-30 12:17 ` Jean Delvare
2006-05-01 11:15 ` Jim Cromie
2006-05-01 12:22 ` Jean Delvare
2006-05-01 13:58 ` Thomas Andrews
2006-05-01 15:12 ` Jim Cromie
2006-05-01 17:26 ` Thomas Andrews
2006-05-02 14:08 ` Alexander Krause
2006-05-03 11:17 ` Thomas Andrews
2006-05-03 11:39 ` Alexander Krause
2006-05-03 12:21 ` Thomas Andrews
2006-05-03 19:59 ` Thomas Andrews
2006-05-04  3:24 ` Jim Cromie
2006-05-04  6:32 ` Thomas Andrews [this message]
2006-05-10 18:36 ` Thomas Andrews
2006-06-09 21:28 ` Jim Cromie
2007-04-26 12:45 ` 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=20060504063205.GG19375@grok.co.za \
    --to=tandrews@grok.co.za \
    --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.