Received: by 10.223.185.116 with SMTP id b49csp511927wrg; Fri, 16 Feb 2018 02:45:18 -0800 (PST) X-Google-Smtp-Source: AH8x225ReuWVb6SOx7EDp0yYi+lROS8/Z03zX3btxO5sX1vqydStRbSqvChPDU7pkSWRy+Jbid2M X-Received: by 10.101.100.213 with SMTP id t21mr4803906pgv.19.1518777918862; Fri, 16 Feb 2018 02:45:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518777918; cv=none; d=google.com; s=arc-20160816; b=zd3c1wkynvOenlEUstXedieSZuxiQrrQ+A4C32GwSbvfi2laPcyW1W/tAn5Yg8r8WW az9r/05ZoBn7JJtpfoBrzeai4csC2R4lGLr0oftD/FuUx8Wn8+Z7CA4ETOyM3VyHBg12 4TQPNvVYKWSbZ7CpQHFjMVihcXKXsy3cv4qFlVvUCDrFFSpWHXCCryrErsS+oeaA+mKt JWqriDXp0PYyiaR4ZHf7zCiLrasSdmmf8GpeADuICY+NfFGWN2ppNjCzWYsGfYiXynyd BVT2q5ZjPjSUw6XaeiPdeD2XeW3J9Gc5moskiP3LtWytunYRmFaxOUk3viKvmswF7zgv oXWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=jeVZY4Qihdy1U9bZrWz6P18df2rTGOLpGcO+Z9owADE=; b=ZrVYN/rWwCqkvF84RONMfdnk6wXvrO8OD3SvkHTAIoqTG0xFR+dqvPzEOdW+AUxDwD g6JyGyGoPPgvgLcT/poo64wBg2rK3U49e5cquhotFs/caUm5V7XYvrw2cZ7fNPlwAw3D o+UheZ4PzePSlFfUsEdG7yU0C/EKd/3REgPxtzvjRpJzS0ki8xikH2tDDfEp/1sgIBKg 3doCHjwxZWm21RNMuyktGBdTLQ0VK7r/bWL+744ZXoMjUgGbdj9cxBHtZ8YC3tfdHs2I 6YHu1WcThpJPcjjIvXtKXodE18yO8ImuL2blQRWtvOItoRMC23gKU2nNFZHlqYEbnsDM igUQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b84si4115602pfj.183.2018.02.16.02.45.04; Fri, 16 Feb 2018 02:45:18 -0800 (PST) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1427190AbeBORSn (ORCPT + 99 others); Thu, 15 Feb 2018 12:18:43 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:57638 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422811AbeBOPgD (ORCPT ); Thu, 15 Feb 2018 10:36:03 -0500 Received: from localhost (LFbn-1-12258-90.w90-92.abo.wanadoo.fr [90.92.71.90]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 2F86A1155; Thu, 15 Feb 2018 15:36:03 +0000 (UTC) From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, John Keeping , Mark Brown Subject: [PATCH 4.14 143/195] ASoC: rockchip: i2s: fix playback after runtime resume Date: Thu, 15 Feb 2018 16:17:14 +0100 Message-Id: <20180215151712.961615588@linuxfoundation.org> X-Mailer: git-send-email 2.16.1 In-Reply-To: <20180215151705.738773577@linuxfoundation.org> References: <20180215151705.738773577@linuxfoundation.org> User-Agent: quilt/0.65 MIME-Version: 1.0 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 4.14-stable review patch. If anyone has any objections, please let me know. ------------------ From: John Keeping commit c66234cfedfc3e6e3b62563a5f2c1562be09a35d upstream. When restoring registers during runtime resume, we must not write to I2S_TXDR which is the transmit FIFO as this queues up a sample to be output and pushes all of the output channels down by one. This can be demonstrated with the speaker-test utility: for i in a b c; do speaker-test -c 2 -s 1; done which should play a test through the left speaker three times but if the I2S hardware starts runtime suspended the first sample will be played through the right speaker. Fix this by marking I2S_TXDR as volatile (which also requires marking it as readble, even though it technically isn't). This seems to be the most robust fix, the alternative of giving I2S_TXDR a default value is more fragile since it does not prevent regcache writing to the register in all circumstances. While here, also fix the configuration of I2S_RXDR and I2S_FIFOLR; these are not writable so they do not suffer from the same problem as I2S_TXDR but reading from I2S_RXDR does suffer from a similar problem. Fixes: f0447f6cbb20 ("ASoC: rockchip: i2s: restore register during runtime_suspend/resume cycle", 2016-09-07) Signed-off-by: John Keeping Signed-off-by: Mark Brown Signed-off-by: Greg Kroah-Hartman --- sound/soc/rockchip/rockchip_i2s.c | 6 ++++++ 1 file changed, 6 insertions(+) --- a/sound/soc/rockchip/rockchip_i2s.c +++ b/sound/soc/rockchip/rockchip_i2s.c @@ -504,6 +504,7 @@ static bool rockchip_i2s_rd_reg(struct d case I2S_INTCR: case I2S_XFER: case I2S_CLR: + case I2S_TXDR: case I2S_RXDR: case I2S_FIFOLR: case I2S_INTSR: @@ -518,6 +519,9 @@ static bool rockchip_i2s_volatile_reg(st switch (reg) { case I2S_INTSR: case I2S_CLR: + case I2S_FIFOLR: + case I2S_TXDR: + case I2S_RXDR: return true; default: return false; @@ -527,6 +531,8 @@ static bool rockchip_i2s_volatile_reg(st static bool rockchip_i2s_precious_reg(struct device *dev, unsigned int reg) { switch (reg) { + case I2S_RXDR: + return true; default: return false; }