From: khilman@linaro•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: qcom: Enable basic support for Qualcomm platforms in multi_v7_defconfig
Date: Fri, 28 Feb 2014 08:47:21 -0800 [thread overview]
Message-ID: <7hzjlbtc9y.fsf@paris.lan> (raw)
In-Reply-To: <7hy50xv3rw.fsf@paris.lan> (Kevin Hilman's message of "Wed, 26 Feb 2014 15:43:31 -0800")
Hi Kumar,
Kevin Hilman <khilman@linaro•org> writes:
> Kumar Gala <galak@codeaurora•org> writes:
>
>> Enable support for the MSM8x60, MSM8960, and MSM8974 SoCs, clocks and
>> serial console as part of the standard multi_v7_defconfig.
>>
>> Signed-off-by: Kumar Gala <galak@codeaurora•org>
>> ---
>>
>> I leave this to the arm-soc guys to apply because of possible conflicts
>> with other updates to multi_v7_defconfig.
>
> Seem to be a handful of !qcom changes here, probably resulting from a
> run of 'make savedefconfig' without all the new changes in.
>
> I've thinned this out to only the qcom changes and applied the following
> to next/boards. I think it's better to do any 'make savedefconfig'
> cleanups as a separate, cleanup-only patch as needed.
Bisecting a new boot failure on u8500/snowball came down to this patch.
Simply disabling CONFIG_ARCH_QCOM in mutli_v7_defconfig gets the
u8500/snowball booting again, so it looks like there may still be some
qcom specifics that are being run on non-qcom platforms with a
multi-platform config.
Could you audit for initcalls/drivers being initialized on non-qcom
SoCs?
Thanks,
Kevin
next prev parent reply other threads:[~2014-02-28 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 20:34 [PATCH] ARM: qcom: Enable basic support for Qualcomm platforms in multi_v7_defconfig Kumar Gala
2014-02-26 23:43 ` Kevin Hilman
2014-02-27 14:12 ` Kumar Gala
2014-02-28 16:47 ` Kevin Hilman [this message]
2014-02-28 18:27 ` Stephen Boyd
2014-02-28 18:44 ` Kevin Hilman
2014-02-28 20:24 ` 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=7hzjlbtc9y.fsf@paris.lan \
--to=khilman@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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