linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dwalker@fifo99.com
To: Rob Herring <robh@kernel.org>
Cc: Daniel Walker <danielwa@cisco.com>,
	xe-kernel@external.cisco.com,
	Frank Rowand <frowand.list@gmail.com>,
	Grant Likely <grant.likely@linaro.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH-RFC 6/7] drivers: of: ifdef out cmdline section
Date: Wed, 7 Oct 2015 09:27:55 -0700	[thread overview]
Message-ID: <20151007162755.GA23283@fifo99.com> (raw)
In-Reply-To: <CAL_JsqLmVRdWZqxFRAZ-pgd225PGW8MNv4A47bcfD+cD_+K7rg@mail.gmail.com>

On Tue, Oct 06, 2015 at 12:14:43PM -0500, Rob Herring wrote:
> On Tue, Oct 6, 2015 at 10:47 AM, Daniel Walker <danielwa@cisco.com> wrote:
> > It looks like there's some seepage of cmdline stuff into
> > the generic device tree code. This conflicts with the
> > generic cmdline implementation so I remove it in the case
> > when that's enabled.
> 
> Nice series in general. I've had passing desire to do this every time
> I run into the command line code.
> 
> The DT handling of the command line is generic across architectures.
> The current design is working around that the kernel command line code
> is not that way. I think we can take this a bit further by making the
> generic DT code add the command line string directly rather than
> relying on the arch to do that. Then we can remove all command line
> handling from the arch code. I would also look at whether we can make
> boot_command_line static rather than directly accessed. We might have
> to leave it public for now, but could treat it as static for generic
> cmdline case.
> 

Sorry I didn't respond sooner. I was waiting to see if there were more replies.

One of my colleague suggested something similar, I was reluctant to change anything
prior to sending it out so I could get more feedback on the direction.

So your suggesting this patch be something like,

#ifdef CONFIG_GENERIC_CMDLINE
// call generic cmdline functions
#else
// keep what's there currently
#endif

Then remove the arch specific generic cmdline changes in the architecture code for the DT path.. 
Most of them have two places where they add in the command line. One from the device tree, and
another place that's from the bootloader. For example , ARM has the device tree call, then another
for atags. I don't think these device tree changes would allow us to remove the atags version, also
the boot_command_line wouldn't be able to be static.

Daniel


  reply	other threads:[~2015-10-07 16:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 15:47 [PATCH-RFC 6/7] drivers: of: ifdef out cmdline section Daniel Walker
2015-10-06 17:14 ` Rob Herring
2015-10-07 16:27   ` dwalker [this message]
2015-10-07 21:48     ` Rob Herring
2015-10-13 20:13       ` Daniel Walker
2015-10-13 21:17         ` Rob Herring
2015-10-14 14:48           ` Daniel Walker
2015-10-14 17:57             ` Rob Herring
2015-10-14 19:16               ` Daniel Walker

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=20151007162755.GA23283@fifo99.com \
    --to=dwalker@fifo99.com \
    --cc=danielwa@cisco.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=grant.likely@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=xe-kernel@external.cisco.com \
    /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).