From: Timur Tabi <timur@freescale.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v4 3/5] powerpc/mpc5121: shared DIU framebuffer support
Date: Fri, 16 Dec 2011 18:24:49 +0000 [thread overview]
Message-ID: <4EEB8CF1.4050902@freescale.com> (raw)
In-Reply-To: <1279893639-24333-4-git-send-email-agust@denx.de>
Anatolij Gustschin wrote:
> We cannot guarantee that the DIU is not in these modes. Even
> if U-Boot didn't set these modes there is still a possibility
> that such mode is configured. E.g. I've seen U-Boot binary
> standalone applications for other display controllers initializing
> the display controller.
True, but modes 2 and 3 don't make any sense. 2 is just a color bar, and 3 writes back to memory (which means you need to have a reserved DMA buffer otherwise you'll crash). Have you really seen Linux boot with the DIU in either of these modes?
> But you are right. With this snippet, if the DIU is already
> disabled, there will be not needed mode register access. So
> the code should better look like:
>
> diu_mode = in_be32(&dr.diu_reg->diu_mode);
> if (diu_mode && diu_mode != MFB_MODE1)
> out_be32(&dr.diu_reg->diu_mode, 0);
Ok. I'm planning on cleaning up the driver so that it does not initialize the DIU until the .open call, and once that's done, I should be able to remove most of the code from your patch.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-12-16 18:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 14:00 [PATCH v4 0/5] Rework MPC5121 DIU support (for 2.6.36) Anatolij Gustschin
2010-07-23 14:00 ` [PATCH v4 1/5] fsl-diu-fb: fix issue with re-enabling DIU area descriptor Anatolij Gustschin
2010-07-28 7:02 ` [PATCH v4 1/5] fsl-diu-fb: fix issue with re-enabling DIU area Grant Likely
[not found] ` <AANLkTikkLVCxU4ZC_nmUhKTQogUNeQzxOX6KqgZcxiYr-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-28 7:56 ` Anatolij Gustschin
2010-07-23 14:00 ` [PATCH v4 2/5] fsl-diu-fb: move fsl-diu-fb.h to include/linux Anatolij Gustschin
2010-07-23 14:00 ` [PATCH v4 3/5] powerpc/mpc5121: shared DIU framebuffer support Anatolij Gustschin
2011-12-15 17:27 ` Tabi Timur-B04825
2011-12-15 21:26 ` Anatolij Gustschin
2011-12-16 18:24 ` Timur Tabi [this message]
2011-12-16 22:59 ` Anatolij Gustschin
2011-12-16 23:00 ` Timur Tabi
2010-07-23 14:00 ` [PATCH v4 4/5] powerpc: doc/dts-bindings: update doc of FSL DIU bindings Anatolij Gustschin
2010-07-23 14:00 ` [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID Anatolij Gustschin
[not found] ` <1279893639-24333-6-git-send-email-agust-ynQEQJNshbs@public.gmane.org>
2010-12-16 16:47 ` Timur Tabi
[not found] ` <AANLkTin-TL5_TKnyHYtZdixosfqpkPNoarSTC+K4tTUb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-16 16:53 ` Grant Likely
2010-12-16 16:55 ` [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using Timur Tabi
[not found] ` <4D0A446E.5020600-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2010-12-16 17:06 ` [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID Grant Likely
2010-12-16 17:28 ` [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using Timur Tabi
2010-12-16 17:42 ` [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID Grant Likely
2010-12-16 17:42 ` [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using Anatolij Gustschin
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=4EEB8CF1.4050902@freescale.com \
--to=timur@freescale.com \
--cc=linux-fbdev@vger.kernel.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).