From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [RFC][PATCH 1/2] powerpc/85xx: create dts components to build up an SoC
Date: Thu, 20 Oct 2011 16:05:36 -0500 [thread overview]
Message-ID: <4EA08D20.7010405@freescale.com> (raw)
In-Reply-To: <A54F7698-A96F-4EE1-89DB-B6A7C5A071FB@kernel.crashing.org>
Kumar Gala wrote:
>> > How about we put all serial devices into one pq3-duart.dtsi file, and
>> > let the parent dtsi file reference just the ones that it needs?
> there isn't an option to do that w/dtc
What about making all the nodes disabled by default, and then the soc.dtsi
or si.dtsi file can re-enable them?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-10-20 21:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 7:24 [RFC][PATCH 1/2] powerpc/85xx: create dts components to build up an SoC Kumar Gala
2011-10-20 7:24 ` Kumar Gala
2011-10-20 7:24 ` [RFC][PATCH 2/2] powerpc/85xx: Introduce a P1020 SoC device tree Kumar Gala
2011-10-20 7:24 ` Kumar Gala
2011-10-20 16:28 ` Tabi Timur-B04825
2011-10-20 16:28 ` Tabi Timur-B04825
2011-10-20 20:56 ` Kumar Gala
2011-10-20 20:56 ` Kumar Gala
2011-10-20 16:42 ` [RFC][PATCH 1/2] powerpc/85xx: create dts components to build up an SoC Tabi Timur-B04825
2011-10-20 16:42 ` Tabi Timur-B04825
2011-10-20 20:44 ` Kumar Gala
2011-10-20 20:44 ` Kumar Gala
2011-10-20 21:05 ` Timur Tabi [this message]
2011-10-21 3:03 ` Kumar Gala
2011-10-21 3:03 ` Kumar Gala
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=4EA08D20.7010405@freescale.com \
--to=timur@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.