From: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
James Cowgill <james.cowgill@blaize.com>,
Matt Redfearn <matthew.redfearn@blaize.com>,
Neil Jones <neil.jones@blaize.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 5/5] arm64: defconfig: Add VeriSilicon GPIO driver
Date: Wed, 12 Feb 2025 16:20:38 +0000 [thread overview]
Message-ID: <259dd121-8c49-44f7-b8f6-e0b68ab88304@blaize.com> (raw)
In-Reply-To: <9442a87b-ab61-40e3-bbf0-caae87c5731a@kernel.org>
On 12/02/2025 15:25, Krzysztof Kozlowski wrote:
> On 12/02/2025 14:46, Nikolaos Pasaloukos wrote:
>> Add support for VeriSilicon GPIO controller.
> You enable not add support, but still the main question is: Why? Which
> devices needs it? Why this cannot be a module?
Hi Krzysztof,
Thank you for your fast review and apologies for the typo. I forgot to
mention on the commit message but I have mentioned in the cover letter
that the driver is needed for the Blaize BLZP1600 CB2 board which is
already supported on v6.14. I will fix the commit message on V2.
This driver enables support (controls) for multiple peripherals on
the board, like Ethernet for NFS boot, SD and eMMC to load modules from
these media. Without this driver build in the kernel, it will be hard to
mount a filesystem and load modules.
Kind regards,
Nikolaos
>
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-02-12 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 13:46 [PATCH 0/5] Add support for VeriSilicon APB GPIO driver Nikolaos Pasaloukos
2025-02-12 13:46 ` [PATCH 1/5] dt-bindings: Add VeriSilicon vendor prefix Nikolaos Pasaloukos
2025-02-12 17:01 ` Krzysztof Kozlowski
2025-02-12 13:46 ` [PATCH 2/5] dt-bindings: Document VeriSilicon APB GPIO driver Nikolaos Pasaloukos
2025-02-12 17:08 ` Krzysztof Kozlowski
2025-02-12 13:46 ` [PATCH 4/5] arm64: dts: blaize-blzp1600: Add VeriSilicon GPIO support Nikolaos Pasaloukos
2025-02-12 13:46 ` [PATCH 3/5] gpio: vsiapb: Add VeriSilicon APB support Nikolaos Pasaloukos
2025-02-12 22:05 ` Linus Walleij
2025-02-12 13:46 ` [PATCH 5/5] arm64: defconfig: Add VeriSilicon GPIO driver Nikolaos Pasaloukos
2025-02-12 15:25 ` Krzysztof Kozlowski
2025-02-12 16:20 ` Nikolaos Pasaloukos [this message]
2025-02-12 16:28 ` Bartosz Golaszewski
2025-02-12 16:32 ` Nikolaos Pasaloukos
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=259dd121-8c49-44f7-b8f6-e0b68ab88304@blaize.com \
--to=nikolaos.pasaloukos@blaize.com \
--cc=brgl@bgdev.pl \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.cowgill@blaize.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.redfearn@blaize.com \
--cc=neil.jones@blaize.com \
--cc=robh@kernel.org \
--cc=will@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