From: "Arnd Bergmann" <arnd@arndb.de>
To: "Nathan Chancellor" <nathan@kernel.org>,
"Vamsi Attunuru" <vattunuru@marvell.com>
Cc: "Greg Kroah-Hartman" <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 15:51:08 +0200 [thread overview]
Message-ID: <83ac6b91-c7f1-4b18-a522-8188d6d1298b@app.fastmail.com> (raw)
In-Reply-To: <20240716132603.GA3136577@thelio-3990X>
On Tue, Jul 16, 2024, at 15:26, Nathan Chancellor wrote:
> On Thu, Jul 11, 2024 at 05:01:15AM -0700, Vamsi Attunuru wrote:
>>
>
> 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).
Right, a dependency on 64BIT makes sense here. The alternative is
to include linux/io-64-nonatomic-hi-lo.h or linux/io-64-nonatomic-lo-hi.h
in order to have a replacement readq/writeq implementation that
works on 32-bit architectures. However, doing this requires
understanding whether what the side-effects of accessing the
64-bit registers are and whether they require writing the upper
or lower half of the register last.
Arnd
next prev parent reply other threads:[~2024-07-16 13:51 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
2024-07-16 13:51 ` Arnd Bergmann [this message]
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=83ac6b91-c7f1-4b18-a522-8188d6d1298b@app.fastmail.com \
--to=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@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®