From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 90518CE834F for ; Mon, 30 Sep 2024 14:45:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:MIME-Version:Date:Message-Id:Subject:References:In-Reply-To:Cc: To:From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=Pb2llYi6quXR1Qjbzb6Y/n9UNAPf4wNGcZ9g68cJ7gw=; b=d4CgCVVfV4XSKQ9c2WKQjCb8yg LFvIlTjIfTOntmT+30LMelAWBlbI28wZiAG4kCwHCOjmtqH39WQeaOy/EJqACu5lozbslpA5E7egr g1hxTe3jlr5p/Zbuu6/PcpO/qm7DXegqhwVWoyTGKLQXsKJMNrYNa0oogcGesr8CY5gSmv2PyYWnx 5eXiB4ayp2OohdaqM3msHnuQhIsUWiGatOFQ003EePq/f0GLmgpxpJqXZw/0Ab7Wo7/eQ3xTCA8XI zD71MEBDrQL7ae9QonW1dSkBsekB1fSsLiqRrxi/zRK+G+5prPBtc3a/UrZ/iySwXaD4ZPlB8CPJh H7bItj3A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1svHe2-0000000HXOH-47TO; Mon, 30 Sep 2024 14:45:02 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1svHcp-0000000HWyV-1k1o for linux-arm-kernel@lists.infradead.org; Mon, 30 Sep 2024 14:43:48 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 4D5F95C1008; Mon, 30 Sep 2024 14:43:42 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6F900C4CEC7; Mon, 30 Sep 2024 14:43:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1727707426; bh=Q2YuJhchLQ06poSHZTzxtq2r4V1ioxkny0f6QHo+LAU=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=ey1iSMRhogguUBkHmM2gdxTFxCJ7EEaHnXOcz/fEy5qg/C9Td8rGsuQ7vjC2cL8XD J/Vt2agO32fRKlkQCoZOfyveSJl4UO9WKfZL2cH50mSKPTJUxL63RaT/nTapEKmjwI 1Cr6J+GBsxFOxBkmlzGYyMYW1JUXtGzyAM2ELYUjb5n0WkouJAgnLmBCZfXt2OVyuZ vRdGVUn9N86kTUKjUUbSPIBAuk9JsQtvf/Yn/i2XJteH/y3yeQVHGou5ufb8pf2bnY LMitkZa96iQc1mxIOgHrJGnN2GobBb94MfFWkBuqDK76Aqse7jJ8MA30wHU14q1Jrm R5PpBJR8u5BRQ== From: Lee Jones To: Lee Jones , Nishanth Menon Cc: Arnd Bergmann , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Mark Brown , Shawn Guo , linux-arm-msm@vger.kernel.org, Bjorn Andersson , bcm-kernel-feedback-list@broadcom.com, Florian Fainelli , linux-stm32@st-md-mailman.stormreply.com, Alexandre Torgue In-Reply-To: <20240903184710.1552067-1-nm@ti.com> References: <20240903184710.1552067-1-nm@ti.com> Subject: Re: (subset) [PATCH V2] mfd: syscon: Use regmap max_register_is_0 as needed Message-Id: <172770742318.523866.16912261914335612487.b4-ty@kernel.org> Date: Mon, 30 Sep 2024 15:43:43 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Mailer: b4 0.13.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240930_074347_519927_EEDB0F58 X-CRM114-Status: UNSURE ( 8.28 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, 03 Sep 2024 13:47:10 -0500, Nishanth Menon wrote: > syscon has always set the optional max_register configuration of > regmap to ensure the correct checks are in place. However, a recent > commit 0ec74ad3c157 ("regmap: rework ->max_register handling") > introduced explicit configuration in regmap framework for register > maps that is exactly 1 register, when max_register is pointing to a > valid register 0. This commit solved a previous limitation of regmap > framework. > > [...] Applied, thanks! [1/1] mfd: syscon: Use regmap max_register_is_0 as needed commit: bf5b2ddf06da57fa623c11d599697a98f1007752 -- Lee Jones [李琼斯]