Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp7755933yba; Thu, 2 May 2019 15:55:38 -0700 (PDT) X-Google-Smtp-Source: APXvYqyPTZNb1zX4Rwws4TYsMFU76vE34eaRydOYn0Lmdaf9i75yxvZVHiO2OXS3ORMpz2IItM/2 X-Received: by 2002:a62:e90d:: with SMTP id j13mr7240840pfh.42.1556837738613; Thu, 02 May 2019 15:55:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556837738; cv=none; d=google.com; s=arc-20160816; b=rEX3YbshsX4qujUNtyYMnInk3/jDsdL+xu570+z+mbrouQ23ziKDb5oa+ynqH6Bm+n aoRhyHptWs1k/oLZGIEYeFUPrIsX7G6JBaYvhI/GNyQXxWiAxhxX5wuMvly/V1MZYero 2D/utnomiZJTWXklLSRojBRhneKlYWp2rpR9KdgjeARg9BtyIROQg+wAx4BzVMmyyk1A VfxvM6vhlpuEmYWC8Hbboq71l9WnF+mTu9ZfY3e/7tFGcojgD24Id5y4nJIC7lBA7qjL dYxEvtPEiHlofjiHI/ufsW8+LyjcDAUN9iS8M9vTqvF5TMKRV1U4y4bkepfSvCmaN4k+ eLIQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=U2bbAFLYHg7BbnCqa8Z/3P6ZnGKzIwrgxFqmU0u6MtQ=; b=K0W2569SK/G5qrPezQVRvDdx0IZfAxDFTjEoFFmJuKvaUVLc1C778EI+dLVhIZ8Hvc QGxSJtMaPWGuk1MYhdz3qdG6aH1ieT+KJFwp8JpQ4U/4tmnmdA5V19GL9GCrRX8BoWE2 3iGg29aiWUtDbxiU4pK3P4//od1pHowhMrr6nAs0AubknNb1JeDqsAjCkLsg1PWsVwZB b4t8ZE2o1w1M88QYFRl6YjnOkXEqoSMe147Y8e4KuUpsUENM7NnEFKrZQdjljx5sA0af Ctxu6KSfLDzmaFxApPRFNjs5XLwHWKSJ8TRoJT2EXvVDAzR/myuWh1Mqsj/j8TAYGBT0 FnPA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=nvDXTTBk; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bb8si470342plb.388.2019.05.02.15.55.21; Thu, 02 May 2019 15:55:38 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=nvDXTTBk; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726278AbfEBWyZ (ORCPT + 99 others); Thu, 2 May 2019 18:54:25 -0400 Received: from mail-pf1-f193.google.com ([209.85.210.193]:43091 "EHLO mail-pf1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726022AbfEBWyZ (ORCPT ); Thu, 2 May 2019 18:54:25 -0400 Received: by mail-pf1-f193.google.com with SMTP id e67so1845751pfe.10 for ; Thu, 02 May 2019 15:54:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=U2bbAFLYHg7BbnCqa8Z/3P6ZnGKzIwrgxFqmU0u6MtQ=; b=nvDXTTBkx6gM2GY6hocJXtXsnawL+o/xemGlJje4+eusDN2A0o97J9U5hlrR6RCeYY IaJiOv66CzjRFRG/86f/hhXlcSZ+ENN1Ls1spzYSyWL9Pe4VRgvlST5J0rYjN+wmNlBC i7F+im4W83ea6FPef3xVPExFEFv7Pdt/bcRcQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=U2bbAFLYHg7BbnCqa8Z/3P6ZnGKzIwrgxFqmU0u6MtQ=; b=eS8MZjD56qQZOU0tNbe244cX7zL7iO8iVZ6WJv5arM+GOAFylY9sz1ZiOCTPNqkOTh SEXyoulSgP+ntWZISu7qjwVJQlZePJ8/XVHDS3ZZTUVd6X6BD6WD1PDhyPQXcofzIg5P yRfT7Hr3iKTP0Wp9KELUh0IPBVIcUQpQ61LJydDOfsIxpV+BIm4XpGuqcvydqxH+Q2YZ 4OZKZUttckO/75pxmtzihtllEKif8YuMkvOMloJ71sO2v/F5egodVBVt0ExxhPXHt9W7 QX85eNjaIz4kOGcUD+Nam8o/7jUMmZEHd4t/IgsID3DrgQwQDKsmy8J7wfcAMa/ObFaZ YAqA== X-Gm-Message-State: APjAAAXTGYYY+ygxHSLTTN2bAovuAydCLMFv3fBDHdZIGUk675EwAIXp rk1agU5he6G8j1G4H2d7XbAL3Q== X-Received: by 2002:a65:6688:: with SMTP id b8mr6519822pgw.81.1556837664123; Thu, 02 May 2019 15:54:24 -0700 (PDT) Received: from tictac2.mtv.corp.google.com ([2620:15c:202:1:24fa:e766:52c9:e3b2]) by smtp.gmail.com with ESMTPSA id v15sm264736pff.105.2019.05.02.15.54.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 May 2019 15:54:23 -0700 (PDT) From: Douglas Anderson To: Heiko Stuebner , Sandy Huang , Andrzej Hajda , Laurent Pinchart , Rob Herring Cc: linux-rockchip@lists.infradead.org, Neil Armstrong , Mark Rutland , mka@chromium.org, Sean Paul , Douglas Anderson , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, David Airlie , linux-arm-kernel@lists.infradead.org, Daniel Vetter Subject: [PATCH 1/5] dt-bindings: drm/bridge/synopsys: dw-hdmi: Add "unwedge" for ddc bus Date: Thu, 2 May 2019 15:53:32 -0700 Message-Id: <20190502225336.206885-1-dianders@chromium.org> X-Mailer: git-send-email 2.21.0.1020.gf2820cf01a-goog MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 --- .../bindings/display/rockchip/dw_hdmi-rockchip.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Documentation/devicetree/bindings/display/rockchip/dw_hdmi-rockchip.txt b/Documentation/devicetree/bindings/display/rockchip/dw_hdmi-rockchip.txt index 39143424a474..8346bac81f1c 100644 --- a/Documentation/devicetree/bindings/display/rockchip/dw_hdmi-rockchip.txt +++ b/Documentation/devicetree/bindings/display/rockchip/dw_hdmi-rockchip.txt @@ -38,6 +38,13 @@ Optional properties - phys: from general PHY binding: the phandle for the PHY device. - phy-names: Should be "hdmi" if phys references an external phy. +Optional pinctrl entry: +- If you have both a "unwedge" and "default" pinctrl entry, dw_hdmi + will switch to the unwedge pinctrl state for 10ms if it ever gets an + i2c timeout. It's intended that this unwedge pinctrl entry will + cause the SDA line to be driven low to work around a hardware + errata. + Example: hdmi: hdmi@ff980000 { -- 2.21.0.1020.gf2820cf01a-goog