public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sergei Antonov <saproj@gmail.com>
To: u-boot@lists.denx.de
Cc: Sergei Antonov <saproj@gmail.com>, Mario Six <mario.six@gdsys.cc>
Subject: [PATCH] axi: fix a warning
Date: Mon, 19 Jun 2023 23:35:41 +0300	[thread overview]
Message-ID: <20230619203541.1921288-1-saproj@gmail.com> (raw)

Fix an enum/integer mismatch encountered in 'sandbox_defconfig' build.

.../u-boot/drivers/axi/axi-emul-uclass.c:16:5: warning: conflicting types for ‘axi_sandbox_get_emul’ due to enum/integer mismatch; have ‘int(struct udevice *, ulong,  enum axi_size_t,  struct udevice **)’ {aka ‘int(struct udevice *, long unsigned int,  enum axi_size_t,  struct udevice **)’} [-Wenum-int-mismatch]
   16 | int axi_sandbox_get_emul(struct udevice *bus, ulong address,
      |     ^~~~~~~~~~~~~~~~~~~~
In file included from .../u-boot/drivers/axi/axi-emul-uclass.c:14:
.../u-boot/arch/sandbox/include/asm/axi.h:48:5: note: previous declaration of ‘axi_sandbox_get_emul’ with type ‘int(struct udevice *, ulong,  uint,  struct udevice **)’ {aka ‘int(struct udevice *, long unsigned int,  unsigned int,  struct udevice **)’}
   48 | int axi_sandbox_get_emul(struct udevice *bus, ulong address, uint length,
      |     ^~~~~~~~~~~~~~~~~~~~

Make function declaration match function definition.

Cc: Mario Six <mario.six@gdsys.cc>
Signed-off-by: Sergei Antonov <saproj@gmail.com>
---
 arch/sandbox/include/asm/axi.h | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/arch/sandbox/include/asm/axi.h b/arch/sandbox/include/asm/axi.h
index d483f7b65a02..a93975c6534b 100644
--- a/arch/sandbox/include/asm/axi.h
+++ b/arch/sandbox/include/asm/axi.h
@@ -7,6 +7,8 @@
 #ifndef __asm_axi_h
 #define __asm_axi_h
 
+#include <axi.h>
+
 #define axi_emul_get_ops(dev)	((struct axi_emul_ops *)(dev)->driver->ops)
 
 /**
@@ -14,10 +16,10 @@
  * @bus:     The AXI bus from which to retrieve a emulation device
  * @address: The address of a transfer that should be handled by a emulation
  *	     device
- * @length:  The data width of a transfer that should be handled by a emulation
+ * @size:    The data width of a transfer that should be handled by a emulation
  *	     device
  * @emulp:   Pointer to a buffer receiving the emulation device that handles
- *	     the transfer specified by the address and length parameters
+ *	     the transfer specified by the address and size parameters
  *
  * To test the AXI uclass, we implement a simple AXI emulation device, which is
  * a virtual device on a AXI bus that exposes a simple storage interface: When
@@ -45,7 +47,7 @@
  * Return: 0 of OK, -ENODEV if no device capable of handling the specified
  *	   transfer exists or the device could not be retrieved
  */
-int axi_sandbox_get_emul(struct udevice *bus, ulong address, uint length,
+int axi_sandbox_get_emul(struct udevice *bus, ulong address, enum axi_size_t size,
 			 struct udevice **emulp);
 /**
  * axi_get_store() - Get address of internal storage of a emulated AXI device
-- 
2.37.2


             reply	other threads:[~2023-06-19 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 20:35 Sergei Antonov [this message]
2023-06-20 10:04 ` [PATCH] axi: fix a warning Simon Glass

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=20230619203541.1921288-1-saproj@gmail.com \
    --to=saproj@gmail.com \
    --cc=mario.six@gdsys.cc \
    --cc=u-boot@lists.denx.de \
    /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