[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yictcf0BCvveVT+V@smile.fi.intel.com>
Date: Tue, 8 Mar 2022 12:18:25 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
dri-devel@...ts.freedesktop.org, linux-fbdev@...r.kernel.org,
linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Cc: Helge Deller <deller@....de>
Subject: Re: [PATCH v1 1/1] staging: fbtft: Consider type of init sequence
values in fbtft_init_display()
+Cc: Helge
Maybe you can pick this up?
On Fri, Mar 04, 2022 at 09:34:14PM +0200, Andy Shevchenko wrote:
> In the fbtft_init_display() the init sequence is printed for
> the debug purposes. Unfortunately the current code doesn't take
> into account that values in the buffer are of the s16 type.
>
> Consider that and replace the printing code with fbtft_par_dbg_hex()
> call.
>
> Fixes: b888897014a9 ("staging/fbtft: Remove all strcpy() uses")
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
> ---
> drivers/staging/fbtft/fbtft-core.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/fbtft/fbtft-core.c b/drivers/staging/fbtft/fbtft-core.c
> index 4a35347b3020..b28a059ad3b4 100644
> --- a/drivers/staging/fbtft/fbtft-core.c
> +++ b/drivers/staging/fbtft/fbtft-core.c
> @@ -1035,10 +1035,9 @@ int fbtft_init_display(struct fbtft_par *par)
> for (j = 0; par->init_sequence[i + 1 + j] >= 0; j++)
> ;
>
> - fbtft_par_dbg(DEBUG_INIT_DISPLAY, par,
> - "init: write(0x%02X) %*ph\n",
> - par->init_sequence[i], j,
> - &par->init_sequence[i + 1]);
> + fbtft_par_dbg_hex(DEBUG_INIT_DISPLAY, par, par->info->device,
> + s16, &par->init_sequence[i + 1], j,
> + "init: write(0x%02X)", par->init_sequence[i]);
>
> /* Write */
> j = 0;
> --
> 2.34.1
>
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists