[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9549d5f6-a90a-48e7-a320-23487a6470cf@blaize.com>
Date: Wed, 12 Feb 2025 16:32:03 +0000
From: Nikolaos Pasaloukos <nikolaos.pasaloukos@...ize.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley
<conor+dt@...nel.org>,
James Cowgill <james.cowgill@...ize.com>,
Matt Redfearn <matthew.redfearn@...ize.com>,
Neil Jones <neil.jones@...ize.com>,
Linus Walleij
<linus.walleij@...aro.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 5/5] arm64: defconfig: Add VeriSilicon GPIO driver
On 12/02/2025 16:28, Bartosz Golaszewski wrote:
> On Wed, Feb 12, 2025 at 5:20 PM Nikolaos Pasaloukos
> <nikolaos.pasaloukos@...ize.com> wrote:
>> 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.
>>
> That's alright but typically you'd want to have something like:
>
> default y if ARCH_BLAIZE
>
> in the driver's Kconfig entry.
>
> Bart
Hi Bart,
Thank you for your suggestion. I will fix it on V2.
Kind regards,
Nikolaos
Powered by blists - more mailing lists