mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Vamsi Attunuru <vattunuru@marvell.com>
Cc: arnd@arndb.de, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: Kconfig: add a new dependency for MARVELL_CN10K_DPI
Date: Tue, 16 Jul 2024 06:26:03 -0700	[thread overview]
Message-ID: <20240716132603.GA3136577@thelio-3990X> (raw)
In-Reply-To: <20240711120115.4069401-1-vattunuru@marvell.com>

Hi Vamsi,

On Thu, Jul 11, 2024 at 05:01:15AM -0700, Vamsi Attunuru wrote:
> DPI hardware is an on-chip PCIe device on Marvell's arm64 SoC
> platforms. As Arnd suggested, CN10K belongs to ARCH_THUNDER
> lineage.
> 
> Patch makes mrvl_cn10k_dpi driver dependent on CONFIG_ARCH_THUNDER.
> 
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
> ---
>  drivers/misc/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> index 64fcca9e44d7..f3bb75384627 100644
> --- a/drivers/misc/Kconfig
> +++ b/drivers/misc/Kconfig
> @@ -588,6 +588,7 @@ config NSM
>  config MARVELL_CN10K_DPI
>  	tristate "Octeon CN10K DPI driver"
>  	depends on PCI
> +	depends on ARCH_THUNDER || COMPILE_TEST
>  	help
>  	  Enables Octeon CN10K DMA packet interface (DPI) driver which
>  	  intializes DPI hardware's physical function (PF) device's
> -- 
> 2.25.1
> 

After this change, ARCH=arm allmodconfig fails with:

  drivers/misc/mrvl_cn10k_dpi.c: In function 'dpi_reg_write':
  drivers/misc/mrvl_cn10k_dpi.c:190:9: error: implicit declaration of function 'writeq'; did you mean 'writeb'? [-Wimplicit-function-declaration]
    190 |         writeq(val, dpi->reg_base + offset);
        |         ^~~~~~
        |         writeb
  drivers/misc/mrvl_cn10k_dpi.c: In function 'dpi_reg_read':
  drivers/misc/mrvl_cn10k_dpi.c:195:16: error: implicit declaration of function 'readq'; did you mean 'readb'? [-Wimplicit-function-declaration]
    195 |         return readq(dpi->reg_base + offset);
        |                ^~~~~
        |                readb

Including one of the io-64-nonatomic headers would resolve this but I am
not sure which one would be appropriate (or perhaps the dependency
should be tightened to requiring 64BIT, as some other drivers have
done).

Cheers,
Nathan

  reply	other threads:[~2024-07-16 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 12:01 Vamsi Attunuru
2024-07-16 13:26 ` Nathan Chancellor [this message]
2024-07-16 13:51   ` Arnd Bergmann
2024-07-16 15:33     ` [EXTERNAL] " Vamsi Krishna Attunuru
2024-07-16 15:48       ` Arnd Bergmann
2024-07-17  0:28       ` Nathan Chancellor

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=20240716132603.GA3136577@thelio-3990X \
    --to=nathan@kernel.org \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vattunuru@marvell.com \
    /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

all inboxes | Powered by JetHome®