linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm/mx5: parse iomuxc pad configuratoin from device tree
Date: Fri, 5 Aug 2011 13:36:29 -0700	[thread overview]
Message-ID: <20110805203629.GB6991@huya.qualcomm.com> (raw)
In-Reply-To: <4E3C51F5.50707@freescale.com>

On Fri, Aug 05, 2011 at 03:26:29PM -0500, Scott Wood wrote:

> > Yes, it puts the onus of the work on the firmware guys, but they're
> > the ones writing the device trees for their hardware anyway.
> 
> Sometimes.

I'm not even sure that is going to be common.  At least our setup is
going to have the device tree living in flash somewhere.  The
bootloader only knows enough about the FDT to insert arguments and
memory information into it.  They certainly aren't the appropriate
team to be defining the device tree.

David


-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2011-08-05 20:36 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
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 [this message]
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=20110805203629.GB6991@huya.qualcomm.com \
    --to=davidb@codeaurora.org \
    --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).