From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Konrad Dybcio <konradybcio@gmail.com>,
skrzynka@konradybcio.pl, Andy Gross <agross@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-clk@vger.kernel.org, DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] clk: qcom: smd: Add support for MSM8992/4 rpm clocks
Date: Sat, 11 Jul 2020 12:47:46 -0700 [thread overview]
Message-ID: <20200711194746.GA388985@builder.lan> (raw)
In-Reply-To: <159303797640.62212.15039388585433005717@swboyd.mtv.corp.google.com>
On Wed 24 Jun 15:32 PDT 2020, Stephen Boyd wrote:
> Quoting Konrad Dybcio (2020-06-24 08:09:18)
> > I should also note that for quite some time a hack [1]
> > has been needed on some platforms for the RPMCC to register.
> >
> > This includes 8992/94, 8956/76 and possibly many more.
> >
> > With that commit, RPMCC registers fine.
> >
>
> What happens if that patch isn't applied? Does the system crash? Because
> I'd rather not merge a patch in clk tree that causes the system to fail
> to boot.
The state machine code in the SMD implementation finds the RPM channel,
but it's in a state that indicates that the remote side is still
closing/cleaning up from when the bootloader had it open.
The result is that we never probe the RPM driver.
I merged a patch that would cause the logic here to be a little bit more
aggressive/optimistic, but that had to be reverted because it prevented
the modem from coming up cleanly after a crash. And I unfortunately
still don't have any hardware that manifest this problem that I can
debug this on myself.
But I think it's fine to merge the rpmcc patch (which I see you did).
Thanks,
Bjorn
next prev parent reply other threads:[~2020-07-11 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 23:00 [PATCH 1/1] clk: qcom: smd: Add support for MSM8992/4 rpm clocks Konrad Dybcio
2020-06-24 15:09 ` Konrad Dybcio
2020-06-24 22:32 ` Stephen Boyd
2020-06-24 22:38 ` Konrad Dybcio
2020-07-11 19:47 ` Bjorn Andersson [this message]
2020-07-11 16:19 ` Stephen Boyd
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=20200711194746.GA388985@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=skrzynka@konradybcio.pl \
/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.