All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
To: Tabi Timur-B04825 <B04825-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: "mmarek-AlSwsSmVLrQ@public.gmane.org"
	<mmarek-AlSwsSmVLrQ@public.gmane.org>,
	Wood Scott-B07421
	<B07421-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
	"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
	David Gibson <dwg-8fk3Idey6ehBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [RFC:PATCH dtc-1.3.0] dtc: Add --strip-disabled option to dtc.
Date: Mon, 20 Aug 2012 07:16:17 -1000	[thread overview]
Message-ID: <503270E1.6050902@firmworks.com> (raw)
In-Reply-To: <50322F9C.2070403-KZfg59tc24xl57MIdRCFDg@public.gmane.org>

On 8/20/2012 2:37 AM, Tabi Timur-B04825 wrote:
> Srinivas KANDAGATLA wrote:
>>>> But assuming that this really is the best approach, then it would make
>>>> sense for --strip-disabled to leave this node in the dtb, because
>>>> otherwise there would be no way to re-enable it.
>> --strip-disabled should still get rid for nodes marked as failed
>> as-well, because fail means something serious and un-recoverable.
> 
> Well, I don't know if that's true.  Does status=fail really mean 
> unrecoverable?

My intention when I first conceived of the status property is that
"fail" means that something has determined that the device is not
working properly and the software does not know how to make it work.

That is distinct from "disabled", which means that the choice has been
made not to use the device.

In the modern world of SoC with physically-unconnected functional units,
perhaps a new value would be appropriate: status="unused".

  parent reply	other threads:[~2012-08-20 17:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1345034325-26656-1-git-send-email-srinivas.kandagatla@st.com>
     [not found] ` <1345034325-26656-1-git-send-email-srinivas.kandagatla-qxv4g6HH51o@public.gmane.org>
2012-08-15 13:21   ` [RFC:PATCH dtc-1.3.0] dtc: Add --strip-disabled option to dtc Tabi Timur-B04825
2012-08-17  6:04   ` David Gibson
     [not found]     ` <20120817060415.GC29724-W9XWwYn+TF0XU02nzanrWNbf9cGiqdzd@public.gmane.org>
2012-08-17  8:55       ` Srinivas KANDAGATLA
2012-08-17 12:16       ` Tabi Timur-B04825
     [not found]         ` <502E3632.70208-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-08-17 14:19           ` Srinivas KANDAGATLA
     [not found]             ` <502E52F3.7090404-qxv4g6HH51o@public.gmane.org>
2012-08-17 15:36               ` Timur Tabi
     [not found]                 ` <502E64F9.2020400-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-08-20  8:36                   ` Srinivas KANDAGATLA
     [not found]                     ` <5031F706.3050509-qxv4g6HH51o@public.gmane.org>
2012-08-20 12:37                       ` Tabi Timur-B04825
     [not found]                         ` <50322F9C.2070403-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-08-20 17:16                           ` Mitch Bradley [this message]
     [not found]                             ` <503270E1.6050902-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2012-08-21  0:09                               ` David Gibson
2012-08-20 15:59                       ` Scott Wood
     [not found]                         ` <50325ED4.2070403-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-08-20 16:01                           ` Timur Tabi
     [not found]                             ` <50325F60.9070106-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-08-20 16:06                               ` Scott Wood
     [not found]                                 ` <50326088.8060402-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-08-21  0:10                                   ` David Gibson
2012-08-21  0:11                       ` David Gibson

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=503270E1.6050902@firmworks.com \
    --to=wmb-d5eqfidgl7eakbo8gow8eq@public.gmane.org \
    --cc=B04825-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=B07421-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=dwg-8fk3Idey6ehBDgjK7y7TUQ@public.gmane.org \
    --cc=mmarek-AlSwsSmVLrQ@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 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.