From: Fil Dunsky <filipp.dunsky@gmail.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v5 0/2] gpio: Add Cortina Systems CS75xx GPIO driver
Date: Thu, 19 Nov 2026 18:08:33 +0300 [thread overview]
Message-ID: <179510091368.5.7008617353574583652@gmail.com> (raw)
In-Reply-To: <p3qjb3oncivinobxa5wvwwkql3xmjfujdwmxigyxczk5ya23ua@xayhbwbn35af>
Hi Bart,
On Thu, Nov 19, 2026 at 02:42:27PM +0100, Bartosz Golaszewski wrote:
> The driver looks good but I cannot pick it up while it references a
> Kconfig symbol that's not upstream.
You're right. I have replaced ARCH_CORTINA_ACCESS || COMPILE_TEST with
OF. The driver only uses generic MMIO, GPIO and IRQ APIs; HAS_IOMEM is
already required by the enclosing MMIO GPIO menu. There is no need to
keep an architecture-specific condition here.
I checked built-in and module builds on ARM with GCC and x86-64 with
Clang, with OF=y and COMPILE_TEST=n, using just the GPIO series on
v7.4-rc1 without the CS75xx platform series. All four builds passed,
including vmlinux for the built-in cases and the modules for the modular
cases. The GPIO driver code is unchanged.
I am sending v6 with this Kconfig change and an updated cover letter.
Thanks,
Fil
prev parent reply other threads:[~2026-11-19 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 11:02 [PATCH v5 0/2] gpio: Add Cortina Systems CS75xx GPIO driver Fil Dunsky via B4 Relay
2026-11-19 11:02 ` [PATCH v5 1/2] dt-bindings: gpio: Add Cortina Systems CS7542 GPIO controller Fil Dunsky via B4 Relay
2026-11-19 11:02 ` [PATCH v5 2/2] gpio: Add Cortina Systems CS75xx GPIO driver Fil Dunsky via B4 Relay
2026-11-19 13:42 ` [PATCH v5 0/2] " Bartosz Golaszewski
2026-11-19 15:08 ` Fil Dunsky [this message]
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=179510091368.5.7008617353574583652@gmail.com \
--to=filipp.dunsky@gmail.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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