[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_Jsq+v3r1dNY1+CK=_Atyyysq=JAFfk0q7i6YVhKS1zTZMVg@mail.gmail.com>
Date: Sat, 30 Apr 2016 15:38:35 -0500
From: Rob Herring <robh+dt@...nel.org>
To: Gaurav Minocha <gaurav.minocha.os@...il.com>
Cc: Frank Rowand <frowand.list@...il.com>,
Grant Likely <grant.likely@...aro.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Pavel Machek <pavel@....cz>,
Alison Chaiken <alison_chaiken@...tor.com>
Subject: Re: [PATCH] scripts/dtc: dt_to_config - report kernel config options
for a devicetree
On Fri, Apr 29, 2016 at 1:39 AM, Gaurav Minocha
<gaurav.minocha.os@...il.com> wrote:
> On Thu, Apr 28, 2016 at 3:32 PM, Rob Herring <robh+dt@...nel.org> wrote:
>> On Thu, Apr 28, 2016 at 4:46 PM, Frank Rowand <frowand.list@...il.com> wrote:
>>> From: Frank Rowand <frank.rowand@...sony.com>
>>>
>>> Determining which kernel config options need to be enabled for a
>>> given devicetree can be a painful process. Create a new tool to
>>> find the drivers that may match a devicetree node compatible,
>>> find the kernel config options that enable the driver, and
>>> optionally report whether the kernel config option is enabled.
>>
>> I would find this more useful to output a config fragment with all the
>> options enabled. The hard part there is enabling the options a given
>> option is dependent on which I don't think kbuild takes care of.
>
> Do you mean to generate something like .config? If yes, then IMO it would
> not be a correct configuration file.
No, only a config fragment which is just some subset of config
options. Then you could have a generic defconfig plus the fragment for
a platform to get a working setup.
Rob
Powered by blists - more mailing lists