linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jayakumar.lkml@gmail.com (Jaya Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 08/10] [ARM] tegra: Add framebuffer driver
Date: Wed, 14 Apr 2010 07:26:00 +0800	[thread overview]
Message-ID: <q2l45a44e481004131626j7f5afbfcsfcf861aa70dab651@mail.gmail.com> (raw)
In-Reply-To: <1271198563-10424-9-git-send-email-konkers@android.com>

Please CC fbdev as well. Thanks.

On Wed, Apr 14, 2010 at 6:42 AM,  <konkers@android.com> wrote:
> +/* palette attary used by the fbcon */
> +u32 pseudo_palette[16];

attary?

> +static int tegra_plat_probe(struct platform_device *pdev)
> +{

> + ? ? ? info = framebuffer_alloc(sizeof(struct tegra_fb_info), &pdev->dev);
> + ? ? ? if (!info) {
> + ? ? ? ? ? ? ? ret = -ENOMEM;
> + ? ? ? ? ? ? ? goto err;
> + ? ? ? }
> +
> + ? ? ? irq = platform_get_irq(pdev, 0);
> + ? ? ? if (irq <= 0) {
> + ? ? ? ? ? ? ? pr_debug("%s: no irq\n", pdev->name);
> + ? ? ? ? ? ? ? ret = -ENOENT;
> + ? ? ? ? ? ? ? goto err_free;
> + ? ? ? }

I see the irq get and the request_irq.

> +
> + ? ? ? if (request_irq(irq, tegra_fb_irq, IRQF_DISABLED,
> + ? ? ? ? ? ? ? ? ? ? ? dev_name(&pdev->dev), info)) {
> + ? ? ? ? ? ? ? pr_debug("%s: request_irq %d failed\n",
> + ? ? ? ? ? ? ? ? ? ? ? pdev->name, irq);
> + ? ? ? ? ? ? ? ret = -EBUSY;
> + ? ? ? ? ? ? ? goto err_clk_disable;
> + ? ? ? }
> +

but when I look at the failout cleanup, I didn't see the irq being
cleaned up. Maybe I missed something, just wanted to check that.

> +err_clk_disable:
> + ? ? ? clk_disable(clk);
> +err_iounmap_fb:
> + ? ? ? iounmap(fb_base);
> +err_release_resource_fb:
> + ? ? ? release_resource(fb_mem);
> +err_iounmap_reg:
> + ? ? ? iounmap(reg_base);
> +err_release_resource_reg:
> + ? ? ? release_resource(reg_mem);
> +err_free:
> + ? ? ? framebuffer_release(info);
> +err:
> + ? ? ? return ret;
> +}
> +
> +static int tegra_plat_remove(struct platform_device *pdev)
> +{
> + ? ? ? struct fb_info *info = platform_get_drvdata(pdev);
> + ? ? ? struct tegra_fb_info *tegra_fb = info->par;
> + ? ? ? unregister_framebuffer(info);
> + ? ? ? clk_disable(tegra_fb->clk);
> + ? ? ? iounmap(info->screen_base);
> + ? ? ? release_resource(tegra_fb->fb_mem);
> + ? ? ? iounmap(tegra_fb->reg_base);
> + ? ? ? release_resource(tegra_fb->reg_mem);
> + ? ? ? framebuffer_release(info);
> + ? ? ? return 0;
> +}
> +

Thanks,
jaya

  parent reply	other threads:[~2010-04-13 23:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1268721431-24434-1-git-send-email-konkers@google.com>
2010-04-13 22:42 ` [PATCH v2 00/10] Tegra2 support konkers at android.com
2010-04-13 22:42   ` [PATCH v2 01/10] [ARM] tegra: initial tegra support konkers at android.com
2010-04-13 22:42     ` [PATCH v2 02/10] [ARM] tegra: Add IRQ support konkers at android.com
2010-04-13 22:42       ` [PATCH v2 03/10] [ARM] tegra: Add clock support konkers at android.com
2010-04-13 22:42         ` [PATCH v2 04/10] [ARM] tegra: SMP support konkers at android.com
2010-04-13 22:42           ` [PATCH v2 05/10] [ARM] tegra: Add timer support konkers at android.com
2010-04-13 22:42             ` [PATCH v2 06/10] [ARM] tegra: add GPIO support konkers at android.com
2010-04-13 22:42               ` [PATCH v2 07/10] [ARM] tegra: add pinmux support konkers at android.com
2010-04-13 22:42                 ` [PATCH v2 08/10] [ARM] tegra: Add framebuffer driver konkers at android.com
2010-04-13 22:42                   ` [PATCH v2 09/10] [ARM] tegra: harmony: Add harmony board file konkers at android.com
2010-04-13 22:42                     ` [PATCH v2 10/10] [ARM] tegra: Add harmony_defconfig konkers at android.com
2010-04-13 23:26                   ` Jaya Kumar [this message]
2010-05-13  0:49               ` [PATCH v2 06/10] [ARM] tegra: add GPIO support Ben Dooks
2010-04-21 23:46           ` [PATCH v2 04/10] [ARM] tegra: SMP support Olof Johansson
2010-06-14 21:10   ` [PATCH v3 00/11] [ARM] tegra: tegra support Erik Gilling
2010-06-14 21:10     ` [PATCH v3 01/11] [ARM] tegra: initial " Erik Gilling
2010-06-14 21:10       ` [PATCH v3 02/11] [ARM] tegra: Add IRQ support Erik Gilling
2010-06-14 21:10         ` [PATCH v3 03/11] [ARM] tegra: Add clock support Erik Gilling
2010-06-14 21:10           ` [PATCH v3 04/11] [ARM] tegra: SMP support Erik Gilling
2010-06-14 21:10             ` [PATCH v3 05/11] [ARM] tegra: Add timer support Erik Gilling
2010-06-14 21:10               ` [PATCH v3 06/11] [ARM] tegra: add GPIO support Erik Gilling
2010-06-14 21:10                 ` [PATCH v3 07/11] [ARM] tegra: add pinmux support Erik Gilling
2010-06-14 21:10                   ` [PATCH v3 08/11] [ARM] tegra: harmony: Add harmony board file Erik Gilling
2010-06-14 21:10                     ` [PATCH v3 09/11] [ARM] tegra: add MAINTAINERS entry Erik Gilling
2010-06-14 21:10                       ` [PATCH v3 10/11] [ARM] tegra: Add framebuffer driver Erik Gilling
2010-06-14 21:10                         ` [PATCH v3 11/11] [ARM] tegra: add panel support to harmony board files Erik Gilling
2010-06-14 23:59                         ` [PATCH v3 10/11] [ARM] tegra: Add framebuffer driver Jaya Kumar
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=q2l45a44e481004131626j7f5afbfcsfcf861aa70dab651@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).