public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Felipe Balbi <me@felipebalbi.com>,
	balbi@ti.com, linux-usb@vger.kernel.org,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-main <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>
Subject: Re: [PATCH v2 3/3] drivers: cleanup Kconfig stuff
Date: Tue, 19 Oct 2010 16:44:14 -0700	[thread overview]
Message-ID: <20101019234414.GB30991@atomide.com> (raw)
In-Reply-To: <AANLkTinYM5aavk9_jcTTymff=OY+Yyv8T6C+dmMih0p_@mail.gmail.com>

* Felipe Contreras <felipe.contreras@gmail.com> [101019 13:43]:
> On Tue, Oct 19, 2010 at 6:05 PM, Felipe Balbi <me@felipebalbi.com> wrote:
> > On Tue, 19 Oct 2010 17:32:07 +0300, Felipe Contreras
> > <felipe.contreras@gmail.com> wrote:
> >> There are two parts, one part is to fix the Kconfigs, and another was
> >> to come up with a way to replace the horrible defconfigs. Part two is
> >> mostly fixed thanks to 'make savedefconfig', since the defconfigs are
> >> not so horrible any more, but part one is a continued effort.
> >>
> >> For part two Linus had the idea to use Kconfigs instead of defconfigs,
> >> but they would mostly look very similar to the current ones generated
> >> by 'make savedefconfig'.
> >>
> >> I don't know what makes you think Linus didn't want part one to be
> >> done. He wanted the Kconfig.rx51 to be human readable, and you are
> >> proposing that TWL4030_USB should be manually added there... I don't
> >> think TWL4030_USB says anything to human beings.
> >
> > I don't read anywhere Linus saying we should clutter drivers/*/Kconfig
> > with defaults. I think you're inverting things, it's much better
> > to select TWL4030_USB when you enable MACH_OMAP_RX51 then default y
> > if MACH_OMAP_RX51.
> 
> So say, if you have 100 board defconfigs with OMAP3 chips and TWL4030,
> each and every one of them should select both USB_MUSB_HDRC and
> TWL4030_USB?
> 
> And you are saying if somebody is doing 'make menuconfig', that person
> should somehow know that _obviously_ he needs TWL4030_USB in order to
> use USB_MUSB_HDRC, or USB_G_NOKIA?

Hey we're already dealing with stuff like this :)

See ARCH_OMAP2PLUS_TYPICAL in arch/arm/mach-omap2/Kconfig:

config ARCH_OMAP2PLUS_TYPICAL
        bool "Typical OMAP configuration"
        default y
        select AEABI
        select REGULATOR
        select PM
        select PM_RUNTIME
        select VFP
        select NEON if ARCH_OMAP3 || ARCH_OMAP4
        select SERIAL_OMAP
        select SERIAL_OMAP_CONSOLE
        select I2C
        select I2C_OMAP
        select MFD
        select MENELAUS if ARCH_OMAP2
        select TWL4030_CORE if ARCH_OMAP3 || ARCH_OMAP4
        select TWL4030_POWER if ARCH_OMAP3 || ARCH_OMAP4
        help
          Compile a kernel suitable for booting most boards

This actually produces a booting omap2+ kernel with no .config
at all. I've tested it with:

$ echo CONFIG_ARCH_OMAP=y > .config
$ yes "" | ARCH=arm make oldconfig

So if you have something that's needed on almost every omap,
you can select it there.

Regards,

Tony

  reply	other threads:[~2010-10-19 23:44 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 10:03 [PATCH v2 0/3] usb: generic Kconfig fixes Felipe Contreras
2010-10-19 10:03 ` [PATCH v2 1/3] usb: fix Kconfig warning Felipe Contreras
2010-10-19 10:28   ` Felipe Balbi
2010-10-19 15:50     ` Greg KH
2010-10-20  6:34   ` Felipe Balbi
2010-10-19 10:03 ` [PATCH v2 2/3] usb: trivial Kconfig cleanups Felipe Contreras
2010-10-19 15:51   ` Greg KH
2010-10-19 17:15     ` Felipe Contreras
2010-10-19 17:50       ` Greg KH
2010-10-19 18:15         ` Felipe Contreras
2010-10-20 18:25   ` Felipe Balbi
2010-10-19 10:03 ` [PATCH v2 3/3] drivers: cleanup Kconfig stuff Felipe Contreras
2010-10-19 10:32   ` Felipe Balbi
2010-10-19 10:59     ` Felipe Contreras
2010-10-19 11:16       ` Felipe Balbi
2010-10-19 11:36         ` Felipe Contreras
2010-10-19 11:52           ` Felipe Balbi
2010-10-19 14:32             ` Felipe Contreras
2010-10-19 15:05               ` Felipe Balbi
2010-10-19 20:52                 ` Felipe Contreras
2010-10-19 23:44                   ` Tony Lindgren [this message]
2010-10-20  0:13                     ` Kevin Hilman
2010-10-20  0:31                       ` Tony Lindgren
2010-10-20  6:35                       ` Felipe Balbi
2010-10-20  8:47                       ` felipe.contreras
2010-10-19 13:40   ` Roger Quadros
2010-10-19 14:33     ` Felipe Contreras
2010-10-20  7:46       ` Roger Quadros
2010-10-20  8:01         ` Felipe Balbi
2010-10-20  8:53         ` felipe.contreras
2010-10-20  9:14           ` Roger Quadros
2010-10-20  9:23             ` Felipe Contreras
2010-10-20 12:33               ` Roger Quadros
2010-10-20 14:38                 ` Felipe Contreras
2010-10-21 14:07                   ` Roger Quadros
2010-10-21 15:41                     ` Felipe Balbi
2010-10-21 15:57                       ` Tony Lindgren
2010-10-20 12:33               ` Roger Quadros
2010-10-20 12:54               ` Felipe Balbi
2010-10-20 14:52                 ` Felipe Contreras
2010-10-20 15:15                   ` Felipe Balbi
2010-10-20 16:22                     ` Felipe Contreras
2010-10-20 17:54                       ` Felipe Balbi
2010-10-21  9:04                         ` Felipe Contreras
2010-10-21 10:24                           ` Felipe Balbi
2010-10-21 10:55                             ` Felipe Contreras
2010-10-19 15:52   ` Greg KH
2010-10-19 16:12     ` Anand Gadiyar
2010-10-19 16:23       ` Greg KH
2010-10-19 17:06       ` Kevin Hilman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101019234414.GB30991@atomide.com \
    --to=tony@atomide.com \
    --cc=balbi@ti.com \
    --cc=felipe.contreras@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=me@felipebalbi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox