From: Bjorn Andersson <andersson@kernel.org>
To: Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Ohad Ben-Cohen <ohad@wizery.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Christian Marangi <ansuelsmth@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] hwspinlock: qcom: add missing regmap config for SFPB MMIO implementation
Date: Tue, 18 Jul 2023 20:21:48 -0700 [thread overview]
Message-ID: <168973689569.3446802.8548756605942770542.b4-ty@kernel.org> (raw)
In-Reply-To: <20230716022804.21239-1-ansuelsmth@gmail.com>
On Sun, 16 Jul 2023 04:28:04 +0200, Christian Marangi wrote:
> Commit 5d4753f741d8 ("hwspinlock: qcom: add support for MMIO on older
> SoCs") introduced and made regmap_config mandatory in the of_data struct
> but didn't add the regmap_config for sfpb based devices.
>
> SFPB based devices can both use the legacy syscon way to probe or the
> new MMIO way and currently device that use the MMIO way are broken as
> they lack the definition of the now required regmap_config and always
> return -EINVAL (and indirectly makes fail probing everything that
> depends on it, smem, nandc with smem-parser...)
>
> [...]
Applied, thanks!
[1/1] hwspinlock: qcom: add missing regmap config for SFPB MMIO implementation
commit: 23316be8a9d450f33a21f1efe7d89570becbec58
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-07-19 3:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 2:28 [PATCH] hwspinlock: qcom: add missing regmap config for SFPB MMIO implementation Christian Marangi
2023-07-19 3:21 ` Bjorn Andersson [this message]
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=168973689569.3446802.8548756605942770542.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=stable@vger.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