public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel•org>
To: Douglas Anderson <dianders@chromium•org>
Cc: Mark Rutland <mark.rutland@arm•com>,
	devicetree@vger•kernel.org, Heiko Stuebner <heiko@sntech•de>,
	linux-rockchip@lists•infradead.org,
	David Airlie <airlied@linux•ie>,
	linux-kernel@vger•kernel.org,
	Neil Armstrong <narmstrong@baylibre•com>,
	Sandy Huang <hjc@rock-chips•com>,
	dri-devel@lists•freedesktop.org,
	Douglas Anderson <dianders@chromium•org>,
	Andrzej Hajda <a.hajda@samsung•com>,
	mka@chromium•org, Sean Paul <seanpaul@chromium•org>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard•com>,
	Daniel Vetter <daniel@ffwll•ch>,
	linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH 1/5] dt-bindings: drm/bridge/synopsys: dw-hdmi: Add "unwedge" for ddc bus
Date: Tue, 14 May 2019 15:49:12 -0500	[thread overview]
Message-ID: <20190514204912.GA25548@bogus> (raw)
In-Reply-To: <20190502225336.206885-1-dianders@chromium.org>

On Thu,  2 May 2019 15:53:32 -0700, Douglas Anderson wrote:
> In certain situations it was seen that we could wedge up the DDC bus
> on the HDMI adapter on rk3288.  The only way to unwedge was to mux one
> of the pins over to GPIO output-driven-low temporarily and then
> quickly mux back.  Full details can be found in the patch
> ("drm/bridge/synopsys: dw-hdmi: Add "unwedge" for ddc bus").
> 
> Since unwedge requires remuxing the pins, we first need to add to the
> bindings so that we can specify what state the pins should be in for
> unwedging.
> 
> Signed-off-by: Douglas Anderson <dianders@chromium•org>
> ---
> 
>  .../bindings/display/rockchip/dw_hdmi-rockchip.txt         | 7 +++++++
>  1 file changed, 7 insertions(+)
> 

Reviewed-by: Rob Herring <robh@kernel•org>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-05-14 20:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02 22:53 [PATCH 1/5] dt-bindings: drm/bridge/synopsys: dw-hdmi: Add "unwedge" for ddc bus Douglas Anderson
2019-05-02 22:53 ` [PATCH 3/5] ARM: dts: rockchip: Switch to builtin HDMI DDC bus on rk3288-veyron Douglas Anderson
2019-05-15 18:25   ` Sean Paul
2019-06-06 10:28   ` Heiko Stuebner
2019-05-02 22:53 ` [PATCH 4/5] ARM: dts: rockchip: Add unwedge pinctrl entries for dw_hdmi on rk3288 Douglas Anderson
2019-05-15 18:25   ` Sean Paul
2019-05-02 22:53 ` [PATCH 5/5] ARM: dts: rockchip: Add HDMI i2c unwedging for rk3288-veyron Douglas Anderson
2019-05-15 18:26   ` Sean Paul
2019-05-14 20:49 ` Rob Herring [this message]
2019-06-05 20:21 ` [PATCH 1/5] dt-bindings: drm/bridge/synopsys: dw-hdmi: Add "unwedge" for ddc bus Sean Paul

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=20190514204912.GA25548@bogus \
    --to=robh@kernel$(echo .)org \
    --cc=Laurent.pinchart@ideasonboard$(echo .)com \
    --cc=a.hajda@samsung$(echo .)com \
    --cc=airlied@linux$(echo .)ie \
    --cc=daniel@ffwll$(echo .)ch \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=dianders@chromium$(echo .)org \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=heiko@sntech$(echo .)de \
    --cc=hjc@rock-chips$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-rockchip@lists$(echo .)infradead.org \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=mka@chromium$(echo .)org \
    --cc=narmstrong@baylibre$(echo .)com \
    --cc=seanpaul@chromium$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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