All of lore.kernel.org
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: defconfig: include QCOM_EBI2 in multi_v7
Date: Wed, 11 Jan 2017 17:01:03 -0800	[thread overview]
Message-ID: <cee567ef-adc3-eb3f-81bb-e8a678b35fa8@codeaurora.org> (raw)
In-Reply-To: <CACRpkdacU0X1NH5HRwTvt1Wtn=9iqEs0MYQ_vt4UsGV67S4kBA@mail.gmail.com>

On 01/11/2017 07:22 AM, Linus Walleij wrote:
> On Tue, Jan 10, 2017 at 7:02 PM, Olof Johansson <olof@lixom.net> wrote:
>> On Tue, Jan 10, 2017 at 2:09 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
>>> This adds the Qualcomm External Bus Interface 2 to the multi_v7
>>> defconfig: it is hard for users to realize that this is a
>>> required driver for getting things like ethernet, and a necessary
>>> prerequisite to get the external bus discoverable on the
>>> MSM8660/APQ8060 machines.
>> Is it the kind of option that should really be selected through
>> Kconfig instead for those platforms?
> Stephen Boyd question.
>
> AFAIK the ambition is to go with the platform to have zero
> stuff in mach-qcom/* and thus it all becomes a defconfig
> thing.

It could be made a 'default ARCH_QCOM' type of thing. Then the config
doesn't need an update unless you want to turn it off. I imagine people
would want to turn it off if they're using a board with a qcom SoC that
isn't 8660, which is probably going to stay the majority forever.

It's true I've been pushing to get rid of the ARCH_MSM* configs in
mach-qcom/Kconfig as they lead to confusion about what qcom SoCs are
supported in mainline and cause config options to become outdated each
time a new SoC comes out that supports some particular driver. I'll go
repush those changes.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2017-01-12  1:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 10:09 [PATCH] ARM: defconfig: include QCOM_EBI2 in multi_v7 Linus Walleij
2017-01-10 18:02 ` Olof Johansson
2017-01-11 15:22   ` Linus Walleij
2017-01-12  1:01     ` Stephen Boyd [this message]
2017-01-12  7:04       ` Linus Walleij

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=cee567ef-adc3-eb3f-81bb-e8a678b35fa8@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.