Received: by 10.213.65.68 with SMTP id h4csp1194438imn; Mon, 26 Mar 2018 02:45:49 -0700 (PDT) X-Google-Smtp-Source: AG47ELvSxsKWVl8rSWvuVUAZRIVFBJDI5ezktoZaalFvFYS7LP7VdJuFLk/+nUXMnT3TtHKgrofE X-Received: by 10.98.50.130 with SMTP id y124mr32498653pfy.147.1522057549204; Mon, 26 Mar 2018 02:45:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522057549; cv=none; d=google.com; s=arc-20160816; b=IlGeFBRQtnaJI+Tjyohn8QW2HW5WallTgBexoW/2znl16mkmpjeJsI9cqyKsVAEztK dD1OW15GkyrCm0n7gNf46y4bH4EyNNp6IZwU9i9IbwGW2RSC5/3z4qwMA8btJmtzTmpI Me50H1xTvy+FfN0UBFvRvRVXxB8YZcmITZOr9nyNm4AQCIOQS64RARlqEm5WrCPangLE 8byZyKO1nzdSRx/+L1Qu7mS4nffV6/oFHeJu3s+r9nyMuv+bo07q/N1vN/8G4Iw9bS/S KER4h/Zahq7lkye4vFQyx+NBB3GkxipAhqScbfRtNUF8Qys+dQnx4f10tVJcm5U/fRXP PWUQ== 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 :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature:arc-authentication-results; bh=2Z4sZXyssqNSW2l66Pj3o4EjXpjnzue5xt1JW0LH17U=; b=HsYmvWCgjmiIVqRp8dBpCEnBKaudmDu2L2masyu/T7er60s7MXTJbwPRBFb/suTeUJ v8xTxzWmIngZcm6Kbh8P/aEWhQyuAzHcvi+LUvVaM0RB0flwnqjcQtTo2kCQJgp/WxgZ ZrW3hLusyDd+apT3BwFbIyE2kZ96VWJpDbKCaJsnA5PDcFSJZ7/WvDk2RC2zhXTpLugb p/6kA1ZJSAL1HQL/J1BGaoQ7OIVN7V6dxXKPtJHpBf8X3Njgpj5nkIru1TNfu9Cj+UnR nx4VsPZI5u9NQka3n7AUg+Oars0dy834we6w6CeW/HArBVNNlqp/6LBHITlmxKAsepN6 hjKQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=WI9s6EcH; 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 13-v6si14273781plb.515.2018.03.26.02.45.34; Mon, 26 Mar 2018 02:45:49 -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=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=WI9s6EcH; 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 S1751896AbeCZJoD (ORCPT + 99 others); Mon, 26 Mar 2018 05:44:03 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:54440 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751765AbeCZJoC (ORCPT ); Mon, 26 Mar 2018 05:44:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=Content-Transfer-Encoding: Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To: From:Date:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=2Z4sZXyssqNSW2l66Pj3o4EjXpjnzue5xt1JW0LH17U=; b=WI9s6EcHLFli7Ffub/rFcSnew ct+bixz+Pzt42CtnDoYB7uJRGWm5gmxhS+Jm547/VOtvXKvYHq5DTeoRGVR/ZJ+WrVl3e3GxzzSJP fRbJxUvfn2jfHfyC1X6rZE+vI8yyyMlBU0JYQgG70fGeV1yOFflQ0UUpigHiUKU79JSlPAlli8Ked NiIBNCauwCGmNdqx63TRUY6xgkiDaP759fO3rhCe+Azt/LmQjrK0ETIkQoqRc5Ps/V3xMtMCvT3T0 g/rdqQZQa7MItpQg1CluBbJdydTNb8MkT2TZQXpUQVZSlAXdOt2PrOJkmJwUW8EuUjw/MLo3wvsF3 S4Ml683uA==; Received: from [179.95.60.72] (helo=vento.lan) by bombadil.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1f0OfX-0004ZU-4v; Mon, 26 Mar 2018 09:43:59 +0000 Date: Mon, 26 Mar 2018 06:43:53 -0300 From: Mauro Carvalho Chehab To: Nasser Afshin Cc: p.zabel@pengutronix.de, sakari.ailus@linux.intel.com, hans.verkuil@cisco.com, bparrot@ti.com, garsilva@embeddedor.com, linux-media@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] media: i2c: tvp5150: fix color burst lock instability on some hardware Message-ID: <20180326064353.187f752c@vento.lan> In-Reply-To: <20180325225633.5899-1-Afshin.Nasser@gmail.com> References: <20180325225633.5899-1-Afshin.Nasser@gmail.com> X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Nasser, Em Mon, 26 Mar 2018 03:26:33 +0430 Nasser Afshin escreveu: > According to the datasheet, INTREQ/GPCL/VBLK should have a pull-up/down > resistor if it's been disabled. On hardware that does not have such > resistor, we should use the default output enable value. > This prevents the color burst lock instability problem. If this is hardware-dependent, you should instead store it at OF (for SoC) or pass via platform_data (for PCI/USB devices). > > Signed-off-by: Nasser Afshin > --- > drivers/media/i2c/tvp5150.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/drivers/media/i2c/tvp5150.c b/drivers/media/i2c/tvp5150.c > index 2476d812f669..0e9713814816 100644 > --- a/drivers/media/i2c/tvp5150.c > +++ b/drivers/media/i2c/tvp5150.c > @@ -328,7 +328,7 @@ static const struct i2c_reg_value tvp5150_init_default[] = { > TVP5150_OP_MODE_CTL,0x00 > }, > { /* 0x03 */ > - TVP5150_MISC_CTL,0x01 > + TVP5150_MISC_CTL,0x21 > }, > { /* 0x06 */ > TVP5150_COLOR_KIL_THSH_CTL,0x10 > @@ -1072,7 +1072,8 @@ static int tvp5150_s_stream(struct v4l2_subdev *sd, int enable) > * Enable the YCbCr and clock outputs. In discrete sync mode > * (non-BT.656) additionally enable the the sync outputs. > */ > - val |= TVP5150_MISC_CTL_YCBCR_OE | TVP5150_MISC_CTL_CLOCK_OE; > + val |= TVP5150_MISC_CTL_YCBCR_OE | TVP5150_MISC_CTL_CLOCK_OE | > + TVP5150_MISC_CTL_INTREQ_OE; > if (decoder->mbus_type == V4L2_MBUS_PARALLEL) > val |= TVP5150_MISC_CTL_SYNC_OE; > } Thanks, Mauro