Devicetree
 help / color / mirror / Atom feed
From: Jeremy Kerr <jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: [PATCH 04/11] arm-dt: Add ATAG_DEVTREE tag
Date: Tue, 22 Dec 2009 18:54:56 +0800	[thread overview]
Message-ID: <1261479296.246767.738000991632.4.gpush@pororo> (raw)
In-Reply-To: <1261479296.245235.191110925832.0.gpush@pororo>

We'd like to provide a pointer to the device tree blob through the atags
mechanism, so add a tag type containing a physical dtb pointer.

We won't need a parser for this, as we'll need to do the devtree parsing
a little earlier than other tags.

Signed-off-by: Jeremy Kerr <jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>

---
 arch/arm/include/asm/setup.h |    8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/arch/arm/include/asm/setup.h b/arch/arm/include/asm/setup.h
index 3fa2555..99ba6db 100644
--- a/arch/arm/include/asm/setup.h
+++ b/arch/arm/include/asm/setup.h
@@ -141,6 +141,13 @@ struct tag_memclk {
 	__u32 fmemclk;
 };
 
+/* OF device tree blob pointer */
+#define ATAG_DEVTREE	0x5441000a
+
+struct tag_devtree {
+	__u32 devtree;		/* physical address */
+};
+
 struct tag {
 	struct tag_header hdr;
 	union {
@@ -153,6 +160,7 @@ struct tag {
 		struct tag_revision	revision;
 		struct tag_videolfb	videolfb;
 		struct tag_cmdline	cmdline;
+		struct tag_devtree	devtree;
 
 		/*
 		 * Acorn specific

  parent reply	other threads:[~2009-12-22 10:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 10:54 [PATCH 00/11] Device-tree support for ARM Jeremy Kerr
2009-12-22 10:54 ` [PATCH 03/11] arm: export arm_add_memory Jeremy Kerr
2009-12-22 10:54 ` [PATCH 06/11] arm-dt: postpone machine detection until setup_arch with CONFIG_ARM_DEVTREE Jeremy Kerr
2010-01-04 16:36   ` Ben Dooks
     [not found]     ` <4B421903.4050200-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org>
2010-01-04 22:26       ` Jeremy Kerr
2009-12-22 10:54 ` [PATCH 09/11] arm-dt: probe for device-tree enabled platforms Jeremy Kerr
2009-12-22 10:54 ` [PATCH 10/11] arm-dt: parse initrd from device tree Jeremy Kerr
2009-12-22 10:54 ` [PATCH 07/11] arm-dt: parse devtree pointer on boot Jeremy Kerr
2009-12-22 10:54 ` [PATCH 01/11] arm: change command_line to cmd_line, and export it Jeremy Kerr
2009-12-22 10:54 ` [PATCH 02/11] arm: use generic infrastructure for early params Jeremy Kerr
2010-01-06 16:27   ` Russell King - ARM Linux
     [not found]     ` <20100106162731.GB1728-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2010-01-06 22:31       ` Jeremy Kerr
     [not found]         ` <201003060733.57636.rob@landley.net>
     [not found]           ` <201003060733.57636.rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
2010-03-06 16:01             ` Grant Likely
2009-12-22 10:54 ` Jeremy Kerr [this message]
2009-12-22 10:54 ` [PATCH 11/11] arm/versatile: probe via device tree Jeremy Kerr
2009-12-22 10:54 ` [PATCH 05/11] arm-dt: Add CONFIG_ARM_DEVTREE Jeremy Kerr
2009-12-22 10:54 ` [PATCH 08/11] arm-dt: parse memory info from DT Jeremy Kerr

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=1261479296.246767.738000991632.4.gpush@pororo \
    --to=jeremy.kerr-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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