Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
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
Message-ID: <168973689569.3446802.8548756605942770542.b4-ty@kernel.org>
In-Reply-To: <20230716022804.21239-1-ansuelsmth@gmail.com>
References: <20230716022804.21239-1-ansuelsmth@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk


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>