From: Timur Tabi <timur-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Anatolij Gustschin <agust-ynQEQJNshbs@public.gmane.org>
Cc: linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
linux-fbdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID
Date: Thu, 16 Dec 2010 10:47:53 -0600 [thread overview]
Message-ID: <AANLkTin-TL5_TKnyHYtZdixosfqpkPNoarSTC+K4tTUb@mail.gmail.com> (raw)
In-Reply-To: <1279893639-24333-6-git-send-email-agust-ynQEQJNshbs@public.gmane.org>
On Fri, Jul 23, 2010 at 9:00 AM, Anatolij Gustschin <agust-ynQEQJNshbs@public.gmane.org> wrote:
> Adds support for encoding display mode information
> in the device tree using verbatim EDID block.
>
> If the EDID entry in the DIU node is present, the
> driver will build mode database using EDID data
> and allow setting the display modes from this database.
> Otherwise display mode will be set using mode
> entries from driver's internal database as usual.
>
> This patch also updates device tree bindings.
>
> Signed-off-by: Anatolij Gustschin <agust-ynQEQJNshbs@public.gmane.org>
> Acked-by: Timur Tabi <timur-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
> Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Anatolij,
I know this patch is old, but I'm now getting back to working on the
DIU driver. One question I have: why are you reading the EDID data
from the device tree? Why not just read it directly from the device
using I2C? Who is supposed to put the EDID data into the device tree
in the first place?
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Anatolij Gustschin <agust-ynQEQJNshbs@public.gmane.org>
Cc: linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
linux-fbdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID
Date: Thu, 16 Dec 2010 16:47:53 +0000 [thread overview]
Message-ID: <AANLkTin-TL5_TKnyHYtZdixosfqpkPNoarSTC+K4tTUb@mail.gmail.com> (raw)
In-Reply-To: <1279893639-24333-6-git-send-email-agust-ynQEQJNshbs@public.gmane.org>
On Fri, Jul 23, 2010 at 9:00 AM, Anatolij Gustschin <agust@denx.de> wrote:
> Adds support for encoding display mode information
> in the device tree using verbatim EDID block.
>
> If the EDID entry in the DIU node is present, the
> driver will build mode database using EDID data
> and allow setting the display modes from this database.
> Otherwise display mode will be set using mode
> entries from driver's internal database as usual.
>
> This patch also updates device tree bindings.
>
> Signed-off-by: Anatolij Gustschin <agust@denx.de>
> Acked-by: Timur Tabi <timur@freescale.com>
> Cc: devicetree-discuss@lists.ozlabs.org
Anatolij,
I know this patch is old, but I'm now getting back to working on the
DIU driver. One question I have: why are you reading the EDID data
from the device tree? Why not just read it directly from the device
using I2C? Who is supposed to put the EDID data into the device tree
in the first place?
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Anatolij Gustschin <agust@denx.de>
Cc: linuxppc-dev@ozlabs.org, linux-fbdev@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID
Date: Thu, 16 Dec 2010 10:47:53 -0600 [thread overview]
Message-ID: <AANLkTin-TL5_TKnyHYtZdixosfqpkPNoarSTC+K4tTUb@mail.gmail.com> (raw)
In-Reply-To: <1279893639-24333-6-git-send-email-agust@denx.de>
On Fri, Jul 23, 2010 at 9:00 AM, Anatolij Gustschin <agust@denx.de> wrote:
> Adds support for encoding display mode information
> in the device tree using verbatim EDID block.
>
> If the EDID entry in the DIU node is present, the
> driver will build mode database using EDID data
> and allow setting the display modes from this database.
> Otherwise display mode will be set using mode
> entries from driver's internal database as usual.
>
> This patch also updates device tree bindings.
>
> Signed-off-by: Anatolij Gustschin <agust@denx.de>
> Acked-by: Timur Tabi <timur@freescale.com>
> Cc: devicetree-discuss@lists.ozlabs.org
Anatolij,
I know this patch is old, but I'm now getting back to working on the
DIU driver. One question I have: why are you reading the EDID data
from the device tree? Why not just read it directly from the device
using I2C? Who is supposed to put the EDID data into the device tree
in the first place?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2010-12-16 16:47 UTC|newest]
Thread overview: 42+ 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 ` 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-23 14:00 ` Anatolij Gustschin
2010-07-28 7:02 ` Grant Likely
2010-07-28 7:02 ` Grant Likely
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 ` [PATCH v4 1/5] fsl-diu-fb: fix issue with re-enabling DIU area descriptor Anatolij Gustschin
2010-07-28 7:56 ` Anatolij Gustschin
2010-07-28 7:56 ` [PATCH v4 1/5] fsl-diu-fb: fix issue with re-enabling DIU area Anatolij Gustschin
[not found] ` <AANLkTikkLVCxU4ZC_nmUhKTQogUNeQzxOX6KqgZcxiYr__2540.83384429595$1280300644$gmane$org@mail.gmail.com>
2010-07-29 11:48 ` [PATCH v4 1/5] fsl-diu-fb: fix issue with re-enabling DIU area descriptor Detlev Zundel
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 ` Anatolij Gustschin
2010-07-23 14:00 ` [PATCH v4 3/5] powerpc/mpc5121: shared DIU framebuffer support Anatolij Gustschin
2010-07-23 14:00 ` Anatolij Gustschin
2011-12-15 17:27 ` Tabi Timur-B04825
2011-12-15 21:26 ` Anatolij Gustschin
2011-12-16 18:24 ` Timur Tabi
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 ` Anatolij Gustschin
2010-07-23 14:00 ` [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID Anatolij Gustschin
2010-07-23 14:00 ` Anatolij Gustschin
[not found] ` <1279893639-24333-6-git-send-email-agust-ynQEQJNshbs@public.gmane.org>
2010-12-16 16:47 ` Timur Tabi [this message]
2010-12-16 16:47 ` Timur Tabi
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:53 ` Grant Likely
2010-12-16 16:53 ` Grant Likely
2010-12-16 16:55 ` Timur Tabi
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:06 ` Grant Likely
2010-12-16 17:06 ` Grant Likely
2010-12-16 17:28 ` Timur Tabi
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 ` Grant Likely
2010-12-16 17:42 ` Grant Likely
2010-12-16 17:42 ` Anatolij Gustschin
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=AANLkTin-TL5_TKnyHYtZdixosfqpkPNoarSTC+K4tTUb@mail.gmail.com \
--to=timur-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=agust-ynQEQJNshbs@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-fbdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.