public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, "Stefan Roese" <sr@denx.de>,
	"Marek Behún" <marek.behun@nic.cz>,
	"Konstantin Porotchkin" <kostap@marvell.com>
Subject: Re: [RFC 1/7] ARM: mvebu: a38x: Correct mismatched bound warnings
Date: Wed, 14 Jul 2021 22:52:26 +0200	[thread overview]
Message-ID: <20210714205226.3vdvmrmh6554x2ih@pali> (raw)
In-Reply-To: <20210503204859.18756-2-trini@konsulko.com>

On Monday 03 May 2021 16:48:53 Tom Rini wrote:
> With gcc-11 we see:
> drivers/ddr/marvell/a38x/ddr3_debug.c:672:47: error: argument 2 of type 'u32[5]' {aka 'unsigned int[5]'} with mismatched bound [-Werror=array-parameter=]
>   672 | int ddr3_tip_read_adll_value(u32 dev_num, u32 pup_values[MAX_INTERFACE_NUM * MAX_BUS_NUM],
>       |                                           ~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> In file included from drivers/ddr/marvell/a38x/ddr3_training_ip_engine.h:10,
>                  from drivers/ddr/marvell/a38x/ddr3_init.h:17,
>                  from drivers/ddr/marvell/a38x/ddr3_debug.c:6:
> drivers/ddr/marvell/a38x/ddr3_training_ip_flow.h:116:47: note: previously declared as 'u32[]' {aka 'unsigned int[]'}
> 
> And similar warnings.  Correct these by updating the prototype.  Remove
> the prototype for ddr3_tip_read_pup_value as it is unused.
> 
> Signed-off-by: Tom Rini <trini@konsulko.com>
> ---
>  drivers/ddr/marvell/a38x/ddr3_training_ip_flow.h | 10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/ddr/marvell/a38x/ddr3_training_ip_flow.h b/drivers/ddr/marvell/a38x/ddr3_training_ip_flow.h
> index ab152cb455e9..55832a55405b 100644
> --- a/drivers/ddr/marvell/a38x/ddr3_training_ip_flow.h
> +++ b/drivers/ddr/marvell/a38x/ddr3_training_ip_flow.h
> @@ -8,6 +8,7 @@
>  
>  #include "ddr3_training_ip.h"
>  #include "ddr3_training_ip_db.h"
> +#include "mv_ddr_plat.h"
>  
>  #define KILLER_PATTERN_LENGTH		32
>  #define EXT_ACCESS_BURST_LENGTH		8
> @@ -112,9 +113,12 @@ int ddr3_tip_configure_odpg(u32 dev_num, enum hws_access_type access_type,
>  int ddr3_tip_write_mrs_cmd(u32 dev_num, u32 *cs_mask_arr, enum mr_number mr_num, u32 data, u32 mask);
>  int ddr3_tip_write_cs_result(u32 dev_num, u32 offset);
>  int ddr3_tip_reset_fifo_ptr(u32 dev_num);
> -int ddr3_tip_read_pup_value(u32 dev_num, u32 pup_values[], int reg_addr, u32 mask);
> -int ddr3_tip_read_adll_value(u32 dev_num, u32 pup_values[], u32 reg_addr, u32 mask);
> -int ddr3_tip_write_adll_value(u32 dev_num, u32 pup_values[], u32 reg_addr);
> +int ddr3_tip_read_adll_value(u32 dev_num,
> +			     u32 pup_values[MAX_INTERFACE_NUM * MAX_BUS_NUM],
> +			     u32 reg_addr, u32 mask);
> +int ddr3_tip_write_adll_value(u32 dev_num,
> +			      u32 pup_values[MAX_INTERFACE_NUM * MAX_BUS_NUM],
> +			      u32 reg_addr);
>  int ddr3_tip_tune_training_params(u32 dev_num, struct tune_train_params *params);
>  
>  #endif /* _DDR3_TRAINING_IP_FLOW_H_ */

CC Stefan, Marek, Konstantin

Could you please send this patch to upstream?
https://github.com/MarvellEmbeddedProcessors/mv-ddr-marvell

Any change done in drivers/ddr/marvell/a38x cause issue in
future code synchronization with upstream repository.

  parent reply	other threads:[~2021-07-14 20:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 20:48 [RFC 0/7] Update CI to using GCC 11.0 / LLVM-11 Tom Rini
2021-05-03 20:48 ` [RFC 1/7] ARM: mvebu: a38x: Correct mismatched bound warnings Tom Rini
2021-07-07 17:33   ` Tom Rini
2021-07-14 20:52   ` Pali Rohár [this message]
2021-07-15  7:59     ` Stefan Roese
2021-07-15 13:07       ` [EXT] " Kostya Porotchkin
2021-05-03 20:48 ` [RFC 2/7] freescale: Drop unnecessary cpld_data_t non-typedef Tom Rini
2021-07-07 17:34   ` Tom Rini
2021-05-03 20:48 ` [RFC 3/7] eb_cpu5282: Declare diplay_width / display_height as externs Tom Rini
2021-07-07 17:34   ` Tom Rini
2021-05-03 20:48 ` [RFC 4/7] pinctrl: mscc: Fix multiple definition error Tom Rini
2021-05-04  7:51   ` Horatiu Vultur
2021-05-04 18:57   ` Daniel Schwierzeck
2021-07-07 17:34   ` Tom Rini
2021-05-03 20:48 ` [RFC 5/7] Makefile: Disable gcc-10.0 warnings Tom Rini
2021-07-07 17:34   ` Tom Rini
2021-05-03 20:48 ` [RFC 6/7] bootstage: Eliminate when not enabled Tom Rini
2021-07-07 17:34   ` Tom Rini
2021-05-03 20:48 ` [RFC 7/7] TEST: Move to gcc-11.0 prerelease and LLVM-11 Tom Rini
2021-06-16 19:58   ` [RFCv2] " Tom Rini
2021-06-16 20:00   ` [RFCv3] Azure/GitLab: Move to gcc-11.1.0 " Tom Rini
2021-06-17  8:27     ` Bin Meng
2021-06-17 12:31       ` Tom Rini
2021-06-17 14:09         ` Bin Meng
2021-06-17 14:14           ` Tom Rini
2021-06-17 14:24             ` Bin Meng
2021-06-17 14:45               ` Tom Rini
2021-06-17 14:51                 ` Bin Meng

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=20210714205226.3vdvmrmh6554x2ih@pali \
    --to=pali@kernel.org \
    --cc=kostap@marvell.com \
    --cc=marek.behun@nic.cz \
    --cc=sr@denx.de \
    --cc=trini@konsulko.com \
    --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