From: Xiao Jiang <jgq516@gmail.com>
To: Olof Johansson <olof@lixom.net>
Cc: linux@arm.linux.org.uk, arnd@arndb.de, tony@atomide.com,
nicolas.ferre@atmel.com, linux-kernel@vger.kernel.org,
ldewangan@nvidia.com, swarren@nvidia.com,
linux-omap@vger.kernel.org, plagnioj@jcrosoft.com,
linux-arm-kernel@lists.infradead.org, hdoyu@nvidia.com
Subject: Re: [PATCH 1/1] ARM: add PROC_DEVICETREE support in Kconfig
Date: Sat, 7 Jul 2012 08:10:57 +0800 [thread overview]
Message-ID: <CAERv70vi6-OanH2p9Db0jy-zLVVeNa+dfC04aYrsd_3m7OydLQ@mail.gmail.com> (raw)
In-Reply-To: <CAOesGMjmeXVx2MR7GGux9Cztkf-C3cBqpBW1_PW75D_Gk0GHiA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1137 bytes --]
2012/7/7 Olof Johansson <olof@lixom.net>
> On Fri, Jul 6, 2012 at 4:15 PM, Xiao Jiang <jgq516@gmail.com> wrote:
> > 2012/7/6 Rob Herring <robherring2@gmail.com>
> >>
> >> On 07/06/2012 05:38 AM, jgq516@gmail.com wrote:
> >> > From: Xiao Jiang <jgq516@gmail.com>
> >> >
> >> > Since more and more arm chips support device tree, it'd be better add
> >> > PROC_DEVICETREE
> >> > in arch/arm/Kconfig to avoid duplicate code.
> >>
> >> I think this should remain user choice. If its going to be selected,
> >> then you might as well just remove the option altogether. Perhaps just
> >> make the option default to yes.
> >>
> > Hmm, sounds reasonable from your point. So the better choice is to set
> the
> > option default to Y if the board has dt support just like tegra_defconfig
> > and at91_dt_defconfig, right? thanks.
>
> Why bother? If the defconfigs select it then most users basing their
> config from that will be just fine.
>
> PROC_DEVICETREE is 100% optional, it's useful to get runtime access to
> the contents of the device tree but it's not required for the kernel
> to boot.
>
> Got it, thanks.
Regards,
Xiao
>
> -Olof
>
[-- Attachment #1.2: Type: text/html, Size: 2034 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: jgq516@gmail.com (Xiao Jiang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: add PROC_DEVICETREE support in Kconfig
Date: Sat, 7 Jul 2012 08:10:57 +0800 [thread overview]
Message-ID: <CAERv70vi6-OanH2p9Db0jy-zLVVeNa+dfC04aYrsd_3m7OydLQ@mail.gmail.com> (raw)
In-Reply-To: <CAOesGMjmeXVx2MR7GGux9Cztkf-C3cBqpBW1_PW75D_Gk0GHiA@mail.gmail.com>
2012/7/7 Olof Johansson <olof@lixom.net>
> On Fri, Jul 6, 2012 at 4:15 PM, Xiao Jiang <jgq516@gmail.com> wrote:
> > 2012/7/6 Rob Herring <robherring2@gmail.com>
> >>
> >> On 07/06/2012 05:38 AM, jgq516 at gmail.com wrote:
> >> > From: Xiao Jiang <jgq516@gmail.com>
> >> >
> >> > Since more and more arm chips support device tree, it'd be better add
> >> > PROC_DEVICETREE
> >> > in arch/arm/Kconfig to avoid duplicate code.
> >>
> >> I think this should remain user choice. If its going to be selected,
> >> then you might as well just remove the option altogether. Perhaps just
> >> make the option default to yes.
> >>
> > Hmm, sounds reasonable from your point. So the better choice is to set
> the
> > option default to Y if the board has dt support just like tegra_defconfig
> > and at91_dt_defconfig, right? thanks.
>
> Why bother? If the defconfigs select it then most users basing their
> config from that will be just fine.
>
> PROC_DEVICETREE is 100% optional, it's useful to get runtime access to
> the contents of the device tree but it's not required for the kernel
> to boot.
>
> Got it, thanks.
Regards,
Xiao
>
> -Olof
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120707/e1b4c8b6/attachment-0001.html>
next prev parent reply other threads:[~2012-07-07 0:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 10:38 [PATCH 1/1] ARM: add PROC_DEVICETREE support in Kconfig jgq516
2012-07-06 10:38 ` jgq516 at gmail.com
2012-07-06 10:38 ` jgq516
2012-07-06 11:28 ` Jean-Christophe PLAGNIOL-VILLARD
2012-07-06 11:28 ` Jean-Christophe PLAGNIOL-VILLARD
2012-07-06 11:28 ` Jean-Christophe PLAGNIOL-VILLARD
2012-07-06 12:40 ` Rob Herring
2012-07-06 12:40 ` Rob Herring
2012-07-06 23:15 ` Xiao Jiang
2012-07-06 23:15 ` Xiao Jiang
2012-07-06 23:24 ` Olof Johansson
2012-07-06 23:24 ` Olof Johansson
2012-07-07 0:10 ` Xiao Jiang [this message]
2012-07-07 0:10 ` Xiao Jiang
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=CAERv70vi6-OanH2p9Db0jy-zLVVeNa+dfC04aYrsd_3m7OydLQ@mail.gmail.com \
--to=jgq516@gmail.com \
--cc=arnd@arndb.de \
--cc=hdoyu@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.ferre@atmel.com \
--cc=olof@lixom.net \
--cc=plagnioj@jcrosoft.com \
--cc=swarren@nvidia.com \
--cc=tony@atomide.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 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.