All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Mythri P K <mythripk@ti.com>,
	linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-media@vger.kernel.org
Subject: Re: [RFC PATCH] HDMI:Support for EDID parsing in kernel.
Date: Tue, 22 Mar 2011 17:58:10 +0000	[thread overview]
Message-ID: <20110322175810.GA32416@linux-sh.org> (raw)
In-Reply-To: <4D88E1FB.5070503@redhat.com>

On Tue, Mar 22, 2011 at 02:52:59PM -0300, Mauro Carvalho Chehab wrote:
> Em 22-03-2011 14:32, Mythri P K escreveu:
> > Adding support for common EDID parsing in kernel.
> > 
> > EDID - Extended display identification data is a data structure provided by
> > a digital display to describe its capabilities to a video source, This a 
> > standard supported by CEA and VESA.
> > 
> > There are several custom implementations for parsing EDID in kernel, some
> > of them are present in fbmon.c, drm_edid.c, sh_mobile_hdmi.c, Ideally
> > parsing of EDID should be done in a library, which is agnostic of the
> > framework (V4l2, DRM, FB)  which is using the functionality, just based on 
> > the raw EDID pointer with size/segment information.
> > 
> > With other RFC's such as the one below, which tries to standardize HDMI API's
> > It would be better to have a common EDID code in one place.It also helps to
> > provide better interoperability with variety of TV/Monitor may be even by
> > listing out quirks which might get missed with several custom implementation
> > of EDID.
> > http://permalink.gmane.org/gmane.linux.drivers.video-input-infrastructure/30401
> > 
> > This patch tries to add functions to parse some portion EDID (detailed timing,
> > monitor limits, AV delay information, deep color mode support, Audio and VSDB)
> > If we can align on this library approach i can enhance this library to parse
> > other blocks and probably we could also add quirks from other implementation
> > as well.
> > 
> > Signed-off-by: Mythri P K <mythripk@ti.com>
> > ---
> >  arch/arm/include/asm/edid.h |  243 ++++++++++++++++++++++++++++++
> >  drivers/video/edid.c        |  340 +++++++++++++++++++++++++++++++++++++++++++
> 
> Hmm... if you want this to be agnostic, the header file should not be inside
> arch/arm, but on some other place, like include/video/.
> 
Ironically this adds a drivers/video/edid.c but completely ignores
drivers/video/edid.h which already exists and already contains many of
these definitions.

I like the idea of a generalized library, but it would be nice to see the
existing edid.h evolved and its users updated incrementally.

WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Mythri P K <mythripk@ti.com>,
	linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-media@vger.kernel.org
Subject: Re: [RFC PATCH] HDMI:Support for EDID parsing in kernel.
Date: Wed, 23 Mar 2011 02:58:10 +0900	[thread overview]
Message-ID: <20110322175810.GA32416@linux-sh.org> (raw)
In-Reply-To: <4D88E1FB.5070503@redhat.com>

On Tue, Mar 22, 2011 at 02:52:59PM -0300, Mauro Carvalho Chehab wrote:
> Em 22-03-2011 14:32, Mythri P K escreveu:
> > Adding support for common EDID parsing in kernel.
> > 
> > EDID - Extended display identification data is a data structure provided by
> > a digital display to describe its capabilities to a video source, This a 
> > standard supported by CEA and VESA.
> > 
> > There are several custom implementations for parsing EDID in kernel, some
> > of them are present in fbmon.c, drm_edid.c, sh_mobile_hdmi.c, Ideally
> > parsing of EDID should be done in a library, which is agnostic of the
> > framework (V4l2, DRM, FB)  which is using the functionality, just based on 
> > the raw EDID pointer with size/segment information.
> > 
> > With other RFC's such as the one below, which tries to standardize HDMI API's
> > It would be better to have a common EDID code in one place.It also helps to
> > provide better interoperability with variety of TV/Monitor may be even by
> > listing out quirks which might get missed with several custom implementation
> > of EDID.
> > http://permalink.gmane.org/gmane.linux.drivers.video-input-infrastructure/30401
> > 
> > This patch tries to add functions to parse some portion EDID (detailed timing,
> > monitor limits, AV delay information, deep color mode support, Audio and VSDB)
> > If we can align on this library approach i can enhance this library to parse
> > other blocks and probably we could also add quirks from other implementation
> > as well.
> > 
> > Signed-off-by: Mythri P K <mythripk@ti.com>
> > ---
> >  arch/arm/include/asm/edid.h |  243 ++++++++++++++++++++++++++++++
> >  drivers/video/edid.c        |  340 +++++++++++++++++++++++++++++++++++++++++++
> 
> Hmm... if you want this to be agnostic, the header file should not be inside
> arch/arm, but on some other place, like include/video/.
> 
Ironically this adds a drivers/video/edid.c but completely ignores
drivers/video/edid.h which already exists and already contains many of
these definitions.

I like the idea of a generalized library, but it would be nice to see the
existing edid.h evolved and its users updated incrementally.

  reply	other threads:[~2011-03-22 17:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 17:32 [RFC PATCH] HDMI:Support for EDID parsing in kernel Mythri P K
2011-03-22 17:44 ` Mythri P K
2011-03-22 17:52 ` Mauro Carvalho Chehab
2011-03-22 17:52   ` Mauro Carvalho Chehab
2011-03-22 17:58   ` Paul Mundt [this message]
2011-03-22 17:58     ` Paul Mundt
2011-03-23 13:47     ` K, Mythri P
2011-03-23 13:59       ` K, Mythri P
2011-03-22 18:32 ` Alex Deucher
2011-03-22 18:32   ` Alex Deucher
2011-03-23  0:46 ` Dave Airlie
2011-03-23  0:46   ` Dave Airlie
2011-03-23  0:46   ` Dave Airlie
2011-03-23 13:28   ` K, Mythri P
2011-03-23 13:40     ` K, Mythri P
2011-03-23 13:28     ` K, Mythri P
2011-03-23 15:18     ` Jesse Barnes
2011-03-23 15:18       ` Jesse Barnes
2011-03-24  9:51       ` K, Mythri P
2011-03-24  9:52         ` K, Mythri P
2011-03-24  9:51         ` K, Mythri P
2011-03-24 19:06         ` Corbin Simpson
2011-03-24 19:06           ` Corbin Simpson
2011-03-24 22:43           ` Florian Tobias Schandinat
2011-03-24 22:43             ` Florian Tobias Schandinat
2011-03-25 15:21             ` K, Mythri P
2011-03-25 15:33               ` K, Mythri P
2011-03-24 19:13         ` Guennadi Liakhovetski
2011-03-24 19:13           ` Guennadi Liakhovetski
2011-03-24 19:13           ` Guennadi Liakhovetski
2011-03-24 19:22           ` Alex Deucher
2011-03-24 19:22             ` Alex Deucher
2011-03-25 13:34           ` K, Mythri P
2011-03-25 13:46             ` K, Mythri P

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=20110322175810.GA32416@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=mythripk@ti.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 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.