Re: [U-Boot] [PATCH 1/2] RFC: dm: Kconfig: Move all driver model CONFIGs to Kconfig

On Tue, Dec 9, 2014 at 7:21 AM, Simon Glass sjg@chromium.org wrote:

Kconfig has been available for a while but there are still driver model CONFIG options. Move all of these to Kconfig.

This patch isn't final - I need to wait until the SPL series can be fully applied, which is in turn waiting on some ARM SPL problems. So for now it is just a placeholder. But it needs to be sent out otherwise we will never move over.

Signed-off-by: Simon Glass sjg@chromium.org

diff --git a/common/Kconfig b/common/Kconfig index fd84fa0..174bf4f 100644 --- a/common/Kconfig +++ b/common/Kconfig @@ -153,6 +153,29 @@ endmenu

menu "Device access commands"

+config CMD_DM

•   bool "dm - Access to driver model information"
  

•   depends on DM
  

•   default y
  

•   help
  

•     Provides access to driver model data structures and information,
  

•     such as a list of devices, list of uclasses and the state of
  

each

•     device (e.g. activated). This is not required for operation, but
  

•     can be useful to see the state of driver model for debugging or
  

•     interest.
  

+config CMD_DEMO

•   bool "demo - Demonstration commands for driver model"
  

•   depends on DM
  

•   help
  

•     Procides a 'demo' command which can be used to play around with
  

Provides

•     driver model. To use this properly you will need to enable one
  

or

•     both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
  

•     Otherwise you will always get an empty list of devices. The demo
  

•     devices are defined in the sandbox device tree, so the easiest
  

•     option is to use sandbox and pass the -d point to sandbox's
  

•     u-boot.dtb file.
  

config CMD_LOADB bool "loadb" help