From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 1D34730F7E8 for ; Tue, 6 Jan 2026 12:25:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767702343; cv=none; b=HbPSk9W/dEbQb/G84NWPLBwDrzi2kBCnOD6cnhjuss6vvdBFN399dkzbh+GFFjKvvRyF3FpiylOhWOkm1lUftDUiWNX9DM1An0T5YvFeuBKfmp8IWwTb0xoAJJLfe6CavXb6oSuUUnc/ghwi2xPPFg9i5OgLrifWPyTfm6el/Sg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767702343; c=relaxed/simple; bh=wg6p23gjDukL2cRVJ78Oc5P5KU7hnB4MDtRCIp1BtIo=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=IBy2g1fZ/syMni7sTkBFJFf5kcG1dxoWn2mDt0XGrdmRXEFnTfWorDAriZBI4NK6FtSdXoKWXJR/CAU4Ob1sScqwXccxUv+hubLjZz7jWZefWqy4NzzFQdR9cJIFEn8kM9vUBBn3PKCpIad3FRTM9qZaaLfoIMeTBZ5sAUwVPnQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=aJthu95e; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="aJthu95e" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B6289C19425 for ; Tue, 6 Jan 2026 12:25:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1767702342; bh=wg6p23gjDukL2cRVJ78Oc5P5KU7hnB4MDtRCIp1BtIo=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=aJthu95es2uZpaCdxmSWIe01j3tHZj0B4FpMqAvoL3Oso+KZqJ8HNHQAsXx6D8sJc 0rdlAtHyGNN+yNf5AoD18s2eOabbv3dqy2HUDH32MvbfmbYdNEPILyQtAbHVfie/Cr u41bhGxdXLHYZzASUM1cW6VOd3GzPEYnzKEhovwV5tOLSpBNDD2RQH88eVieQDGCXA Sfg7Y/GZcSE8Wg1ZTQSzNLQupG7S4zoIloNH1Rx5+OfmDMc32zEuaGR/zqm3n/aP08 5IyxHT1bIru0qf3tR31f4xSVO37TNVg1HVvO7QOgiy1GqrbYzWHoIVozKwhsAQJj4W cBTgMqhcUsuWQ== Received: by mail-lf1-f48.google.com with SMTP id 2adb3069b0e04-5959d9a8eceso956460e87.3 for ; Tue, 06 Jan 2026 04:25:42 -0800 (PST) X-Forwarded-Encrypted: i=1; AJvYcCU74fpCF/MYkOoWIKPEfQzMEfdEbqKP6fvA9lWHFpo/svDqi/r7jkwmokt6kdYWhSPyZv2OtSktXMMftGw=@vger.kernel.org X-Gm-Message-State: AOJu0YwvvyIl8sQTsE6iSfpMGYK/mGQgHX3JIq9QMPt/UhEaFpVI3Kto D/wNaYEVcsUB1abVdWlwoWyqeIPDT0bf2ra+lPy9tIiBMCLrqTV3Dle5qFWsW4inX9URpVcARqk Ub+UIFjH7QoP9073LAfqi/QbiuWvsNLueGF/q73RRVw== X-Google-Smtp-Source: AGHT+IE6DFYY/3rRfXe7XSzL1OxNQpFcEuniQY70NWdKpsxhOEm1y3QR6wUF6cLmyvwNYXoUYahLVw33DzhaMW8X7tU= X-Received: by 2002:a05:6512:2350:b0:59b:4213:75e6 with SMTP id 2adb3069b0e04-59b6521e2f5mr1113951e87.21.1767702341395; Tue, 06 Jan 2026 04:25:41 -0800 (PST) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <20251222-gpio-shared-reset-gpio-proxy-v1-0-8d4bba7d8c14@oss.qualcomm.com> <20251222-gpio-shared-reset-gpio-proxy-v1-3-8d4bba7d8c14@oss.qualcomm.com> <00107523-7737-4b92-a785-14ce4e93b8cb@samsung.com> <9948f635-b753-44cf-8977-7fee4cfb6e3d@sirena.org.uk> In-Reply-To: <9948f635-b753-44cf-8977-7fee4cfb6e3d@sirena.org.uk> From: Bartosz Golaszewski Date: Tue, 6 Jan 2026 13:25:29 +0100 X-Gmail-Original-Message-ID: X-Gm-Features: AQt7F2ptws5Ge5GRn0wLuORiWFu5YPp03xp3H1Zu7XyDX54f2WmFWc1qQlA9EVA Message-ID: Subject: Re: [PATCH 3/3] gpio: shared: allow sharing a reset-gpios pin between reset-gpio and gpiolib To: Mark Brown Cc: Marek Szyprowski , Bartosz Golaszewski , Linus Walleij , linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, Linus Walleij Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jan 6, 2026 at 1:21=E2=80=AFPM Mark Brown wrot= e: > > On Mon, Jan 05, 2026 at 12:50:22PM +0100, Marek Szyprowski wrote: > > On 22.12.2025 11:01, Bartosz Golaszewski wrote: > > > We currently support sharing GPIOs between multiple devices whose dri= vers > > > use either the GPIOLIB API *OR* the reset control API but not both at > > > the same time. > > > This patch landed in linux-next as commit 49416483a953 ("gpio: shared: > > allow sharing a reset-gpios pin between reset-gpio and gpiolib"). In my > > tests I found that it breaks booting and triggers warnings on some of m= y > > test boards. Reverting it on top of next-20260105 fixes those issues. > > Let me know if I can help debugging this issue. > > Not sure if it's this specific patch (one of the bisects identified it, > but I'm seeing others going to the merge commit for the gpio fixes > branch) but I'm also seeing issues with gpios. pwrseq is affected on > several platforms after backtraces that look a lot like the one that > Marek is seeing on Raspberry Pi 3B+ (which I also see). This breaks at > least the WiFi: > > [ 13.475670] platform wifi-pwrseq: deferred probe pending: pwrseq_simpl= e: reset control not ready > > Raspberry Pi 4: > > https://lava.sirena.org.uk/scheduler/job/2335022#L1200 > > Toradax Mallow (TI K3): > > https://lava.sirena.org.uk/scheduler/job/2335415#L1457 Hi! These two should be fixed by the following series: https://lore.kernel.org/all/20260106-gpio-shared-fixes-v2-0-c7091d2f7581@os= s.qualcomm.com/ Could you please give it a try and possibly add your T-b? Bart