On Wed, Feb 12, 2025 at 5:20 PM Nikolaos Pasaloukos <nikolaos.pasaloukos@xxxxxxxxxx> 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
