devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Dong Aisheng <b29396@freescale.com>
Cc: devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, grant.likely@linaro.org,
	rob@landley.net, rob.herring@calxeda.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] of: add update device node status via cmdline feature
Date: Thu, 15 Aug 2013 07:37:04 -0500	[thread overview]
Message-ID: <520CCB70.8090908@gmail.com> (raw)
In-Reply-To: <1376564133-11286-1-git-send-email-b29396@freescale.com>

On 08/15/2013 05:55 AM, Dong Aisheng wrote:
> We meet some boards having a lot of pin conflicts between different devices,
> only one of them can be enabled to run at one time.
> 
> e.g. imx6q sabreauto board, i2c, spi, weim, flexcan, uart and etc involved
> with pin conflict.
> 
> Instead of changing dts manually or adding a lot dts files according to
> different device availability, we provide feature to dynamically update the
> device node status via command line, then those devices involved with
> pin conflict can be enabled or disabled dynamically.
> 
> It's conveniently to use and can save a lot dts board files, also can
> permenantly fix the pin conflicts issue.

This doesn't scale either with updating of lots devices or when the next
person comes along and wants to edit another property.

This is something u-boot is perfectly capable of handling and updating
status is something lots of boards already do.

Rob

> 
> The patch series is based on v3.11-rc5.
> 
> Dong Aisheng (3):
>   of: add device node status update APIs
>   of: add update device node status via cmdline feature
>   of: add node status update via name format with cmdline
> 
>  Documentation/kernel-parameters.txt |   10 +++
>  drivers/of/base.c                   |  107 +++++++++++++++++++++++++++++++++
>  drivers/of/fdt.c                    |  111 +++++++++++++++++++++++++++++++++++
>  include/linux/of.h                  |   13 ++++
>  4 files changed, 241 insertions(+), 0 deletions(-)
> 
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

  parent reply	other threads:[~2013-08-15 12:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 10:55 [PATCH 0/3] of: add update device node status via cmdline feature Dong Aisheng
2013-08-15 10:55 ` [PATCH 1/3] of: add device node status update APIs Dong Aisheng
2013-08-15 10:55 ` [PATCH 2/3] of: add update device node status via cmdline feature Dong Aisheng
2013-08-15 10:55 ` [PATCH 3/3] of: add node status update via name format with cmdline Dong Aisheng
2013-08-15 12:37 ` Rob Herring [this message]
2013-08-15 12:46   ` [PATCH 0/3] of: add update device node status via cmdline feature Grant Likely
2013-08-21 12:47   ` Dong Aisheng
2013-08-21 13:23     ` Rob Herring
2013-08-23  7:13       ` Dong Aisheng
2013-08-15 12:45 ` Grant Likely
2013-08-21 12:37   ` Dong Aisheng
2013-08-23  7:09     ` Dong Aisheng

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=520CCB70.8090908@gmail.com \
    --to=robherring2@gmail.com \
    --cc=b29396@freescale.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    /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).