All of lore.kernel.org
 help / color / mirror / Atom feed
From: vladimir_zapolskiy@mentor.com (Vladimir Zapolskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm: bridge/dw_hdmi: add dw hdmi i2c bus adapter support
Date: Mon, 28 Sep 2015 23:08:17 +0300	[thread overview]
Message-ID: <56099E31.6050908@mentor.com> (raw)
In-Reply-To: <1443470762-17937-1-git-send-email-vladimir_zapolskiy@mentor.com>

On 28.09.2015 23:06, Vladimir Zapolskiy wrote:
> The change adds support of internal HDMI I2C master controller, this
> subdevice is used by default, if "ddc-i2c-bus" DT property is omitted.
> 
> The main purpose of this functionality is to support reading EDID from
> an HDMI monitor on boards, which don't have an I2C bus connected to
> DDC pins.
> 
> The current implementation does not support "I2C Master Interface
> Extended Read Mode" to read data addressed by non-zero segment
> pointer, this means that if EDID has more than 1 extension blocks,
> EDID reading operation won't succeed, in my practice all tested HDMI
> monitors have at maximum one extension block.
> 
> Signed-off-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
> ---
>  .../devicetree/bindings/drm/bridge/dw_hdmi.txt     |   4 +-
>  drivers/gpu/drm/bridge/dw_hdmi.c                   | 263 ++++++++++++++++++++-
>  drivers/gpu/drm/bridge/dw_hdmi.h                   |  19 ++
>  3 files changed, 279 insertions(+), 7 deletions(-)
> 

This change is the same as one in reply, but no changelog/version info
(sent by mistake two copies, sorry for confusion).

--
With best wishes,
Vladimir

WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Russell King <rmk+kernel@arm.linux.org.uk>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Andy Yan <andy.yan@rock-chips.com>,
	Doug Anderson <dianders@chromium.org>
Cc: linux-arm-kernel@lists.infradead.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: bridge/dw_hdmi: add dw hdmi i2c bus adapter support
Date: Mon, 28 Sep 2015 23:08:17 +0300	[thread overview]
Message-ID: <56099E31.6050908@mentor.com> (raw)
In-Reply-To: <1443470762-17937-1-git-send-email-vladimir_zapolskiy@mentor.com>

On 28.09.2015 23:06, Vladimir Zapolskiy wrote:
> The change adds support of internal HDMI I2C master controller, this
> subdevice is used by default, if "ddc-i2c-bus" DT property is omitted.
> 
> The main purpose of this functionality is to support reading EDID from
> an HDMI monitor on boards, which don't have an I2C bus connected to
> DDC pins.
> 
> The current implementation does not support "I2C Master Interface
> Extended Read Mode" to read data addressed by non-zero segment
> pointer, this means that if EDID has more than 1 extension blocks,
> EDID reading operation won't succeed, in my practice all tested HDMI
> monitors have at maximum one extension block.
> 
> Signed-off-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
> ---
>  .../devicetree/bindings/drm/bridge/dw_hdmi.txt     |   4 +-
>  drivers/gpu/drm/bridge/dw_hdmi.c                   | 263 ++++++++++++++++++++-
>  drivers/gpu/drm/bridge/dw_hdmi.h                   |  19 ++
>  3 files changed, 279 insertions(+), 7 deletions(-)
> 

This change is the same as one in reply, but no changelog/version info
(sent by mistake two copies, sorry for confusion).

--
With best wishes,
Vladimir
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-09-28 20:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 20:06 [PATCH] drm: bridge/dw_hdmi: add dw hdmi i2c bus adapter support Vladimir Zapolskiy
2015-09-28 20:06 ` Vladimir Zapolskiy
2015-09-28 20:06 ` [PATCH v5] " Vladimir Zapolskiy
2015-09-28 20:06   ` Vladimir Zapolskiy
2015-09-28 20:08 ` Vladimir Zapolskiy [this message]
2015-09-28 20:08   ` [PATCH] " Vladimir Zapolskiy

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=56099E31.6050908@mentor.com \
    --to=vladimir_zapolskiy@mentor.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 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.