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: Stephen Boyd <sboyd@codeaurora.org>, linux-arm-msm@vger.kernel.org
Subject: Re: msm8909 support in a recent kernel
Date: Sun, 10 Dec 2017 22:11:21 -0800	[thread overview]
Message-ID: <20171211061121.GC4803@minitux> (raw)
In-Reply-To: <CAFbHwiQSR2NnvGZir2YjEBamrTs5omJCNxU4vam5escSB634=g@mail.gmail.com>

On Thu 07 Dec 06:13 PST 2017, Will Newton wrote:
[..]
> 
> I think I have narrowed down the issue to the fact that the qcom_smd
> driver is not getting any interrupts. I get a channel created:
> 
> [    0.728352]  smd:rpm: new channel 'rpm_requests' info-size: 88
> fifo-size: 1024
> [    0.731684]  smd:rpm: new channel found: 'rpm_requests'
> 

That's good.

> But on the first (and only) time through qcom_channel_state_worker the
> channel is in state FLUSHING so we never create a device. Any idea why
> I might not be getting any interrupts?
> 

I presume you mean the value of GET_RX_CHANNEL_INFO(channel, state)
here. This has been reported on 8994 as well and do stem from a
misunderstanding of mine when it comes to how the state machine is
ticking when a channel is closed.

What we see on 8994 is that the boot loader opens the rpm_requests
channel, send a few regulator requests and then put the channel (the
apps side of it) in closing state. During boot of the Linux kernel the
rpm_requests channel is then found in "closing" state.

And looking at LK, the two platforms implementing this schema are 8994
and 8909.


My two hypothesises for 8994 was that we could either:

1) Complete the closing (i.e. not leave the channel in closing/reset
state) and that might cause the other side to move to "opening" again,
or
2) take a more active role in driving the channel to opening,
based on the knowledge that Linux do have someone to interested in
communicating over this link.

The first is pretty close of being a hack and the second relies on this
loop figuring out if there is going to be a driver-device match in the
future.

Unfortunately, this being reported on 8994 gave it a low priority, so
it's been sitting far down on my todo list ever since.

> The irq numbers etc. all look correct as far as I can tell. smem and
> tcsr-mutex also look OK. I'm not sure about apcs as I don't have clear
> documentation on what it actually entails e.g. I have SAW devices
> setup which seem to be part of APCS but not sure what else.

Looked at the documentation, apcs should be defined as reg = <0x0b011000
0x1000> and qcom,ipc should be <&apcs 8 0>. I.e. exactly the same as
8916.

Regards,
Bjorn

  parent reply	other threads:[~2017-12-11  6:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 16:47 msm8909 support in a recent kernel Will Newton
2017-11-29 18:50 ` Stephen Boyd
2017-12-01 17:23   ` Will Newton
2017-12-06  2:45     ` Stephen Boyd
2017-12-06 14:39       ` Will Newton
2017-12-06 18:43         ` Bjorn Andersson
2017-12-06 20:10           ` Will Newton
2017-12-06 21:58             ` Bjorn Andersson
2017-12-07 14:13               ` Will Newton
2017-12-08 15:17                 ` Will Newton
2017-12-08 17:07                   ` Stephen Boyd
2017-12-10  9:37                     ` Will Newton
2017-12-11  6:11                 ` Bjorn Andersson [this message]
2017-12-12 10:59                   ` Will Newton
2017-12-12 17:24                     ` Will Newton
2017-12-13  0:01                     ` Bjorn Andersson
2017-12-13  9:46                       ` 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=20171211061121.GC4803@minitux \
    --to=bjorn.andersson@linaro.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.