From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Brian Masney <masneyb@onstation.org>
Cc: georgi.djakov@linaro.org, robh+dt@kernel.org, agross@kernel.org,
mark.rutland@arm.com, linux-arm-msm@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, jonathan@marek.ca
Subject: Re: [PATCH v2 2/2] interconnect: qcom: add msm8974 driver
Date: Fri, 11 Oct 2019 10:05:06 -0700 [thread overview]
Message-ID: <20191011170506.GD571@minitux> (raw)
In-Reply-To: <20191005114605.5279-3-masneyb@onstation.org>
On Sat 05 Oct 04:46 PDT 2019, Brian Masney wrote:
> diff --git a/drivers/interconnect/qcom/msm8974.c b/drivers/interconnect/qcom/msm8974.c
[..]
> +static void msm8974_icc_rpm_smd_send(struct device *dev, int rsc_type,
> + char *name, int id, u64 val)
> +{
> + int ret;
> +
> + if (id == -1)
> + return;
> +
> + /*
> + * Setting the bandwidth requests for some nodes fails and this same
> + * behavior occurs on the downstream MSM 3.4 kernel sources based on
> + * errors like this in that kernel:
> + *
> + * msm_rpm_get_error_from_ack(): RPM NACK Unsupported resource
> + * AXI: msm_bus_rpm_req(): RPM: Ack failed
> + * AXI: msm_bus_rpm_commit_arb(): RPM: Req fail: mas:32, bw:240000000
> + *
> + * Since there's no publicly available documentation for this hardware,
> + * and the bandwidth for some nodes in the path can be set properly,
> + * let's not return an error.
> + */
So presumably all that matters for paths including these endpoints is
the clk_set_rate() on the bus itself. But I prefer that we merge it like
you propose and then swing back to work out the details.
> + ret = qcom_icc_rpm_smd_send(QCOM_SMD_RPM_ACTIVE_STATE, rsc_type, id,
> + val);
> + if (ret)
> + dev_dbg(dev, "Cannot set bandwidth for node %s (%d): %d\n",
> + name, id, ret);
> +}
> +
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Regards,
Bjorn
next prev parent reply other threads:[~2019-10-11 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 11:46 [PATCH v2 0/2] interconnect: qcom: add msm8974 support Brian Masney
2019-10-05 11:46 ` [PATCH v2 1/2] dt-bindings: interconnect: qcom: add msm8974 bindings Brian Masney
2019-10-11 15:29 ` Rob Herring
2019-10-11 17:06 ` Bjorn Andersson
2019-10-05 11:46 ` [PATCH v2 2/2] interconnect: qcom: add msm8974 driver Brian Masney
2019-10-11 17:05 ` Bjorn Andersson [this message]
2019-10-12 11:00 ` Brian Masney
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=20191011170506.GD571@minitux \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=georgi.djakov@linaro.org \
--cc=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masneyb@onstation.org \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).