From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from metis.whiteo.stw.pengutronix.de (metis.whiteo.stw.pengutronix.de [185.203.201.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4459B207A32 for ; Tue, 21 Oct 2025 09:31:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.203.201.7 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761039110; cv=none; b=pNgKKw0KKGw5fTHcccAIUy43UmtuijKaUSQRoVBMFpwCqQ33GebTKB0MqWKIaGA+wrXcffYYlKOWcF9qC+ATAEFnZEAjFZ3hH7HxkWNt+dDXo6co1Oji2wM2j+0B4BFQzNl7eg8AyORCW4idJzDsTEUdcrnkXMFwFLL++UvTdr4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761039110; c=relaxed/simple; bh=r24GW0i1udPh6MxH0KHVOL1WuNqWbnMtEjp8otN7o5o=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=jgQuYMjsoOnTjtGVOJ/zk03vNfNbs5rGqMxnMlHy5saLnLi8WVd2cp59stXKJbDyzejk1Gc2GvA3we0f5B+95VdXys3mHht7hNz1ohTFcZc+smtYwVy758QowYYZiRFXvUHHB3vPJtQYtW6pQXfJMjjj4ErNK3CkJXOztZWdXFs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=pengutronix.de; spf=pass smtp.mailfrom=pengutronix.de; arc=none smtp.client-ip=185.203.201.7 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=pengutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pengutronix.de Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1vB8iR-0003nf-Dc; Tue, 21 Oct 2025 11:31:39 +0200 Received: from lupine.office.stw.pengutronix.de ([2a0a:edc0:0:900:1d::4e] helo=lupine) by drehscheibe.grey.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vB8iQ-004hLI-1Z; Tue, 21 Oct 2025 11:31:38 +0200 Received: from pza by lupine with local (Exim 4.98.2) (envelope-from ) id 1vB8iQ-000000004Fy-1ior; Tue, 21 Oct 2025 11:31:38 +0200 Message-ID: <050d74d7619bdfdf5ca81d8914a2a8836a0d4e2e.camel@pengutronix.de> Subject: Re: [PATCH 7/9] reset: make the provider of reset-gpios the parent of the reset device From: Philipp Zabel To: Bartosz Golaszewski Cc: Linus Walleij , Andy Shevchenko , Daniel Scally , Heikki Krogerus , Sakari Ailus , Greg Kroah-Hartman , "Rafael J. Wysocki" , Danilo Krummrich , Krzysztof Kozlowski , linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, Bartosz Golaszewski Date: Tue, 21 Oct 2025 11:31:38 +0200 In-Reply-To: References: <20251006-reset-gpios-swnodes-v1-0-6d3325b9af42@linaro.org> <20251006-reset-gpios-swnodes-v1-7-6d3325b9af42@linaro.org> <95bbec130437846d4b902ce4161ccf0f33c26c59.camel@pengutronix.de> <075a4511a6ae4b047599757d41b559c6b7cf9d0f.camel@pengutronix.de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.56.1-1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-SA-Exim-Connect-IP: 2a0a:edc0:0:c01:1d::a2 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.whiteo.stw.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org On Di, 2025-10-21 at 11:27 +0200, Bartosz Golaszewski wrote: > On Tue, Oct 21, 2025 at 11:17=E2=80=AFAM Philipp Zabel wrote: > >=20 > > On Mo, 2025-10-20 at 17:25 +0200, Bartosz Golaszewski wrote: > > > On Mon, Oct 6, 2025 at 5:19=E2=80=AFPM Philipp Zabel wrote: > > > > [...] could you take this > > > > opportunity to prepend a patch that splits the part under guard() i= nto > > > > a separate function? > > >=20 > > > If I'm being honest, I'd just make everything else use __free() as > > > well. Except for IDA, it's possible. > > >=20 > > > That being said: I have another thing in the works, namely converting > > > the OF code to fwnode in reset core. I may address this there as I'll > > > be moving stuff around. Does this make sense? > >=20 > > Yes. There was already a previous attempt at fwnode support [1], but we > > abandoned that when there was no use case anymore. > >=20 > > [1] https://lore.kernel.org/r/20220323095022.453708-3-clement.leger@boo= tlin.com > >=20 >=20 > Ah, what was the exact reason for abandoning this? It's not clear from > the email thread. >=20 > To be clear: I think that we can convert the core reset code to fwnode > without necessarily converting all the drivers right away. The use case vanished in patch review. No need to convert all existing drivers right away, but I'd like to see a user that benefits from the conversion. regards Philipp