From: Jaya Kumar <jayakumar.lkml@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 10/11] [ARM] tegra: Add framebuffer driver
Date: Mon, 14 Jun 2010 23:59:54 +0000 [thread overview]
Message-ID: <AANLkTikqOrciEnESCC1yGm0UvcxdK942ddrZF4K49TVb@mail.gmail.com> (raw)
In-Reply-To: <1276549827-2688-11-git-send-email-konkers@android.com>
On Tue, Jun 15, 2010 at 5:10 AM, Erik Gilling <konkers@android.com> wrote:
> diff --git a/drivers/video/tegrafb.c b/drivers/video/tegrafb.c
> new file mode 100644
> index 0000000..47b2d42
> --- /dev/null
> +++ b/drivers/video/tegrafb.c
> +/* palette attary used by the fbcon */
> +u32 pseudo_palette[16];
attary
> +
> +irqreturn_t tegra_fb_irq(int irq, void *ptr)
> +{
> + struct fb_info *info = ptr;
> + struct tegra_fb_info *tegra_fb = info->par;
> +
> + u32 reg = tegra_fb_readl(tegra_fb, DC_CMD_INT_STATUS);
> + tegra_fb_writel(tegra_fb, reg, DC_CMD_INT_STATUS);
> +
> + tegra_fb->wait_condition = 1;
> + wake_up(&tegra_fb->event_wq);
> + return IRQ_HANDLED;
> +}
> +
> +static int tegra_fb_wait_for_event(struct tegra_fb_info *tegra_fb,
> + unsigned long timeout, u32 irq_mask)
> +{
> + u32 reg;
> +
> + tegra_fb->wait_condition = 0;
> +
> + reg = tegra_fb_readl(tegra_fb, DC_CMD_INT_MASK);
> + reg |= irq_mask;
> + tegra_fb_writel(tegra_fb, reg, DC_CMD_INT_MASK);
> +
> + /* Clear any pending interrupt */
> + tegra_fb_writel(tegra_fb, irq_mask, DC_CMD_INT_STATUS);
> +
> + tegra_fb_writel(tegra_fb, irq_mask, DC_CMD_INT_ENABLE);
> +
> + /* Wait for the irq to fire */
> + wait_event_interruptible_timeout(tegra_fb->event_wq,
> + tegra_fb->wait_condition, timeout);
> +
> + tegra_fb_writel(tegra_fb, 0, DC_CMD_INT_ENABLE);
> +
> + if (!tegra_fb->wait_condition) {
> + pr_warning("%s: wait for vsync timed out\n", __func__);
> + return -ETIMEDOUT;
> + }
> + return 0;
> +}
Apologies for the incremental review. The wait_condition code above
looks odd to me. Typically, we just test the return value of
wait_event_interruptible_timeout to see whether it timed out (returns
0 if so). But I guess the above approach works as well.
> + if (tegra_fb_wait_for_event(tegra_fb, HZ/10, DC_INT_FRAME_END))
I still didn't follow how tegra_fb_activate is using the -ETIMEDOUT
return value from the wait, it seems like it is just ignored. You are
also doing stuff like HZ/10 and you might prefer to use
msecs_to_jiffies.
Thanks,
jaya
next prev parent reply other threads:[~2010-06-14 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1268721431-24434-1-git-send-email-konkers@google.com>
[not found] ` <1271198563-10424-1-git-send-email-konkers@android.com>
[not found] ` <1271198563-10424-2-git-send-email-konkers@android.com>
[not found] ` <1271198563-10424-3-git-send-email-konkers@android.com>
[not found] ` <1271198563-10424-4-git-send-email-konkers@android.com>
[not found] ` <1271198563-10424-5-git-send-email-konkers@android.com>
[not found] ` <1271198563-10424-6-git-send-email-konkers@android.com>
[not found] ` <1271198563-10424-7-git-send-email-konkers@android.com>
[not found] ` <1271198563-10424-8-git-send-email-konkers@android.com>
[not found] ` <1271198563-10424-9-git-send-email-konkers@android.com>
2010-04-13 23:26 ` [PATCH v2 08/10] [ARM] tegra: Add framebuffer driver Jaya Kumar
[not found] ` <1276549827-2688-1-git-send-email-konkers@android.com>
[not found] ` <1276549827-2688-2-git-send-email-konkers@android.com>
[not found] ` <1276549827-2688-3-git-send-email-konkers@android.com>
[not found] ` <1276549827-2688-4-git-send-email-konkers@android.com>
[not found] ` <1276549827-2688-5-git-send-email-konkers@android.com>
[not found] ` <1276549827-2688-6-git-send-email-konkers@android.com>
[not found] ` <1276549827-2688-7-git-send-email-konkers@android.com>
[not found] ` <1276549827-2688-8-git-send-email-konkers@android.com>
[not found] ` <1276549827-2688-9-git-send-email-konkers@android.com>
[not found] ` <1276549827-2688-10-git-send-email-konkers@android.com>
2010-06-14 21:10 ` [PATCH v3 10/11] " Erik Gilling
2010-06-14 23:59 ` Jaya Kumar [this message]
2010-06-15 0:16 ` Jaya Kumar
2010-06-15 0:43 ` Colin Cross
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=AANLkTikqOrciEnESCC1yGm0UvcxdK942ddrZF4K49TVb@mail.gmail.com \
--to=jayakumar.lkml@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).