All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas KANDAGATLA <srinivas.kandagatla@st.com>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: David Gibson <dwg@au1.ibm.com>, "mmarek@suse.cz" <mmarek@suse.cz>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>
Subject: Re: [RFC:PATCH 3.6.0-rc1] dtc: Add -P option to dtc for Pre-Processing.
Date: Wed, 15 Aug 2012 10:49:44 +0100	[thread overview]
Message-ID: <502B70B8.1030709@st.com> (raw)
In-Reply-To: <CAOZdJXUxguEBJG44kyKH0NW1999a9OBj2M=DEhmf_uSYM6nGaQ@mail.gmail.com>

On 15/08/12 03:12, Tabi Timur-B04825 wrote:
> On Tue, Aug 14, 2012 at 8:11 PM, David Gibson <dwg@au1.ibm.com> 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.
> IMHO, many devices that are marked as "disabled" in the DTS are
> expecting to be enabled by the boot loader, so just because a node is
> disabled in the DTS does not mean that it will be disabled when Linux
> sees it.
Good to know that,
But some of the secured bootloaders like the one's we use don't even
touch the dt blob.
>
>>> In our case this has reduced the blob size from 29K to 15K.
> I don't see that as significant.
>
>>> Also nodes with status="disabled" is are never probed by dt platform bus
>>> code.
>>>
>>> Again, Preprocessing is optional parameter to dtc.
> Using this option would break a lot of our device trees.
As this is optional parameter, I did not expect it to break the
default/existing behavior.
Correct me am missing anything?
>   Perhaps it
> should be given a better name, like --strip-disabled.
Thanks for the advice. I agree, Will be reposting the patch making this
option as --strip-disabled with CC to Jon Loeliger (dtc maintainer).


  reply	other threads:[~2012-08-15 10:19 UTC|newest]

Thread overview: 9+ 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 [this message]
2012-08-15 11:29       ` David Gibson
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

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=502B70B8.1030709@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 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.