From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 004BCC2B9F8 for ; Tue, 25 May 2021 09:11:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D21DE6141B for ; Tue, 25 May 2021 09:11:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232360AbhEYJMg (ORCPT ); Tue, 25 May 2021 05:12:36 -0400 Received: from wnew2-smtp.messagingengine.com ([64.147.123.27]:57127 "EHLO wnew2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231384AbhEYJMe (ORCPT ); Tue, 25 May 2021 05:12:34 -0400 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailnew.west.internal (Postfix) with ESMTP id 0BFCC9E2; Tue, 25 May 2021 05:11:03 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 25 May 2021 05:11:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cerno.tech; h= from:to:cc:subject:date:message-id:content-type:mime-version :content-transfer-encoding; s=fm2; bh=ihjrZyupxC2RY6LoFXxJCvJTHQ 9fJ9jSbr/clQHZS30=; b=pQeXP5AIk15bBOd/X+o0sOjoccxnmHsiH5psfIdsGm pDrEzLuifnSZoayrcHu5lzOEVDsOMuh4TqqA/khZ9Tvkyb1oDMTXOPVUp9dMPJ5U 1agg5ZzwlIrMwDHUZAXzvvszeZQKG4WcenIe5LkZcXy1LhnuTo550TpoHm2JQNtq Mv0NM+4ZXwwpA2qDIRVAz711fK2ML3xv7kVZbxN6R3Lq0T4uaz/F4K53WVRNsVGb lwUY2FnSbc/AnppofPjVuFIYPx2fUJaojCcSC60hTwQlzqr/pVMzNpRmsOzkVQ0+ HlxzmUTj22XMzJsq5ZcKetamtwQZBkEU3yIvnpPH8Z6Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ihjrZy upxC2RY6LoFXxJCvJTHQ9fJ9jSbr/clQHZS30=; b=dsT1bzI4VX4yQaQAdk+pBK Ok9iwk7+5gjLjT7b+G6CpeGZ0dj0DNVHb1ef2Jo1CWN+CX2/pRgEv9bSSUAXJ/dS Z39fNiTKhZQv6CJWCqMnqNpMIwYmkrpw/4s9cylZFU2hon8HP0bo67GtHe3Ne0wn 0MzJ+J+7TnQgrSaOYi05cNPgcsry3MjJaRap9Byi/q85gMjYz0iiRqdsFm0t06b4 gRXMFwBEahGK2Vmji/CzWsdSV7CXdrXfOncQbZXWBaUlEPfStI0rJNHbFS6ZqGBa fRUu8gtmpNTG/nQO2hDGjQdbicKtGGjlMeviOTMpun7lah7rS/jt06zxpId/5OCg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdekuddgudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkffotggggfesthhqredtredtjeenucfhrhhomhepofgrgihimhgv ucftihhprghrugcuoehmrgigihhmvgestggvrhhnohdrthgvtghhqeenucggtffrrghtth gvrhhnpeetieekgfffkeegkeeltdehudetteejgfekueevhffhteegudfgkedtueegfffg feenucfkphepledtrdekledrieekrdejieenucevlhhushhtvghrufhiiigvpedtnecurf grrhgrmhepmhgrihhlfhhrohhmpehmrgigihhmvgestggvrhhnohdrthgvtghh X-ME-Proxy: Received: from localhost (lfbn-tou-1-1502-76.w90-89.abo.wanadoo.fr [90.89.68.76]) by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 25 May 2021 05:11:01 -0400 (EDT) From: Maxime Ripard To: dri-devel@lists.freedesktop.org, Daniel Vetter , David Airlie , Maarten Lankhorst , Thomas Zimmermann , Maxime Ripard Cc: Daniel Vetter , Boris Brezillon , linux-kernel@vger.kernel.org, Eric Anholt , Emma Anholt , Dave Stevenson , Phil Elwell , Tim Gover , Dom Cobley , Maxime Ripard Subject: [PATCH 0/3] drm/vc4: Fix for the HDMI detect power state Date: Tue, 25 May 2021 11:10:56 +0200 Message-Id: <20210525091059.234116-1-maxime@cerno.tech> X-Mailer: git-send-email 2.31.1 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi,=0D =0D This fixes an issue found during a rework on the RPi3 where we would=0D end up with the detect callback of the HDMI connector called while the=0D device would be disabled.=0D =0D This unfortunately results in a complete CPU hang on the RaspberryPi.=0D =0D The documentation doesn't really provide any expectation on the power=0D state for various operations that could be performed while the device is=0D off, so the first patch makes that clear. The next two patches make sure=0D the device is sufficiently powered for detect to run without any issue.=0D =0D Let me know what you think,=0D Maxime=0D =0D Maxime Ripard (3):=0D drm: Mention the power state requirement on side-channel operations=0D drm/vc4: hdmi: Move the HSM clock enable to runtime_pm=0D drm/vc4: hdmi: Make sure the controller is powered in detect=0D =0D drivers/gpu/drm/vc4/vc4_hdmi.c | 45 ++++++++++++++++++++++++++--------=0D include/drm/drm_connector.h | 5 ++++=0D include/drm/drm_dp_helper.h | 4 +++=0D include/drm/drm_mipi_dsi.h | 5 ++++=0D 4 files changed, 49 insertions(+), 10 deletions(-)=0D =0D -- =0D 2.31.1=0D =0D