From: Sam Ravnborg <sam@ravnborg.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: linux-fbdev@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Enrico Weigelt <info@metux.net>
Subject: Re: [PATCH] fbdev: mx3fb: avoid warning about psABI change
Date: Wed, 08 Apr 2020 18:02:16 +0000 [thread overview]
Message-ID: <20200408180216.GC24828@ravnborg.org> (raw)
In-Reply-To: <87pnchhp2s.fsf@intel.com>
Hi Jani & Laurent.
On Wed, Apr 08, 2020 at 08:20:11PM +0300, Jani Nikula wrote:
> On Wed, 08 Apr 2020, Arnd Bergmann <arnd@arndb.de> wrote:
> > The arm64 gcc-9 release warns about a change in the calling
> > conventions:
> >
> > drivers/video/fbdev/mx3fb.c: In function 'sdc_init_panel':
> > drivers/video/fbdev/mx3fb.c:506:12: note: parameter passing for argument of type 'struct ipu_di_signal_cfg' changed in GCC 9.1
> > 506 | static int sdc_init_panel(struct mx3fb_data *mx3fb, enum ipu_panel panel,
> > | ^~~~~~~~~~~~~~
> > drivers/video/fbdev/mx3fb.c: In function '__set_par':
> > drivers/video/fbdev/mx3fb.c:848:7: note: parameter passing for argument of type 'struct ipu_di_signal_cfg' changed in GCC 9.1
> >
> > Change the file to just pass the struct by reference, which is
> > unambiguous and avoids the warning.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > ---
> > drivers/video/fbdev/mx3fb.c | 20 ++++++++++----------
> > 1 file changed, 10 insertions(+), 10 deletions(-)
> >
> > diff --git a/drivers/video/fbdev/mx3fb.c b/drivers/video/fbdev/mx3fb.c
> > index 4af28e4421e5..e13fea3a292f 100644
> > --- a/drivers/video/fbdev/mx3fb.c
> > +++ b/drivers/video/fbdev/mx3fb.c
> > @@ -509,7 +509,7 @@ static int sdc_init_panel(struct mx3fb_data *mx3fb, enum ipu_panel panel,
> > uint16_t h_start_width, uint16_t h_sync_width,
> > uint16_t h_end_width, uint16_t v_start_width,
> > uint16_t v_sync_width, uint16_t v_end_width,
> > - struct ipu_di_signal_cfg sig)
> > + struct ipu_di_signal_cfg *sig)
>
> I have no idea why get_maintainer.pl (I presume) is Cc'ing me... but
> since it is, I'll note that the pointer could be const, while the patch
> is
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
I was too quick to apply this - sorry.
I will follow-up with a const fix.
Sam
>
> either way.
>
> > {
> > unsigned long lock_flags;
> > uint32_t reg;
> > @@ -591,17 +591,17 @@ static int sdc_init_panel(struct mx3fb_data *mx3fb, enum ipu_panel panel,
> >
> > /* DI settings */
> > old_conf = mx3fb_read_reg(mx3fb, DI_DISP_IF_CONF) & 0x78FFFFFF;
> > - old_conf |= sig.datamask_en << DI_D3_DATAMSK_SHIFT |
> > - sig.clksel_en << DI_D3_CLK_SEL_SHIFT |
> > - sig.clkidle_en << DI_D3_CLK_IDLE_SHIFT;
> > + old_conf |= sig->datamask_en << DI_D3_DATAMSK_SHIFT |
> > + sig->clksel_en << DI_D3_CLK_SEL_SHIFT |
> > + sig->clkidle_en << DI_D3_CLK_IDLE_SHIFT;
> > mx3fb_write_reg(mx3fb, old_conf, DI_DISP_IF_CONF);
> >
> > old_conf = mx3fb_read_reg(mx3fb, DI_DISP_SIG_POL) & 0xE0FFFFFF;
> > - old_conf |= sig.data_pol << DI_D3_DATA_POL_SHIFT |
> > - sig.clk_pol << DI_D3_CLK_POL_SHIFT |
> > - sig.enable_pol << DI_D3_DRDY_SHARP_POL_SHIFT |
> > - sig.Hsync_pol << DI_D3_HSYNC_POL_SHIFT |
> > - sig.Vsync_pol << DI_D3_VSYNC_POL_SHIFT;
> > + old_conf |= sig->data_pol << DI_D3_DATA_POL_SHIFT |
> > + sig->clk_pol << DI_D3_CLK_POL_SHIFT |
> > + sig->enable_pol << DI_D3_DRDY_SHARP_POL_SHIFT |
> > + sig->Hsync_pol << DI_D3_HSYNC_POL_SHIFT |
> > + sig->Vsync_pol << DI_D3_VSYNC_POL_SHIFT;
> > mx3fb_write_reg(mx3fb, old_conf, DI_DISP_SIG_POL);
> >
> > map = &di_mappings[mx3fb->disp_data_fmt];
> > @@ -855,7 +855,7 @@ static int __set_par(struct fb_info *fbi, bool lock)
> > fbi->var.upper_margin,
> > fbi->var.vsync_len,
> > fbi->var.lower_margin +
> > - fbi->var.vsync_len, sig_cfg) != 0) {
> > + fbi->var.vsync_len, &sig_cfg) != 0) {
> > dev_err(fbi->device,
> > "mx3fb: Error initializing panel.\n");
> > return -EINVAL;
>
> --
> Jani Nikula, Intel Open Source Graphics Center
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-04-08 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 16:25 [PATCH] fbdev: mx3fb: avoid warning about psABI change Arnd Bergmann
2020-04-08 17:16 ` Laurent Pinchart
2020-04-08 17:20 ` Jani Nikula
2020-04-08 18:02 ` Sam Ravnborg [this message]
2020-04-08 18:29 ` [PATCH] fbdev: mx3fb: const pointer to ipu_di_signal_cfg Sam Ravnborg
2020-04-08 20:01 ` Laurent Pinchart
2020-04-12 20:34 ` Sam Ravnborg
2020-04-08 17:22 ` [PATCH] fbdev: mx3fb: avoid warning about psABI change Sam Ravnborg
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=20200408180216.GC24828@ravnborg.org \
--to=sam@ravnborg.org \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=info@metux.net \
--cc=jani.nikula@intel.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).