linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [PATCH v1] fbdev: sm712fb: fix an issue about iounmap for a wrong address
@ 2020-04-23 12:14 Markus Elfring
  2020-04-23 14:52 ` Dejin Zheng
  0 siblings, 1 reply; 2+ messages in thread
From: Markus Elfring @ 2020-04-23 12:14 UTC (permalink / raw)
  To: Dejin Zheng, dri-devel, linux-fbdev, Bartlomiej Zolnierkiewicz,
	Sudip Mukherjee, Teddy Wang
  Cc: linux-kernel, kernel-janitors, Greg Kroah-Hartman, Andy Shevchenko

> the sfb->fb->screen_base is not save the value get by iounmap() when
> the chip id is 0x720.

I suggest to improve this change description.
How did you determine relevant differences for the mentioned chip model?


> so iounmap() for address sfb->fb->screen_base is not right.

Will another imperative wording become helpful here?


…
> +++ b/drivers/video/fbdev/sm712fb.c
> @@ -1429,6 +1429,8 @@  static int smtc_map_smem(struct smtcfb_info *sfb,
>  static void smtc_unmap_smem(struct smtcfb_info *sfb)
>  {
>  	if (sfb && sfb->fb->screen_base) {
> +		if (sfb->chip_id == 0x720)
> +			sfb->fb->screen_base -= 0x00200000;
>  		iounmap(sfb->fb->screen_base);

How do you think about to use descriptive identifiers for
the shown constants?

Would you like to clarify any related software analysis approaches?

Regards,
Markus

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH v1] fbdev: sm712fb: fix an issue about iounmap for a wrong address
  2020-04-23 12:14 [PATCH v1] fbdev: sm712fb: fix an issue about iounmap for a wrong address Markus Elfring
@ 2020-04-23 14:52 ` Dejin Zheng
  0 siblings, 0 replies; 2+ messages in thread
From: Dejin Zheng @ 2020-04-23 14:52 UTC (permalink / raw)
  To: Markus Elfring
  Cc: dri-devel, linux-fbdev, Bartlomiej Zolnierkiewicz,
	Sudip Mukherjee, Teddy Wang, linux-kernel, kernel-janitors,
	Greg Kroah-Hartman, Andy Shevchenko

On Thu, Apr 23, 2020 at 02:14:48PM +0200, Markus Elfring wrote:
> > the sfb->fb->screen_base is not save the value get by iounmap() when
> > the chip id is 0x720.
> 
> I suggest to improve this change description.
> How did you determine relevant differences for the mentioned chip model?
>
Read and check its codes。

smtcfb_pci_probe() --> smtc_map_smem()

smtcfb_pci_probe()
switch (sfb->chip_id) {
        case 0x710:
        case 0x712:
		sfb->lfb = ioremap(mmio_base, mmio_addr);
	case 0x720:
		sfb->dp_regs = ioremap(mmio_base, 0x00200000 + smem_size);
                sfb->lfb = sfb->dp_regs + 0x00200000;
	}
smtc_map_smem()
	sfb->fb->screen_base = sfb->lfb;


smtcfb_pci_remove() --> smtc_unmap_smem()

smtc_unmap_smem()
	iounmap(sfb->fb->screen_base);

> 
> > so iounmap() for address sfb->fb->screen_base is not right.
> 
> Will another imperative wording become helpful here?
> 
yes, this is why need to change this code.

> 
> …
> > +++ b/drivers/video/fbdev/sm712fb.c
> > @@ -1429,6 +1429,8 @@  static int smtc_map_smem(struct smtcfb_info *sfb,
> >  static void smtc_unmap_smem(struct smtcfb_info *sfb)
> >  {
> >  	if (sfb && sfb->fb->screen_base) {
> > +		if (sfb->chip_id == 0x720)
> > +			sfb->fb->screen_base -= 0x00200000;
> >  		iounmap(sfb->fb->screen_base);
> 
> How do you think about to use descriptive identifiers for
> the shown constants?
>
These two constants are originally in the driver, I don't know enough
about its meaning, There are a lot of constants in this driver. If I
replace it with the macro, I worry that the name of the macro may not
be accurate.

> Would you like to clarify any related software analysis approaches?
>
just read coedes and check it.

> Regards,
> Markus

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-04-23 14:52 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-23 12:14 [PATCH v1] fbdev: sm712fb: fix an issue about iounmap for a wrong address Markus Elfring
2020-04-23 14:52 ` Dejin Zheng

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).