From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm/mx5: parse iomuxc pad configuratoin from device tree
Date: Sat, 30 Jul 2011 22:02:15 -0600 [thread overview]
Message-ID: <20110731040215.GJ24334@ponder.secretlab.ca> (raw)
In-Reply-To: <20110726024354.GI21641@S2100-06.ap.freescale.net>
On Tue, Jul 26, 2011 at 10:43:55AM +0800, Shawn Guo wrote:
> On Mon, Jul 25, 2011 at 02:46:30PM -0600, Grant Likely wrote:
> > On Mon, Jul 25, 2011 at 11:07:46PM +0800, Shawn Guo wrote:
> > The current linux code has each pin config simply a u64. Now, an
> > engineer certainly wouldn't be asked to write raw u64 values, but we
> > could add some form of #define or macro syntax to dtc so that the
> > symbolic names currently used in the board.c file would continue to
> > work.
>
> I was told that the binding should not be bonded to Linux
> implementation. Now I'm told to go the opposite direction? ;)
Nope; it's perfectly valid to use the current Linux implementation for
inspiration, since a real implementation can be proven to actually
/work/. :-) However, the binding must be documented from the
perspective of how the hardware works, not from the perspective of
what Linux currently wants.
g.
next prev parent reply other threads:[~2011-07-31 4:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 15:07 [PATCH 0/2] Add device tree support for i.mx53 boards Shawn Guo
2011-07-25 15:07 ` [PATCH 1/2] arm/mx5: parse iomuxc pad configuratoin from device tree Shawn Guo
2011-07-25 20:46 ` Grant Likely
2011-07-26 2:43 ` Shawn Guo
2011-07-26 6:29 ` Sascha Hauer
2011-07-26 16:34 ` Shawn Guo
2011-07-31 4:02 ` Grant Likely [this message]
2011-07-26 11:19 ` Eric Miao
2011-08-04 23:07 ` Matt Sealey
2011-08-05 7:07 ` David Brown
2011-08-05 18:36 ` Matt Sealey
2011-08-05 20:26 ` Scott Wood
2011-08-05 20:36 ` David Brown
2011-08-05 21:29 ` Matt Sealey
2011-08-05 21:48 ` Scott Wood
2011-08-06 17:41 ` Grant Likely
2011-08-07 16:23 ` Russell King - ARM Linux
2011-08-05 22:58 ` Grant Likely
2011-08-05 23:31 ` Mitch Bradley
2011-08-06 3:47 ` Mark Brown
2011-08-07 11:15 ` Sascha Hauer
2011-07-26 6:31 ` Sascha Hauer
2011-07-26 16:39 ` Shawn Guo
2011-07-26 6:39 ` Sascha Hauer
2011-07-26 16:41 ` Shawn Guo
2011-07-25 15:07 ` [PATCH 2/2] arm/mx5: add device tree support for imx53 boards Shawn Guo
2011-07-25 20:57 ` Grant Likely
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=20110731040215.GJ24334@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.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).