Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp4270090ybp; Mon, 7 Oct 2019 06:04:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqxuqYWKKSVZrrY82aKIzjCNPKv3BQfFSvKtR02Fg2TvJkJVxRyiFeXS6JrsGJssu8O4mn9L X-Received: by 2002:a17:906:25ca:: with SMTP id n10mr24064245ejb.106.1570453475665; Mon, 07 Oct 2019 06:04:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570453475; cv=none; d=google.com; s=arc-20160816; b=MSBnq3WfVjZBsJi5hx/QHJbrls9EUkNqGmAMXSgA3AtBJSxgJKfvMUXAuxmoc9HlM9 WYl37Z5KbzbG3F+t7Ry3DIr6g9GG3TG1PgkYJZwfczOILogwTxempAP0fL9pj31TwB26 fYzc7+dFQojC4RnJ5oejE0gs8j9APOJ7w5GrIGuMIxuUs/wMaoxoPR9NS71RUMB1gN3T m3HT9gl5Lf8bcjsCB3VxWrBqQEzFbHOvDn8/99sg1qgQAN2tjTSG11RA5Rwks3cBqIKH ej/R0PrIyL4nX8D0nsMT5yDr6CIhgG+odFr08yQ85HhDlr0ed3RYBeR82nAwWMbbNcDi hkMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=Ds8WznLX+NYi3ptkiUX0OCakAHSXETW90blbf1WdtvY=; b=CDpjE08/u+BJv8wSgM7FZ2M6hPl490vCvbEP4VewBfT6NUoDjFCaToqhx4iPJV2S5h UaCqnoUQ4CmaioiFVPNp8YjX5dg2YJsst/FSKVwby1dfTKl37YZEBCIcc/G39rE6D7qK HYgIllcNN+th1FnOfu2GBGdf59HfvKVMrpU/TdNLd9wD2ld9SCGX5VAnFHi5XLCBRVR2 Gf0PjKzwYhSPxGxy/gwqUYc8jfAFY3D1IC1l7WwvBS3CX5G1zRroTFHn8WLQMXgwhNnB M95HodnNISu9W9ZBlx/WTnIF8A/FEvq10Jq5OBzirnFM48dy2iPNLN9QC5HgVy8sytAR ngdw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=SeFZrK8g; 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 p15si8550291eda.294.2019.10.07.06.04.11; Mon, 07 Oct 2019 06:04:35 -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=SeFZrK8g; 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 S1728290AbfJGNDk (ORCPT + 99 others); Mon, 7 Oct 2019 09:03:40 -0400 Received: from mail-ua1-f68.google.com ([209.85.222.68]:36247 "EHLO mail-ua1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728146AbfJGNDi (ORCPT ); Mon, 7 Oct 2019 09:03:38 -0400 Received: by mail-ua1-f68.google.com with SMTP id r25so3999610uam.3 for ; Mon, 07 Oct 2019 06:03:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Ds8WznLX+NYi3ptkiUX0OCakAHSXETW90blbf1WdtvY=; b=SeFZrK8gMg6fY4PxMOK0NPAoUBk5SKZP6Rm2RpMc1sRZKgJg2NDDLR9yH+ZTkFrojb ECECpc6XwZXZYWrLpY3dkrOp1pLvCwRPEB3LV/Opy8prDkyQaXBI+0Em6seuvBwIpUf3 WSFX4glUQS905Oi7/4W2htI0p1s5RzgKNERk4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Ds8WznLX+NYi3ptkiUX0OCakAHSXETW90blbf1WdtvY=; b=BUhYbNhTkeHvO2qlf1ePV72Cuxuwkft5xMGmsnEUA6sWmgK/v063Ugok2d/VzLIyCY ElRANH9FWDnFMbbLMzMgm7JQzPPeAyI8jW4TUuvNjBZR1//XJzGuVtnzgPQ6wuYAw/lv xwlpFX6cY6/4gv4jP4tqDdG1AHPfCFKgO9TpFGtNIXSrYB4huOXwtvH5BowHJFtFLWPS 39oaK4hzx+f3kC5DJE1xaBhzB0fdznMGTWoSnQarBEHyffDI6ezKUcrI4QyZ4iQvKxX7 AlJEohYYaJx02EWaXIYLqEBYpkymYXBnGBskPUt4J6X9O/u+z+ndLRzyY8bkqCXNTH9w Br1w== X-Gm-Message-State: APjAAAXgENsfSOJt9ml+449b2XCPDGmgszjvK+B33bzEddLNUU5U052y 9BoaAz9FQBwaf3bp5N8GGNTnFdFKgckFzdyE783p0A== X-Received: by 2002:a9f:2924:: with SMTP id t33mr11661088uat.69.1570453416905; Mon, 07 Oct 2019 06:03:36 -0700 (PDT) MIME-Version: 1.0 References: <20191003041438.194224-1-cychiang@chromium.org> In-Reply-To: From: Cheng-yi Chiang Date: Mon, 7 Oct 2019 21:03:10 +0800 Message-ID: Subject: Re: [PATCH v2 RESEND] drm/bridge: dw-hdmi: Restore audio when setting a mode To: Neil Armstrong Cc: linux-kernel , Jerome Brunet , Jernej Skrabec , Jonas Karlman , Hans Verkuil , Mark Brown , Jaroslav Kysela , Russell King , Doug Anderson , Dylan Reid , Tzung-Bi Shih , "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." , dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, Daniel Kurtz , Yakir Yang Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 7, 2019 at 7:57 PM Neil Armstrong wrote: > > Hi, > > On 03/10/2019 06:14, Cheng-Yi Chiang wrote: > > From: Daniel Kurtz > > > > When setting a new display mode, dw_hdmi_setup() calls > > dw_hdmi_enable_video_path(), which disables all hdmi clocks, including > > the audio clock. > > > > We should only (re-)enable the audio clock if audio was already enabled > > when setting the new mode. > > > > Without this patch, on RK3288, there will be HDMI audio on some monitors > > if i2s was played to headphone when the monitor was plugged. > > ACER H277HU and ASUS PB278 are two of the monitors showing this issue. > > > > Signed-off-by: Cheng-Yi Chiang > > Signed-off-by: Daniel Kurtz > > Signed-off-by: Yakir Yang > > --- > > Change from v1 to v2: > > - Use audio_lock to protect audio clock. > > - Fix the patch title. > > > > drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 13 ++++++++++++- > > 1 file changed, 12 insertions(+), 1 deletion(-) > > > > diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c > > index aa7efd4da1c8..749d8e4c535b 100644 > > --- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c > > +++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c > > @@ -1982,6 +1982,17 @@ static void hdmi_disable_overflow_interrupts(struct dw_hdmi *hdmi) > > HDMI_IH_MUTE_FC_STAT2); > > } > > > > +static void dw_hdmi_audio_restore(struct dw_hdmi *hdmi) > > +{ > > + unsigned long flags; > > + > > + spin_lock_irqsave(&hdmi->audio_lock, flags); > > + > > + hdmi_enable_audio_clk(hdmi, hdmi->audio_enable); > > + > > + spin_unlock_irqrestore(&hdmi->audio_lock, flags); > > Dumb question, why is this protected by a spinlock ? > > Neil > Hi Neil, Thanks for the review. Good catch. I found that the spinlock audio_lock was introduced in b90120a96608 drm: bridge/dw_hdmi: introduce interfaces to enable and disable audio to protect N/CTS value. Actually it was not used to protect audio clock. So we don't need this spinlock. Hi Daniel Kurtz, If this rings any bell in your memory as for why this is protected, please let me know. I would like to remove this spinlock and simplify this patch in v3. Thanks! > > +} > > + > > static int dw_hdmi_setup(struct dw_hdmi *hdmi, struct drm_display_mode *mode) > > { > > int ret; > > @@ -2045,7 +2056,7 @@ static int dw_hdmi_setup(struct dw_hdmi *hdmi, struct drm_display_mode *mode) > > > > /* HDMI Initialization Step E - Configure audio */ > > hdmi_clk_regenerator_update_pixel_clock(hdmi); > > - hdmi_enable_audio_clk(hdmi, true); > > + dw_hdmi_audio_restore(hdmi); > > } > > > > /* not for DVI mode */ > > >