devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas KANDAGATLA <srinivas.kandagatla@st.com>
To: David Gibson <dwg@au1.ibm.com>
Cc: linux-kbuild@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org, mmarek@suse.cz,
	B04825@freescale.com
Subject: Re: [RFC:PATCH 3.6.0-rc1] dtc: Add -P option to dtc for Pre-Processing.
Date: Wed, 15 Aug 2012 10:33:04 +0100	[thread overview]
Message-ID: <502B6CD0.4060102@st.com> (raw)
In-Reply-To: <20120815011149.GF8136@truffula.fritz.box>

On 15/08/12 02:11, David Gibson wrote:
> On Mon, Aug 13, 2012 at 09:01:53AM +0100, Srinivas KANDAGATLA wrote:
>> From: Srinivas Kandagatla <srinivas.kandagatla@st.com>
>>
>> This patch add pre-processing capablity to dtc based on status property.
>> Now the dtc has additional option -P to enable Pre-processing based on
>> status property.
>>
>> The SOCS have lot of device tree infrastructure files which mark the
>> device nodes as disabled and the board level device tree enables them if
>> required. However while creating device tree blob, the compiler can
>> preprocess the nodes and exclude nodes marked as disabled, doing this
>> way will reduce the size of device tree blob.
>>
>> In our case this has reduced the blob size from 29K to 15K.
>>
>> Also nodes with status="disabled" is are never probed by dt platform bus
>> code.
>>
>> Again, Preprocessing is optional parameter to dtc.
> Hrm.
>
> 1) Changes to dtc should be made first against upstream dtc at
> git://git.jdl.com/software/dtc.git.  The version in the kernel is just
> a snapshot of the upstream tree which is updated periodically.
I agree, will re-base the patch against
git://git.jdl.com/software/dtc.git and add Jon Loeliger (dtc maintainer)
to CC.
> 2) I'm not convinced this filtering-by-status is something that
> belongs in dtc, but I'm willing to be persuaded.
As its not a default dtc behavior, Adding filtering-by-status as
optional to dtc would a good addition towards reducing overall dtb sizes.
>
> 3) The name has to change.  "preprocess" is far to general a term for
> the very specific function you're implementing here.  Especially when
> there are serious discussions ongoing about having dtc use cpp or a
> similar preprocessor in a general capacity.
Yes, Pre-process looks very generic, As Tabi suggested --strip-disabled
would be more appropriate.
Will repost the patch with this change.
>


      parent reply	other threads:[~2012-08-15  9:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13  8:01 [RFC:PATCH 3.6.0-rc1] dtc: Add -P option to dtc for Pre-Processing Srinivas KANDAGATLA
2012-08-15  1:11 ` David Gibson
2012-08-15  2:12   ` Tabi Timur-B04825
2012-08-15  9:49     ` Srinivas KANDAGATLA
     [not found]       ` <502B70B8.1030709-qxv4g6HH51o@public.gmane.org>
2012-08-15 11:29         ` David Gibson
2012-08-15 16:00           ` Mitch Bradley
2012-08-15 12:04       ` Tabi Timur-B04825
2012-08-15  9:33   ` Srinivas KANDAGATLA [this message]

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=502B6CD0.4060102@st.com \
    --to=srinivas.kandagatla@st.com \
    --cc=B04825@freescale.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dwg@au1.ibm.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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).