From: Stephen Boyd <sboyd@codeaurora.org>
To: Kevin Hilman <khilman@linaro.org>
Cc: Kumar Gala <galak@codeaurora.org>,
linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linus.walleij@linaro.org
Subject: Re: [PATCH] ARM: qcom: Enable basic support for Qualcomm platforms in multi_v7_defconfig
Date: Fri, 28 Feb 2014 10:27:45 -0800 [thread overview]
Message-ID: <20140228182745.GC2487@codeaurora.org> (raw)
In-Reply-To: <7hzjlbtc9y.fsf@paris.lan>
On 02/28, Kevin Hilman wrote:
> 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?
>
Can you try disabling CONFIG_ARCH_MSM8X60 and
CONFIG_ARCH_MSM8960? MY suspicion is the text offset movement is
causing problems, but I hope I'm wrong.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
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 10:27:45 -0800 [thread overview]
Message-ID: <20140228182745.GC2487@codeaurora.org> (raw)
In-Reply-To: <7hzjlbtc9y.fsf@paris.lan>
On 02/28, Kevin Hilman wrote:
> 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?
>
Can you try disabling CONFIG_ARCH_MSM8X60 and
CONFIG_ARCH_MSM8960? MY suspicion is the text offset movement is
causing problems, but I hope I'm wrong.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-02-28 18:27 UTC|newest]
Thread overview: 15+ 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-25 20:34 ` Kumar Gala
2014-02-25 20:34 ` Kumar Gala
2014-02-26 23:43 ` Kevin Hilman
2014-02-26 23:43 ` Kevin Hilman
2014-02-27 14:12 ` Kumar Gala
2014-02-27 14:12 ` Kumar Gala
2014-02-28 16:47 ` Kevin Hilman
2014-02-28 16:47 ` Kevin Hilman
2014-02-28 18:27 ` Stephen Boyd [this message]
2014-02-28 18:27 ` Stephen Boyd
2014-02-28 18:44 ` Kevin Hilman
2014-02-28 18:44 ` Kevin Hilman
2014-02-28 20:24 ` 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=20140228182745.GC2487@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=arnd@arndb.de \
--cc=galak@codeaurora.org \
--cc=khilman@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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.