[U-Boot] [PATCH 0/2] power: TWL4030: Move CONFIG_TWL4030_POWER to Kconfig

[Tom Rini]

On Thu, Apr 27, 2017 at 09:33:58AM -0500, Adam Ford wrote:
> On Wed, Apr 26, 2017 at 3:19 PM, Tom Rini <trini at konsulko.com> wrote:
> > On Wed, Apr 26, 2017 at 02:55:08PM -0500, Adam Ford wrote:
> >> On Wed, Apr 26, 2017 at 2:49 PM, Tom Rini <trini at konsulko.com> wrote:
> >> > On Wed, Apr 26, 2017 at 01:41:30PM -0500, Adam Ford wrote:
> >> >
> >> >> This series will move  CONFIG_TWL4030_POWER to Kconfig from include/configs.
> >> >> It will enable it by default when selecting OMAP34XX and remove it from
> >> >> a small handful of include/config files that are not yet using ti_omap3_common.h
> >> >> as well as ti_omap3_common.h.  I do not have the other hardware, but I tested
> >> >> this with a Logic PD Torpedo based on a DM3730 (OMAP3630) without issue.
> >> >>
> >> >> Adam Ford (2):
> >> >>   power: twl4030: Move CONFIG_TWL4030_POWER to Kconfig
> >> >>   power: twl4030: Remove CONFIG_TWL4030_POWER from include/configs
> >> >>
> >> >>  arch/arm/Kconfig                  | 1 +
> >> >>  drivers/power/Kconfig             | 7 +++++++
> >> >>  include/configs/cm_t35.h          | 1 -
> >> >>  include/configs/nokia_rx51.h      | 1 -
> >> >>  include/configs/omap3_evm.h       | 1 -
> >> >>  include/configs/sniper.h          | 6 ------
> >> >>  include/configs/tao3530.h         | 1 -
> >> >>  include/configs/ti_omap3_common.h | 3 ---
> >> >>  include/configs/tricorder.h       | 1 -
> >> >>  scripts/config_whitelist.txt      | 1 -
> >> >>  10 files changed, 8 insertions(+), 15 deletions(-)
> >> >
> >> > This looks good, but should just be a single patch that adds to Kconfig
> >> > and updates the include files.  Thanks for doing this!
> >>
> >> Do you want me to re-post with a V2 with them merged?
> >
> > No, that's OK.  Just keep in mind in case anyone else has comments.
> > Thanks!
> >
> 
> So, call me oblivious, but I just learned about moveconfigs.py  (facepalm)
> 
> I was going tackle more Kconfig migration, but I was struggling
> figuring out how to autoupdate defconfigs.  Is there an example I can
> follow?

Well, my workflow is to add X to the Kconfig file and run my
moveconfig.py wrapper for the new option, and then check over the
changes, to see if I should use imply or default y if ... in places.
And I start out by doing a moveconfig.py -sC to re-sync all defconfigs
first so I don't see that noise.

My wrapper around moveconfig.py is just to make sure PATH has all of the
cross toolchains, and then to set CROSS_COMPILE_xxx for a lot of
architectures.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170427/a2f5ca86/attachment.sig>