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 F181236655B for ; Wed, 11 Feb 2026 09:47:56 +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=1770803277; cv=none; b=F/4Ds3+UR7HI7JFDlHyagvYtNy4CcJ/ErMNmlnJCT/5g5ADMfFoi2Kfd/CJXe8PShxBMenasLtJFdywclnvB8V9Uuds0Hpy4QMsUAanUt+VdwweJjIhbhLs7+0EaTn3THBVdwhNlR0XuKEPloDrgSzuUkNboRcfA87RVM0n329k= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770803277; c=relaxed/simple; bh=fP4SfOgARQ7v/Brjb9O3+lwzxomBul6ME0wlt0f7dSM=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=eJw7VxHPy3I3GhFeHey3/nFTGRSKDukqa3UZU/GMkHYAmZMoyQlAfIlJ6wYzn0qnXI70wZ14L4NnedVxaB3hSseA2RZrDIWxSZpnxyf/vu4awPRBccY10GvMDbyiIRLFSjp9RHLNKTSTTqpGSf/S5d1fYfwab4E1cnA5ofvG/R8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=jxPS6QQr; 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="jxPS6QQr" Received: by smtp.kernel.org (Postfix) with ESMTPSA id ADC02C2BCB0 for ; Wed, 11 Feb 2026 09:47:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1770803276; bh=fP4SfOgARQ7v/Brjb9O3+lwzxomBul6ME0wlt0f7dSM=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=jxPS6QQrjrPMrsSQhMh/wWB5EpDpCaVZumokW8m+WSKUXusJqx717HuMsa46BkvYo 4fWdrGtt6jTureCnwwfPQZ1isxZtQ83dooeF+7G6LK8QvorYweVeOS5uIGsf2tL/8h EXJ15RB2jvqRCyg/u/8GaaX/RbxM74rK9jj2qk8ZfDSWDIYFGNjYd28WCfFjmlfX2N a31hCwsVFPdfQWBRwPsGrdhH2BlufKBt0X9G+dKpjB/Z48JeYza0Ti37sehaU+1Pf+ a+wccplsz1kn2i/hNRLwcGZY7vaCGqPRONVwCjguDKBmSENq62cXyGuedwN5qU4Fn4 OuQkI0UJixPgw== Received: by mail-lj1-f179.google.com with SMTP id 38308e7fff4ca-385c23b88e8so61233831fa.3 for ; Wed, 11 Feb 2026 01:47:56 -0800 (PST) X-Forwarded-Encrypted: i=1; AJvYcCVCRxKOo1KdS207JtGcD+X6wsDU74YTF5StDhJD7wXPOl6Iw4SV3423HR3lhoyTbyaOc5i7lqJWSvgSwTU=@vger.kernel.org X-Gm-Message-State: AOJu0YzxXuHgqbL8NOkoTvbuvPgy9j1nugW8cfUN00zCKjLpMYVHEsMk LCGdBLPx+wvtkqeO9w0kHjIokiaVTn6T/x330RPW1Fi8JEpZWfBajNnDmm/EhgezmflUbjyM4E1 wxGQQC4oPyt9mNMdU5eYVoki14pN+nwFtK2hjx3moYA== X-Received: by 2002:a05:651c:31d0:b0:385:9b50:91a2 with SMTP id 38308e7fff4ca-38705403fffmr5340821fa.10.1770803275257; Wed, 11 Feb 2026 01:47:55 -0800 (PST) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <20260211081355.3028947-1-james.hilliard1@gmail.com> <20260211081355.3028947-2-james.hilliard1@gmail.com> In-Reply-To: <20260211081355.3028947-2-james.hilliard1@gmail.com> From: Bartosz Golaszewski Date: Wed, 11 Feb 2026 10:47:42 +0100 X-Gmail-Original-Message-ID: X-Gm-Features: AZwV_QhOgiVsYyK_jjpPbKXaVcpSjcjhcm9AGxleSbT7RLMOVXp0xwFXS4jxvVw Message-ID: Subject: Re: [PATCH v2 2/2] gpio: aggregator: add gpio-aggregator DT compatible To: James Hilliard Cc: linux-gpio@vger.kernel.org, Geert Uytterhoeven , Linus Walleij , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Alexander Stein , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Feb 11, 2026 at 9:14=E2=80=AFAM James Hilliard wrote: > > Add an OF match entry for "gpio-aggregator" to support plain GPIO > forwarding from devicetree without delay semantics. > > This allows exposing selected lines as a logical GPIO controller with > stable aggregated offsets, so consumers can reference forwarded lines > instead of physical controller offsets. It also allows creating bundled > groups of named lines that can be exposed to userspace as a convenient > virtual gpiochip interface. Using "gpio-delay" for this case is not > suitable because it enables delay features and requires 3-cell GPIO > specifiers. > > Signed-off-by: James Hilliard > --- > Changes v1 -> v2: > - Split DT schema into a separate patch > (suggested by Krzysztof Kozlowski) > - Expand commit message rationale and use-case explanation > (suggested by Krzysztof Kozlowski) > - Clarify userspace use case with bundled named line groups > --- > drivers/gpio/gpio-aggregator.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/drivers/gpio/gpio-aggregator.c b/drivers/gpio/gpio-aggregato= r.c > index 416f265d09d0..a09752fc5fe2 100644 > --- a/drivers/gpio/gpio-aggregator.c > +++ b/drivers/gpio/gpio-aggregator.c > @@ -1635,6 +1635,9 @@ static int gpio_aggregator_probe(struct platform_de= vice *pdev) > } > > static const struct of_device_id gpio_aggregator_dt_ids[] =3D { > + { > + .compatible =3D "gpio-aggregator", > + }, > { > .compatible =3D "gpio-delay", > .data =3D (void *)FWD_FEATURE_DELAY, > -- > 2.43.0 > Regardless of the DT bindings - this change is perfectly fine. We do that for other "virtual" devices like gpio-sim, gpio-virtuser, etc. I would just ask you to document it under Documentation/admin-guide/gpio/gpio-aggregator.rst. Bartosz