All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Will Newton <will.newton@gmail.com>
Cc: linux-arm-msm@vger.kernel.org,
	Stephen Boyd <sboyd@codeaurora.org>, anYc <dev@kicherer.org>
Subject: Re: Initial msm8909 support
Date: Wed, 20 Dec 2017 22:45:01 -0800	[thread overview]
Message-ID: <20171221064501.GE478@tuxbook> (raw)
In-Reply-To: <CAFbHwiRJHiTEwxk=0tGw-JN3bRBSTFY+ST4UrzQQn03ipmTrcA@mail.gmail.com>

On Tue 19 Dec 09:30 PST 2017, 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.
> >>
> >> 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?
> 

It's worth noting that there are two sets of errors that occurs in
qcom_scm_pas_auth_and_reset(); either the implementation of the call
itself fails - typically from the lack of clocking of the crypto block -
or if the call succeeds the ARM core in the WiFi subsystem will start
execute the firmware and this might access hardware with expectations on
what the Linux side has configured.

Looking at the pronto in 8916, the only two pieces that comes to mind is
that either vddmx or vddpx are off; or that there are some other nuances
here that I missed when specifying the associated resources - which
isn't needed on the db410c.

Iirc any issues related to the iris (external RF module) will result in
a controlled crash of the remoteproc, not a full system reset.

Regards,
Bjorn

  parent reply	other threads:[~2017-12-21  6:45 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
2017-12-20  9:58       ` Will Newton
2017-12-21  6:45     ` Bjorn Andersson [this message]
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=20171221064501.GE478@tuxbook \
    --to=bjorn.andersson@linaro.org \
    --cc=dev@kicherer.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=sboyd@codeaurora.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 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.