From: "Luís Cargnini" <lvcargnini@gmail.com>
To: Felipe Balbi <felipebalbi@users.sourceforge.net>
Cc: OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: problems with backlight
Date: Wed, 3 Oct 2007 13:44:08 -0300 [thread overview]
Message-ID: <ae36f8040710030944m5b67fb7dle9d23d5486f30941@mail.gmail.com> (raw)
In-Reply-To: <31e679430710021108n1428d7c4gfb799d7aa18f7449@mail.gmail.com>
I applied the patches only now and are compiling the kernel right now
On 10/2/07, Felipe Balbi <felipebalbi@users.sourceforge.net> wrote:
>
> Sorry,
>
> forgot to change to correct function...
>
> try this one
>
>
>
>
>
> On 10/2/07, Felipe Balbi <felipebalbi@users.sourceforge.net> wrote:
> > Hi Luis,
> >
> > On 10/2/07, Luís Cargnini <lvcargnini@gmail.com> wrote:
> > > Dear fellows,
> > > I had the following problems compiling for omap with omap backlight
> enabled,
> > > the following error:
> > > make
> > > CHK include/linux/version.h
> > > make[1]: `include/asm-arm/mach-types.h' is up to date.
> > > CHK include/linux/utsrelease.h
> > > CALL scripts/checksyscalls.sh
> > > <stdin>:1097:2: warning: #warning syscall fadvise64 not implemented
> > > <stdin>:1265:2: warning: #warning syscall migrate_pages not
> implemented
> > > <stdin>:1321:2: warning: #warning syscall pselect6 not implemented
> > > <stdin>:1325:2: warning: #warning syscall ppoll not implemented
> > > <stdin>:1365:2: warning: #warning syscall epoll_pwait not implemented
> > > <stdin>:1385:2: warning: #warning syscall fallocate not implemented
> > > CHK include/linux/compile.h
> > > CC [M] drivers/video/backlight/omap_bl.o
> > > drivers/video/backlight/omap_bl.c: In function 'omapbl_suspend':
> > > drivers/video/backlight/omap_bl.c:79: error: 'struct backlight_device'
> has
> > > no member named 'class_dev'
> > > drivers/video/backlight/omap_bl.c: In function 'omapbl_resume':
> > > drivers/video/backlight/omap_bl.c:88: error: 'struct backlight_device'
> has
> > > no member named 'class_dev'
> > > drivers/video/backlight/omap_bl.c: In function 'omapbl_set_power':
> > > drivers/video/backlight/omap_bl.c:100: error: 'struct
> backlight_device' has
> > > no member named 'class_dev'
> > > drivers/video/backlight/omap_bl.c: In function 'omapbl_update_status':
> > > drivers/video/backlight/omap_bl.c:110: error: 'struct
> backlight_device' has
> > > no member named 'class_dev'
> > > drivers/video/backlight/omap_bl.c: In function 'omapbl_get_intensity':
> > > drivers/video/backlight/omap_bl.c:130: error: 'struct
> backlight_device' has
> > > no member named 'class_dev'
> > > drivers/video/backlight/omap_bl.c: In function 'omapbl_remove':
> > > drivers/video/backlight/omap_bl.c:185: error: 'struct
> backlight_device' has
> > > no member named 'class_dev'
> > > make[3]: *** [drivers/video/backlight/omap_bl.o] Error 1
> > > make[2]: *** [drivers/video/backlight] Error 2
> > > make[1]: *** [drivers/video] Error 2
> > > make: *** [drivers] Error 2
> > >
> > > looking he source code:
> > > struct omap_backlight {
> > > int powermode;
> > > int current_intensity;
> > >
> > > struct device *dev;
> > > struct omap_backlight_config *pdata;
> > > };
> > >
> > >
> > > but :
> > > #ifdef CONFIG_PM
> > > static int omapbl_suspend(struct platform_device *pdev, pm_message_t
> state)
> > > {
> > > struct backlight_device *dev = platform_get_drvdata(pdev);
> > > struct omap_backlight *bl = class_get_devdata(&dev->class_dev);
> > >
> > > omapbl_blank(bl, FB_BLANK_POWERDOWN);
> > > return 0;
> > > }
> > >
> > > someone have figured this problem before ?
> > > can I make the fix ?
> > > There is no fix, no problem I'm just creating one ?
> >
> > Check if the attached fixes the issue...
> >
> > If it works, I'll send a proper formated patch
> >
> > >
> > > --
> > >
> ------------------------------------------------------------------------------
> > > Thanks && Regards
> > > Msc. Bsc. Luís Vitório Cargnini
> > > IEEE Member
> > > Electrical Engineer Faculty @ PUCRS
> > > Ipiranga Avenue, 6681 – Building 30
> > > P.O. Box: 90619-900 – Porto Alegre/RS
> > > Phone: +55 51 3320 3500 extension: 7696
> > >
> ---------------------------------------------------------------------------------
> > > _______________________________________________
> > > Linux-omap-open-source mailing list
> > > Linux-omap-open-source@linux.omap.com
> > > http://linux.omap.com/mailman/listinfo/linux-omap-open-source
> > >
> >
> >
> > --
> > Best Regards,
> >
> > Felipe Balbi
> > felipebalbi@users.sourceforge.net
> >
> >
>
>
> --
> Best Regards,
>
> Felipe Balbi
> felipebalbi@users.sourceforge.net
>
>
--
------------------------------------------------------------------------------
Thanks && Regards
Msc. Bsc. Luís Vitório Cargnini
IEEE Member
Electrical Engineer Faculty @ PUCRS
Ipiranga Avenue, 6681 – Building 30
P.O. Box: 90619-900 – Porto Alegre/RS
Phone: +55 51 3320 3500 extension: 7696
---------------------------------------------------------------------------------
next prev parent reply other threads:[~2007-10-03 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 17:45 problems with backlight Luís Cargnini
2007-10-02 18:03 ` Felipe Balbi
2007-10-02 18:08 ` Felipe Balbi
2007-10-03 16:44 ` Luís Cargnini [this message]
2007-10-03 16:54 ` Felipe Balbi
2007-10-03 17:17 ` Luís Cargnini
-- strict thread matches above, loose matches on Subject: below --
2007-10-02 17:57 Luís Cargnini
2007-10-02 18:16 ` David Brownell
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=ae36f8040710030944m5b67fb7dle9d23d5486f30941@mail.gmail.com \
--to=lvcargnini@gmail.com \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=felipebalbi@users.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox