Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp243785ybi; Wed, 29 May 2019 20:31:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqxLXbTRgygyE+5RcAYwjXpPVvIK+0FPtMonPr1RmozHIsKs1X4or5yp0uwgKzyojwUYZKiN X-Received: by 2002:a17:90a:dd45:: with SMTP id u5mr1309476pjv.109.1559187067609; Wed, 29 May 2019 20:31:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559187067; cv=none; d=google.com; s=arc-20160816; b=cVLy9H2ISZrMadR+20Z4sslA7/qkaDGUVaiht1gu07AUnxomTfN4IXuu9leGmxYVqZ k6+2ICypj5bTQPPyrGLeHlDfZvvFdnaFujkQXVFOoB1XMS9pu+PwHk1ObGWAuoNkIHv5 dE9adYh8ozYLC4aMdom9PELQfSX4HPG1T5HaG2AawPn4HDx3UxfVK0tdGG8B+Vy/Zg8m CU1JkhmyCWCd+p388h9hDYgxlHEB7rGdjNwO65JMaCKBRgA4fNL+ub2jcJafz431hD/V lfjfEaPlPux09xtx2M8ynjQDT+Q+NIeTcCSVEpVBmILkhacJiEb5VWsbc2lf/ADXl5vb q1Lg== 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 :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=dDDl0qcZe+njU4P/oLPfr9uqKhxsZqvJnqfgMRSOziY=; b=kMaoGGUnj9DIOV7VIDvjLT+uxQ+zGcxThQ5+9h/W/LxrqwtVSo+Kp1RSYtt44H5nFS /TeNKw+9s2jSRyYNnurE8YhvaYHBIwHAFFxT5UOqpshQBHFX4S8WozaGLwxRc3vroH3C duTi/VTcLmfRkDe1i/1TwI3CG4m3I739w/ZgMRZywvLvYy59M61WGkxGTcwJu2+g1Pj7 kluxvjdd9QwkwP3cnpQ5KaOXZrMw0VHxNm8JIIqpgPddgrKKviZ6mRiARKNpWVeXte+1 93FtKSSuNoaXc9P3MqvyjDxNO/o2Z24uKiJjPBoeimYtSFhxL6y4uVi69RUH+kv+Xrz/ Ligg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=aF36lg9C; 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 k3si1784490pls.146.2019.05.29.20.30.51; Wed, 29 May 2019 20:31:07 -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=@kernel.org header.s=default header.b=aF36lg9C; 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 S2388173AbfE3D2a (ORCPT + 99 others); Wed, 29 May 2019 23:28:30 -0400 Received: from mail.kernel.org ([198.145.29.99]:57440 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728696AbfE3DT6 (ORCPT ); Wed, 29 May 2019 23:19:58 -0400 Received: from localhost (ip67-88-213-2.z213-88-67.customer.algx.net [67.88.213.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id F0E6E248F9; Thu, 30 May 2019 03:19:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559186398; bh=kDay58/x01apOMo6Iefun5Hh8aXIldRq8oagKmf/Tj8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=aF36lg9C53Sh/9j4VsuV5v4z+8JVTO3cJPWFu0ArolXO2EmNn4QJb4Vnjv9sijy+7 oduNsQFBtHLUnQubXC3uFQYvzhGDRz3q6q4TUA16ot1hiui6fjmFfLnnRChnn0qyWs UmMsqFRgtf/GkLFm3vu1Z3bEwCOmPWJA/59C/Wzo= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, James Hutchinson , Antti Palosaari , Sean Young , Mauro Carvalho Chehab , Sasha Levin Subject: [PATCH 4.14 178/193] media: m88ds3103: serialize reset messages in m88ds3103_set_frontend Date: Wed, 29 May 2019 20:07:12 -0700 Message-Id: <20190530030512.425712303@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190530030446.953835040@linuxfoundation.org> References: <20190530030446.953835040@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [ Upstream commit 981fbe3da20a6f35f17977453bce7dfc1664d74f ] Ref: https://bugzilla.kernel.org/show_bug.cgi?id=199323 Users are experiencing problems with the DVBSky S960/S960C USB devices since the following commit: 9d659ae: ("locking/mutex: Add lock handoff to avoid starvation") The device malfunctions after running for an indeterminable period of time, and the problem can only be cleared by rebooting the machine. It is possible to encourage the problem to surface by blocking the signal to the LNB. Further debugging revealed the cause of the problem. In the following capture: - thread #1325 is running m88ds3103_set_frontend - thread #42 is running ts2020_stat_work a> [1325] usb 1-1: dvb_usb_v2_generic_io: >>> 08 68 02 07 80 [1325] usb 1-1: dvb_usb_v2_generic_io: <<< 08 [42] usb 1-1: dvb_usb_v2_generic_io: >>> 09 01 01 68 3f [42] usb 1-1: dvb_usb_v2_generic_io: <<< 08 ff [42] usb 1-1: dvb_usb_v2_generic_io: >>> 08 68 02 03 11 [42] usb 1-1: dvb_usb_v2_generic_io: <<< 07 [42] usb 1-1: dvb_usb_v2_generic_io: >>> 09 01 01 60 3d [42] usb 1-1: dvb_usb_v2_generic_io: <<< 07 ff b> [1325] usb 1-1: dvb_usb_v2_generic_io: >>> 08 68 02 07 00 [1325] usb 1-1: dvb_usb_v2_generic_io: <<< 07 [42] usb 1-1: dvb_usb_v2_generic_io: >>> 08 68 02 03 11 [42] usb 1-1: dvb_usb_v2_generic_io: <<< 07 [42] usb 1-1: dvb_usb_v2_generic_io: >>> 09 01 01 60 21 [42] usb 1-1: dvb_usb_v2_generic_io: <<< 07 ff [42] usb 1-1: dvb_usb_v2_generic_io: >>> 08 68 02 03 11 [42] usb 1-1: dvb_usb_v2_generic_io: <<< 07 [42] usb 1-1: dvb_usb_v2_generic_io: >>> 09 01 01 60 66 [42] usb 1-1: dvb_usb_v2_generic_io: <<< 07 ff [1325] usb 1-1: dvb_usb_v2_generic_io: >>> 08 68 02 03 11 [1325] usb 1-1: dvb_usb_v2_generic_io: <<< 07 [1325] usb 1-1: dvb_usb_v2_generic_io: >>> 08 60 02 10 0b [1325] usb 1-1: dvb_usb_v2_generic_io: <<< 07 Two i2c messages are sent to perform a reset in m88ds3103_set_frontend: a. 0x07, 0x80 b. 0x07, 0x00 However, as shown in the capture, the regmap mutex is being handed over to another thread (ts2020_stat_work) in between these two messages. >From here, the device responds to every i2c message with an 07 message, and will only return to normal operation following a power cycle. Use regmap_multi_reg_write to group the two reset messages, ensuring both are processed before the regmap mutex is unlocked. Signed-off-by: James Hutchinson Reviewed-by: Antti Palosaari Signed-off-by: Sean Young Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Sasha Levin --- drivers/media/dvb-frontends/m88ds3103.c | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/media/dvb-frontends/m88ds3103.c b/drivers/media/dvb-frontends/m88ds3103.c index 65d157fe76d19..b4bd1af34745d 100644 --- a/drivers/media/dvb-frontends/m88ds3103.c +++ b/drivers/media/dvb-frontends/m88ds3103.c @@ -309,6 +309,9 @@ static int m88ds3103_set_frontend(struct dvb_frontend *fe) u16 u16tmp; u32 tuner_frequency_khz, target_mclk; s32 s32tmp; + static const struct reg_sequence reset_buf[] = { + {0x07, 0x80}, {0x07, 0x00} + }; dev_dbg(&client->dev, "delivery_system=%d modulation=%d frequency=%u symbol_rate=%d inversion=%d pilot=%d rolloff=%d\n", @@ -321,11 +324,7 @@ static int m88ds3103_set_frontend(struct dvb_frontend *fe) } /* reset */ - ret = regmap_write(dev->regmap, 0x07, 0x80); - if (ret) - goto err; - - ret = regmap_write(dev->regmap, 0x07, 0x00); + ret = regmap_multi_reg_write(dev->regmap, reset_buf, 2); if (ret) goto err; -- 2.20.1