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 B6D644AC786 for ; Thu, 8 Jan 2026 12:02:12 +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=1767873737; cv=none; b=Gbk4MNSMsNzqPCJS+DAJjfD0BfesKI9m53LGAg6P0rOY/rAnPUpcbCvYaEiN7HGk344hFvMUDP64TcgL/7bni5GWWcujLxGEWcX/YK5UHX5hF+vdtJi5QEwCkpa/HB9cpVMRjMYyt9c38JnemYC4Ck5jg/nkBdif/Hf2monEBk0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767873737; c=relaxed/simple; bh=JEBv/LFavLWvuZ+RD6HpZxezctAK2EQR6JS+/TfDwrI=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=gtvcjV2bMj+GD0RoYzazx6P550ZWA/q5xBBPzKfNULPhFqJbbmRdOzwTVkWaCIj1IEDQF9wSB5KHOnqlE0IsGISvY+Srh1XSzV73yJBi55tfhDdq4okkaIYf93O5yf38Aw9gzGJSD5vSmJXriJPEk9TuK2bnSA5gMnMUZpP/INo= 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 1vdoiQ-0003KQ-6e; Thu, 08 Jan 2026 13:02:10 +0100 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 1vdoiP-009fc8-2U; Thu, 08 Jan 2026 13:02:09 +0100 Received: from pza by lupine with local (Exim 4.98.2) (envelope-from ) id 1vdoiP-000000006UN-2wZK; Thu, 08 Jan 2026 13:02:09 +0100 Message-ID: Subject: Re: [PATCH] reset: gpio: add the "compatible" property From: Philipp Zabel To: Bartosz Golaszewski Cc: Krzysztof Kozlowski , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, Bartosz Golaszewski , Bartosz Golaszewski Date: Thu, 08 Jan 2026 13:02:09 +0100 In-Reply-To: References: <20251121135739.66528-1-brgl@bgdev.pl> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.56.2-0+deb13u1 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 Hi Bartosz, On Mo, 2025-12-08 at 23:57 -0800, Bartosz Golaszewski wrote: > On Tue, 25 Nov 2025 11:43:01 +0100, Philipp Zabel said: > > On Fr, 2025-11-21 at 14:57 +0100, Bartosz Golaszewski wrote: > > > From: Bartosz Golaszewski > > >=20 > > > In order to correctly handle the interaction between the reset-gpio > > > devices and shared GPIOs managed by GPIOLIB, we need to be able to > > > identify the former. Add the "compatible" property to allow us to use > > > the device_is_compatible() helper. > > >=20 > > > Signed-off-by: Bartosz Golaszewski > > > --- > > > Philipp: this can go directly into your branch, I will fix the GPIO p= art > > > in the next cycle. For now it just parses the device name. > >=20 > > Applied to reset/next, thanks! > >=20 > > [1/1] reset: gpio: add the "compatible" property > > https://git.pengutronix.de/cgit/pza/linux/commit/?id=3Da0d57f7504= b6 > >=20 > > regards > > Philipp > >=20 >=20 > Hi Phillipp! >=20 > I realized this didn't make your v6.19-rc1 PR. Any chance you could make = it > into an immutable branch or maybe you could back it out from your branch = and > allow me to take it with your Ack? I have a WiP patch that fixes one rema= ining > issue in the interaction between reset-gpios and shared GPIOs. I want to = send > it for rc1 or rc2 but I would prefer to use device_is_compatible() in it. Sorry for the delay, I didn't get to this before hibernating. I've now rebased the patch onto v6.19-rc1 now and made an immutable branch for you to fetch: The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8= : Linux 6.19-rc1 (2025-12-14 16:05:07 +1200) are available in the Git repository at: https://git.pengutronix.de/git/pza/linux.git reset/gpio-compatible for you to fetch changes up to b3d8508351af7f6366a0a18068c194b399ead2c3: reset: gpio: add the "compatible" property (2026-01-08 12:25:20 +0100) ---------------------------------------------------------------- Bartosz Golaszewski (1): reset: gpio: add the "compatible" property drivers/reset/core.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) regards Philipp