From: Stephen Boyd <sboyd@codeaurora.org>
To: Will Newton <will.newton@gmail.com>
Cc: linux-arm-msm@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
anYc <dev@kicherer.org>
Subject: Re: Initial msm8909 support
Date: Tue, 19 Dec 2017 11:08:55 -0800 [thread overview]
Message-ID: <20171219190855.GA7997@codeaurora.org> (raw)
In-Reply-To: <CAFbHwiRJHiTEwxk=0tGw-JN3bRBSTFY+ST4UrzQQn03ipmTrcA@mail.gmail.com>
On 12/19, Will Newton wrote:
> On Tue, Dec 19, 2017 at 2:21 PM, Will Newton <will.newton@gmail.com> wrote:
> > On Tue, Dec 19, 2017 at 9:44 AM, Will Newton <will.newton@gmail.com> wrote:
> >> Hi,
> >>
> >> I have a git tree with my initial start at msm8909 support in Linux 4.9 here:
> >>
> >> https://bitbucket.org/andromedauk/msm8909-linux
> >>
> >> It's based off the Linaro Qualcomm landing team tree (with Android
> >> drivers merged too for no useful reason).
> >>
> >> The current state is that pinctrl is pretty much done, regulators are
> >> mostly done, clocks is quite hard to say as I'm not doing a good job
> >> of parsing the docs right now. The serial port works! I've seen the
> >> USB driver enumerate a hub but not tested any further.
The bus clks that you're missing aren't typically exposed in
downstream kernels because we don't control the rates of those
clks. We've been putting them into upstream to keep the clk tree
connected to a root. If you can list the clks that are missing I
can give you the info you need.
> >>
> >> Outstanding tasks:
> >>
> >> 1. Semi-random resets during boot. Occasionally the board will reset
> >> for no obvious reason during boot. I suspect this is something to do
> >> with regulators as it usually seems to be around the time something is
> >> setting voltage and turning on initcall debugging seems to make it
> >> less likely to happen (by slowing the boot).
> >
> > FWIW these resets go away if I disable the wcnss driver in the dts.
>
> Specifically the code that triggers the reset is the call to
> qcom_scm_pas_auth_and_reset in qcom_wcnss.c. If I comment that call
> out then the boot seems to be stable. Does anyone have any ideas what
> might cause that behaviour?
>
The wcnss is probably crashing because some regulator or clk is
not enabled, or voltages need to be bumped up. One idea to debug
would be to make wcnss into a module that you load with modprobe.
Then you can try turning on more regulators, and verify that
they're actually on by dumping the SPMI registers, until you
narrow down what's off that needs to be on. This would also allow
you to confirm the RPM communication is working and regulators
are actually working.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-12-19 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 9:44 Initial msm8909 support Will Newton
2017-12-19 14:21 ` Will Newton
2017-12-19 17:30 ` Will Newton
2017-12-19 19:08 ` Stephen Boyd [this message]
2017-12-20 9:58 ` Will Newton
2017-12-21 6:45 ` Bjorn Andersson
2017-12-21 10:01 ` Will Newton
2017-12-21 15:58 ` Will Newton
2017-12-21 16:02 ` Will Newton
2018-01-04 10:37 ` Will Newton
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=20171219190855.GA7997@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=dev@kicherer.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=will.newton@gmail.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