Messages in this thread | | | Date | Thu, 5 May 2016 09:25:21 -0700 | Subject | Re: [PATCH] scripts/dtc: dt_to_config - report kernel config options for a devicetree | From | Gaurav Minocha <> |
| |
On Sat, Apr 30, 2016 at 1:38 PM, Rob Herring <robh+dt@kernel.org> wrote: > On Fri, Apr 29, 2016 at 1:39 AM, Gaurav Minocha > <gaurav.minocha.os@gmail.com> wrote: >> On Thu, Apr 28, 2016 at 3:32 PM, Rob Herring <robh+dt@kernel.org> wrote: >>> On Thu, Apr 28, 2016 at 4:46 PM, Frank Rowand <frowand.list@gmail.com> wrote: >>>> From: Frank Rowand <frank.rowand@am.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.
Okay, that seems like a useful option, that should be part of the tool itself. Will discuss with Frank once he is back. Thanks!
> > Rob
| |