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;
Feedback-ID: i56a14606:Fastmail
User-Agent: Cyrus-JMAP/3.7.0-alpha0-1115-g8b801eadce-fm-20221102.001-g8b801ead
Mime-Version: 1.0
Message-Id: <0c621478-6429-4a7c-9c14-5fab7017d1e8@app.fastmail.com>
In-Reply-To: <20221209013309.407879-1-jk@codeconstruct.com.au>
References: <20221209013309.407879-1-jk@codeconstruct.com.au>
Date:   Fri, 09 Dec 2022 12:17:36 +0100
From:   "Arnd Bergmann" <arnd@arndb.de>
To:     "Jeremy Kerr" <jk@codeconstruct.com.au>,
        devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
        "Lee Jones" <lee@kernel.org>, "Rob Herring" <robh+dt@kernel.org>,
        "Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
        "Philipp Zabel" <p.zabel@pengutronix.de>,
        "Mark Brown" <broonie@kernel.org>
Subject: Re: [RFC PATCH v2 0/3] Add reset control for mfd syscon devices
Content-Type: text/plain
Precedence: bulk

On Fri, Dec 9, 2022, at 02:33, Jeremy Kerr wrote:
> This RFC series adds a facility for syscon devices to control a reset
> line when probed; we have instances of simple register-only syscon
> resources that need deassertion of a reset line for the register set to
> be accessible.
>
> Rather than requiring a specific driver to implement this, it'd be nice
> to use the generic syscon device and the generic resets linkage to do
> so.
>
> Any comments/queries/etc are most welcome.

The syscon side looks good to me,

Reviewed-by: Arnd Bergmann <arnd@arndb.de>