linux-kernel - Re: [PATCH 2/2] media: pci: mgb4: remove bogus 'select' statements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <78427021-ddc0-45b6-a16b-bf8bc8f84003@app.fastmail.com>
Date:   Tue, 24 Oct 2023 15:27:30 +0200
From:   "Arnd Bergmann" <arnd@...db.de>
To:     "Arnd Bergmann" <arnd@...nel.org>,
        "Martin Tuma" <martin.tuma@...iteqautomotive.com>,
        "Mauro Carvalho Chehab" <mchehab@...nel.org>,
        "Hans Verkuil" <hverkuil-cisco@...all.nl>,
        dmaengine@...r.kernel.org, "Lizhi Hou" <lizhi.hou@....com>,
        "Brian Xu" <brian.xu@....com>,
        "Raj Kumar Rampelli" <raj.kumar.rampelli@....com>,
        "Vinod Koul" <vkoul@...nel.org>
Cc:     linux-media@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] media: pci: mgb4: remove bogus 'select' statements

On Mon, Oct 23, 2023, at 18:05, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@...db.de>
>
> As this is just a regular device driver, it has no business force-enabling
> other drivers in the system, it should be entirely independent of the
> implementation of the spi-nor layer or the specific DMA engine.
>
> The IIO symbols that are selected here are library modules that
> are legitimately used.
>
> Fixes: 0ab13674a9bd ("media: pci: mgb4: Added Digiteq Automotive MGB4 driver")
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
> ---
>  drivers/media/pci/mgb4/Kconfig | 4 ----
>  1 file changed, 4 deletions(-)
>
> diff --git a/drivers/media/pci/mgb4/Kconfig b/drivers/media/pci/mgb4/Kconfig
> index f2a05a1c8ffa..b90347c7f19b 100644
> --- a/drivers/media/pci/mgb4/Kconfig
> +++ b/drivers/media/pci/mgb4/Kconfig
> @@ -6,10 +6,6 @@ config VIDEO_MGB4
>  	select VIDEOBUF2_DMA_SG
>  	select IIO_BUFFER
>  	select IIO_TRIGGERED_BUFFER
> -	select I2C_XILINX
> -	select SPI_XILINX
> -	select MTD_SPI_NOR
> -	select XILINX_XDMA

Apparently, the XDMA reference was in fact needed, as MGB4
calls some exported symbols from that particular dmaengine
driver:

aarch64-linux-ld: drivers/media/pci/mgb4/mgb4_core.o: in function `init_i2c': mgb4_core.c:(.text+0x3ec): undefined reference to `xdma_get_user_irq'
aarch64-linux-ld: mgb4_core.c:(.text+0x404): undefined reference to `xdma_enable_user_irq'

I couldn't easily figure out what a 'user_irq' is here,
but I wonder if this is the expected way to use the DMA engine
layer. Maybe this should have been a nested irqchip instead,
or it should be encoded in the DMA request specifier?

     Arnd