From: Jonas Jelonek <jelonek.jonas@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v1 1/2] dt-bindings: gpio: add gpio-split controller
Date: Fri, 10 Oct 2025 10:27:31 +0200 [thread overview]
Message-ID: <22a99be5-b0ea-4f8c-8a2c-5024507a7e32@gmail.com> (raw)
In-Reply-To: <3118e300-f6de-42af-bd1b-ad13dc80537d@kernel.org>
Hi Krzysztof,
On 10.10.25 03:12, Krzysztof Kozlowski wrote:
> Instead, please fix the subsystem driver?
That's why I sent this as an RFC. I thought about this too but have no good
idea how to represent this in DT while keeping the existing bindings.
So I just thought this small driver would be the easier way, possibly being
useful for other potential usecases.
But sure, if this is the only way to go I'll have to RFC this at the SFP
driver side asking for any ideas how this could be achieved.
> I have also doubts we actually want it in DT, because we tie the
> limitation of Linux drivers to bindings.
>
>
> Best regards,
> Krzysztof
Best regards,
Jonas
next prev parent reply other threads:[~2025-10-10 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 22:34 [RFC PATCH v1 0/2] add support for splitting GPIOs Jonas Jelonek
2025-10-09 22:35 ` [RFC PATCH v1 1/2] dt-bindings: gpio: add gpio-split controller Jonas Jelonek
2025-10-10 1:12 ` Krzysztof Kozlowski
2025-10-10 8:27 ` Jonas Jelonek [this message]
2025-10-14 8:23 ` Linus Walleij
2025-10-16 15:36 ` Jonas Jelonek
2025-10-09 22:35 ` [RFC PATCH v1 2/2] gpio: add gpio-split driver Jonas Jelonek
2025-10-14 8:37 ` Linus Walleij
2025-10-16 15:37 ` Jonas Jelonek
2025-10-16 22:12 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22a99be5-b0ea-4f8c-8a2c-5024507a7e32@gmail.com \
--to=jelonek.jonas@gmail.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).