From: Wade Farnsworth <wfarnsworth@mvista.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
Jon Loeliger <jdl@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] Fix the LPC47M192 SuperIO on the MPC8641 HPCN
Date: Thu, 07 Jun 2007 09:51:24 -0700 [thread overview]
Message-ID: <1181235084.5674.190.camel@rhino> (raw)
In-Reply-To: <63ff9dee6b212cc7908c8e1b73920ea6@kernel.crashing.org>
On Thu, 2007-06-07 at 18:35 +0200, Segher Boessenkool wrote:
> >> 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.
>
> I'd just hide it all, do this setup in the firmware,
> where it belongs, and don't expose the superio config
> in the device tree.
That's a valid point. This probably could (should?) be handled by
U-boot.
Jon, or others do you have any opinions on this?
>
> > 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?
>
> "superio" and "smsc,lpc47m192" I'd say. You also
> then should link the logical devices on the superio
> to the device nodes that represent those. I'm not
> sure this is all worth it, this is low-level setup
> the firmware should do and everything else can treat
> it as a black box.
OK, if we decide to keep this, I'll use those instead.
Thanks.
--Wade
next prev parent reply other threads:[~2007-06-07 16:51 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
2007-06-07 16:35 ` Segher Boessenkool
2007-06-07 16:51 ` Wade Farnsworth [this message]
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=1181235084.5674.190.camel@rhino \
--to=wfarnsworth@mvista.com \
--cc=arnd@arndb.de \
--cc=jdl@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).