From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Odelu Kukatla <quic_okukatla@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
cros-qcom-dts-watchers@chromium.org,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, quic_rlaggysh@quicinc.com,
quic_mdtipton@quicinc.com
Subject: Re: [PATCH v3 1/4] interconnect: qcom: icc-rpmh: Add QoS configuration support
Date: Wed, 6 Mar 2024 09:31:21 +0100 [thread overview]
Message-ID: <e7105dd7-68ff-4af6-b91e-56b6e50ff949@linaro.org> (raw)
In-Reply-To: <20240306073016.2163-2-quic_okukatla@quicinc.com>
On 06/03/2024 08:30, Odelu Kukatla wrote:
> It adds QoS support for QNOC device and includes support for
> configuring priority, priority forward disable, urgency forwarding.
> This helps in priortizing the traffic originating from different
> interconnect masters at NoC(Network On Chip).
>
> Signed-off-by: Odelu Kukatla <quic_okukatla@quicinc.com>
> ---
> drivers/interconnect/qcom/icc-rpmh.c | 105 +++++++++++++++++++++++++++
> drivers/interconnect/qcom/icc-rpmh.h | 32 ++++++++
> 2 files changed, 137 insertions(+)
>
> + if (desc->config) {
> + struct resource *res;
> + void __iomem *base;
> +
> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> + if (!res) {
> + dev_warn(dev, "Skipping QoS, failed to get resource\n");
Why is this a warning? If the MMIO is not required, your driver should
not spawn warnings.
> + goto skip_qos_config;
> + }
> +
> + base = devm_ioremap(dev, res->start, resource_size(res));
Combine these two (there's a helper for that).
> + if (IS_ERR(base)) {
> + dev_warn(dev, "Skipping QoS, ioremap failed: %ld\n", PTR_ERR(base));
> + goto skip_qos_config;
> + };
> +
> + qp->regmap = devm_regmap_init_mmio(dev, base, desc->config);
> +
Drop blank line.
> + if (IS_ERR(qp->regmap)) {
> + dev_warn(dev, "Skipping QoS, regmap failed; %ld\n", PTR_ERR(qp->regmap));
> + goto skip_qos_config;
> + }
> +
> + qp->num_clks = devm_clk_bulk_get_all(qp->dev, &qp->clks);
> + if (qp->num_clks < 0) {
> + dev_warn(dev, "Skipping QoS, failed to get clk: %d\n", qp->num_clks);
dev_info(), because current binding sais clocks are not required and you
are not allowed to affect ABI. While ABI here does not look broken,
spawning new warnings to proper users is not welcomed.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-03-06 8:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 7:30 [PATCH v3 0/4] Add support for QoS configuration Odelu Kukatla
2024-03-06 7:30 ` [PATCH v3 1/4] interconnect: qcom: icc-rpmh: Add QoS configuration support Odelu Kukatla
2024-03-06 8:31 ` Krzysztof Kozlowski [this message]
2024-03-20 17:51 ` Odelu Kukatla
2024-03-06 16:18 ` Konrad Dybcio
2024-03-20 17:59 ` Odelu Kukatla
2024-03-06 7:30 ` [PATCH v3 2/4] interconnect: qcom: sc7280: enable QoS programming Odelu Kukatla
2024-03-06 16:25 ` Konrad Dybcio
2024-03-20 18:05 ` Odelu Kukatla
2024-03-06 7:30 ` [PATCH v3 3/4] dt-bindings: interconnect: add clock property to enable QOS on SC7280 Odelu Kukatla
2024-03-06 8:26 ` Krzysztof Kozlowski
2024-03-20 17:08 ` Odelu Kukatla
2024-03-06 7:30 ` [PATCH v3 4/4] arm64: dts: qcom: sc7280: Add clocks for QOS configuration Odelu Kukatla
2024-03-12 10:35 ` Konrad Dybcio
2024-03-20 18:07 ` Odelu Kukatla
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=e7105dd7-68ff-4af6-b91e-56b6e50ff949@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_mdtipton@quicinc.com \
--cc=quic_okukatla@quicinc.com \
--cc=quic_rlaggysh@quicinc.com \
--cc=robh@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