From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jaya Kumar <jayakumar.lkml@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net, ymiao3@marvell.com,
eric miao <eric.y.miao@gmail.com>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [RFC 2.6.26-rc9 1/5] pxafb: add shared framebuffer interface
Date: Wed, 16 Jul 2008 10:38:55 +0100 [thread overview]
Message-ID: <20080716093855.GC23468@flint.arm.linux.org.uk> (raw)
In-Reply-To: <45a44e480807160159j62b9f989l2ae99bd94d24a95f@mail.gmail.com>
On Wed, Jul 16, 2008 at 01:59:42AM -0700, Jaya Kumar wrote:
> On Wed, Jul 16, 2008 at 12:00 AM, eric miao <eric.y.miao@gmail.com> wrote:
> > On Sun, Jul 13, 2008 at 9:26 PM, Jaya Kumar <jayakumar.lkml@gmail.com> wrote:
> >> These changes are to make it possible for a secondary driver to share the
> >> pxafb framebuffer. The changes include:
> >> - adding clkdev entry in pxafb_mach_info so that a driver can pass in the
> >> correct struct device owner for the LCDCLK.
> >
> > Is it possible that LCDCLK being requested by device other than
> > pxa_device_fb?? Could you give an example and we may work out
> > a better solution.
>
> You're right. I think LCDCLK is only ever requested by pxa_device_fb.
>
> I see now that instead of doing:
> - fbi->clk = clk_get(dev, "LCDCLK");
> + fbi->clk = clk_get(inf->clkdev, "LCDCLK");
>
> a better solution would be to directly use pxa_device_fb:
> - fbi->clk = clk_get(dev, "LCDCLK");
> + fbi->clk = clk_get(pxa_device_fb.dev, "LCDCLK");
>
> and then I can avoid doing the clkdev ugliness.
PXA devices (intentionally) aren't exported. Nor are they going to be,
so the above will fail if built as a module.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
next prev parent reply other threads:[~2008-07-16 9:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 13:26 [RFC 2.6.26-rc9 0/5] am200epd, pxafb, metronomefb changes v5 Jaya Kumar
2008-07-13 13:26 ` [RFC 2.6.26-rc9 1/5] pxafb: add shared framebuffer interface Jaya Kumar
2008-07-16 7:00 ` eric miao
2008-07-16 8:59 ` Jaya Kumar
2008-07-16 9:08 ` eric miao
2008-07-16 11:10 ` Jaya Kumar
2008-07-16 9:38 ` Russell King - ARM Linux [this message]
2008-07-16 11:18 ` Jaya Kumar
2008-07-20 2:41 ` Jaya Kumar
2008-07-21 2:10 ` eric miao
2008-07-21 3:38 ` Jaya Kumar
2008-07-13 13:26 ` [RFC 2.6.26-rc9 2/5] gumstix: conversion to MFP support and add bluetooth support Jaya Kumar
2008-07-16 6:55 ` eric miao
2008-07-16 7:09 ` Jaya Kumar
2008-07-16 7:13 ` eric miao
2008-07-13 13:26 ` [RFC 2.6.26-rc9 3/5] am200epd: convert to shared fb and use gpio api Jaya Kumar
2008-07-13 13:26 ` [RFC 2.6.26-rc9 4/5] metronomefb: convert printk to dev_dbg/err messages Jaya Kumar
2008-07-16 7:09 ` eric miao
2008-07-13 13:26 ` [RFC 2.6.26-rc9 5/5] metronomefb: changes to use separate framebuffer Jaya Kumar
-- strict thread matches above, loose matches on Subject: below --
2008-07-20 6:10 [RFC 2.6.26-rc9 0/5] am200epd, pxafb, metronomefb changes v6 Jaya Kumar
2008-07-20 6:10 ` [RFC 2.6.26-rc9 1/5] pxafb: add shared framebuffer interface Jaya Kumar
2008-07-21 11:11 ` Russell King - ARM Linux
2008-07-21 12:32 ` Jaya Kumar
2008-07-26 3:30 ` Jaya Kumar
2008-07-30 2:41 ` Eric Miao
2008-07-30 3:10 ` Jaya Kumar
2008-07-26 4:32 [RFC 2.6.26-rc9 0/5] am200epd, pxafb, metronomefb changes v7 Jaya Kumar
2008-07-26 4:32 ` [RFC 2.6.26-rc9 1/5] pxafb: add shared framebuffer interface Jaya Kumar
2008-07-29 15:28 ` Krzysztof Helt
2008-07-29 16:39 ` Jaya Kumar
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=20080716093855.GC23468@flint.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=eric.y.miao@gmail.com \
--cc=jayakumar.lkml@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=ymiao3@marvell.com \
/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).