From: Stephen Boyd <sboyd@codeaurora.org>
To: Will Newton <will.newton@gmail.com>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: msm8909 support in a recent kernel
Date: Fri, 8 Dec 2017 09:07:37 -0800 [thread overview]
Message-ID: <20171208170737.GE4283@codeaurora.org> (raw)
In-Reply-To: <CAFbHwiRn_NhT-ugT5b6nt-3gbhJqFuRyaAS1sH26ggzAky6dQQ@mail.gmail.com>
On 12/08, Will Newton wrote:
> On Thu, Dec 7, 2017 at 2:13 PM, Will Newton <will.newton@gmail.com> 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'
> >
> > 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?
> >
> > 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.
>
> Is there any potential for version skew here between the RPM processor
> and Linux? I have an rpm.mbn binary but I have no idea what is in it,
> I just know it works with 3.18.
No, not really. This sounds like a similar problem that was seen
on msm8994, but I can't recall if it was ever resolved. Maybe
that was channel closing instead of flushing.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-12-08 17:07 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 [this message]
2017-12-10 9:37 ` Will Newton
2017-12-11 6:11 ` Bjorn Andersson
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=20171208170737.GE4283@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=bjorn.andersson@linaro.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