From: Wade Farnsworth <wfarnsworth@mvista.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] Fix the LPC47M192 SuperIO on the MPC8641 HPCN
Date: Thu, 07 Jun 2007 09:04:36 -0700 [thread overview]
Message-ID: <1181232276.5674.146.camel@rhino> (raw)
In-Reply-To: <200706070039.51541.arnd@arndb.de>
On Thu, 2007-06-07 at 00:39 +0200, Arnd Bergmann wrote:
> On Wednesday 06 June 2007, Wade Farnsworth wrote:
> > + /* LPC47M192 Super I/O configuration */
> > + outb(0x55, 0x4e); /* enter superio config mode */
> > +
> > + /* Enable keyboard and mouse */
> > + outb(0x07, 0x4e); /* device selector register */
> > + outb(0x07, 0x4f); /* select keyboard registers (device 7) */
> > + outb(0x30, 0x4e); /* keyboard activation register */
> > + outb(0x01, 0x4f); /* activate keyboard */
>
> Hardcoded I/O port numbers always worry me a little. I know that this is
> supposed to work in general, but can't you read the I/O port range from
> a device tree property?
I suppose I could create a device node for the Super I/O config
registers and use those instead of hardcoding it here.
Something to the effect of:
superio_cfg@4e {
reg = <1 4e 2>;
compatible = "smsc-lpc47m192-cfg";
};
I'm not sure if the name and compatible properties are appropriate
though. Any recommendations?
--Wade
next prev parent reply other threads:[~2007-06-07 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 16:30 [PATCH] Fix the LPC47M192 SuperIO on the MPC8641 HPCN Wade Farnsworth
2007-06-06 22:39 ` Arnd Bergmann
2007-06-07 13:03 ` Segher Boessenkool
2007-06-07 16:04 ` Wade Farnsworth [this message]
2007-06-07 16:35 ` Segher Boessenkool
2007-06-07 16:51 ` Wade Farnsworth
2007-06-07 17:05 ` Segher Boessenkool
2007-06-07 20:01 ` Andy Fleming
2007-06-08 8:22 ` Segher Boessenkool
2007-06-07 13:01 ` Segher Boessenkool
2007-06-07 16:42 ` Wade Farnsworth
2007-06-07 17:04 ` Segher Boessenkool
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=1181232276.5674.146.camel@rhino \
--to=wfarnsworth@mvista.com \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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.