Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752081AbcD3UjB (ORCPT ); Sat, 30 Apr 2016 16:39:01 -0400 Received: from mail.kernel.org ([198.145.29.136]:49195 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750775AbcD3Ui7 (ORCPT ); Sat, 30 Apr 2016 16:38:59 -0400 MIME-Version: 1.0 In-Reply-To: References: <572284AB.102@gmail.com> From: Rob Herring Date: Sat, 30 Apr 2016 15:38:35 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] scripts/dtc: dt_to_config - report kernel config options for a devicetree To: Gaurav Minocha Cc: Frank Rowand , Grant Likely , "devicetree@vger.kernel.org" , Linux Kernel list , Geert Uytterhoeven , Pavel Machek , Alison Chaiken Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1138 Lines: 24 On Fri, Apr 29, 2016 at 1:39 AM, Gaurav Minocha wrote: > On Thu, Apr 28, 2016 at 3:32 PM, Rob Herring wrote: >> On Thu, Apr 28, 2016 at 4:46 PM, Frank Rowand wrote: >>> From: Frank Rowand >>> >>> 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