From: Scott Wood <scottwood@freescale.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Heiko Schocher <hs@denx.de>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] 8xx: Add support for the MPC852 based board from keymile.
Date: Tue, 18 Mar 2008 11:56:37 -0500 [thread overview]
Message-ID: <47DFF445.20708@freescale.com> (raw)
In-Reply-To: <20080318161957.766A124349@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Scott,
>
> in message <20080318151132.GA17402@ld0162-tx32.am.freescale.net> you wrote:
>> Well, the device tree is a mechanism for communicating from the firmware
>> to the kernel, and if we could control the firmware better we'd just make
>> it set the pins properly to begin with. :-)
>
> Is this just a comment, or do you oppose Heiko's suggestion?
It was intended more as a gentle nudge to set up the pins in firmware
when not constrained by existing firmwares in the field that must be
supported.
> Other uses of the device tree seem possible and reasonable, too. For
> example, we can use the device tree to configure the firmware (U-Boot
> in this case).
>
> Using the device tree to describe the pin configuration of the
> hardware sounds easier to me than hard-coding it in some source (or
> header) file - no matter if this is in the kernel and/or in the
> firmware.
>
> What do you think?
I'm fine with putting it in the device tree for firmware's benefit,
though I'm not sure I fully agree with the "easier" bit until we get
support for expressions and named constants in dts, so that the flags
would be less opaque.
-Scott
next prev parent reply other threads:[~2008-03-18 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 9:24 [PATCH v2] 8xx: Add support for the MPC852 based board from keymile Heiko Schocher
2008-03-14 23:25 ` Stephen Rothwell
2008-03-18 7:13 ` Heiko Schocher
2008-03-18 7:33 ` Stephen Rothwell
2008-03-18 8:04 ` Heiko Schocher
2008-03-18 15:11 ` Scott Wood
2008-03-18 16:19 ` Wolfgang Denk
2008-03-18 16:56 ` Scott Wood [this message]
2008-03-18 16:19 ` Vitaly Bordug
2008-03-19 6:51 ` Heiko Schocher
2008-03-17 22:46 ` Scott Wood
2008-03-18 8:07 ` [PATCH v3] " Heiko Schocher
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=47DFF445.20708@freescale.com \
--to=scottwood@freescale.com \
--cc=hs@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=wd@denx.de \
/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).