From: Nicolas Boichat <nicolas@boichat.ch>
To: Andrew Morton <akpm@osdl.org>
Cc: adaplas@pol.net, greg@kroah.com, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Fw: Rivafb I2C problem, new patch
Date: Wed, 14 Jul 2004 01:45:54 +0200 [thread overview]
Message-ID: <1089762354.6185.53.camel@tom> (raw)
In-Reply-To: <20040713150235.056f6a5c.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 342 bytes --]
Hello,
This should be the last patch, the changelog is at the beginning of the
file.
Best regards,
Nicolas
On Wed, 2004-07-14 at 00:02, Andrew Morton wrote:
> Nicolas Boichat <nicolas@boichat.ch> wrote:
> >
> > Good idea... it didn't compile. Fixed patch attached.
>
> Please send a complete new patch, with a changelog.
>
> Thanks.
>
[-- Attachment #2: rivafb-i2c-bus-fix.patch --]
[-- Type: text/x-patch, Size: 1795 bytes --]
From: Nicolas Boichat <nicolas@boichat.ch>
The I2C busses opened by rivafb were deleted immediately after
reading the EDID, but they should be kept open, so user-space
applications can use them.
They are now deleted when the driver is unloaded.
---
linux/drivers/video/riva/fbdev.c | 13 +++++++++++--
1 files changed, 11 insertions(+), 2 deletions(-)
diff -puN linux/drivers/video/riva/fbdev.c.old linux/drivers/video/riva/fbdev.c
--- linux/drivers/video/riva/fbdev.c.old 2004-07-13 02:05:47.000000000 +0200
+++ linux/drivers/video/riva/fbdev.c 2004-07-13 23:34:27.023199272 +0200
@@ -1773,7 +1773,6 @@ static void riva_get_EDID(struct fb_info
struct riva_par *par = (struct riva_par *) info->par;
int i;
- riva_create_i2c_busses(par);
for (i = par->bus; i >= 1; i--) {
riva_probe_i2c_connector(par, i, &par->EDID);
if (par->EDID) {
@@ -1781,7 +1780,6 @@ static void riva_get_EDID(struct fb_info
break;
}
}
- riva_delete_i2c_busses(par);
#endif
#endif
}
@@ -1933,6 +1931,10 @@ static int __devinit rivafb_probe(struct
}
#endif /* CONFIG_MTRR */
+#ifdef CONFIG_FB_RIVA_I2C
+ riva_create_i2c_busses((struct riva_par *) info->par);
+#endif
+
info->fbops = &riva_fb_ops;
info->fix = rivafb_fix;
riva_get_EDID(info, pd);
@@ -1961,6 +1963,9 @@ static int __devinit rivafb_probe(struct
return 0;
err_out_iounmap_fb:
+#ifdef CONFIG_FB_RIVA_I2C
+ riva_delete_i2c_busses((struct riva_par *) info->par);
+#endif
iounmap(info->screen_base);
err_out_free_base1:
if (default_par->riva.Architecture == NV_ARCH_03)
@@ -1989,6 +1994,10 @@ static void __exit rivafb_remove(struct
if (!info)
return;
+#ifdef CONFIG_FB_RIVA_I2C
+ riva_delete_i2c_busses(par);
+#endif
+
unregister_framebuffer(info);
#ifdef CONFIG_MTRR
if (par->mtrr.vram_valid)
prev parent reply other threads:[~2004-07-13 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 23:39 Fw: Rivafb I2C problem, new patch Andrew Morton
2004-07-12 23:43 ` Greg KH
2004-07-13 1:58 ` Antonino A. Daplas
2004-07-13 9:53 ` Nicolas Boichat
2004-07-13 20:52 ` Antonino A. Daplas
2004-07-13 21:46 ` Nicolas Boichat
2004-07-13 22:02 ` Andrew Morton
2004-07-13 23:45 ` Nicolas Boichat [this message]
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=1089762354.6185.53.camel@tom \
--to=nicolas@boichat.ch \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.