Received: by 2002:a17:90a:202a:0:0:0:0 with SMTP id n39csp3591364pjc; Sun, 2 Jun 2019 13:50:59 -0700 (PDT) X-Google-Smtp-Source: APXvYqzqF3mouZ4Le0pw1RCQlXL4ivWpFFIuq7/p+HF/avrsdOaykCHknaCPgs/FiAb7OBUKCCT5 X-Received: by 2002:a63:d70b:: with SMTP id d11mr24191589pgg.178.1559508658452; Sun, 02 Jun 2019 13:50:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559508658; cv=none; d=google.com; s=arc-20160816; b=GJ95zKBwlXmO2G9GgRr8qFLagI3y6bQLRLss2LBEYpCTe+nKDAxu0CxRNGf/gvql9n J8rLFufO5f4DWulkK1RRnj8R41rJIn99bg+mcvwTqSfBXl/SVsAjyA4zNvtlGstSs9Z4 +d1ryanuvYh0fKp+8w2yuz6tOphLCT5TFRRelCcHRLzRbBg5FpAcls0XwFoxGyI1GUA1 9BgvEpR1fIxG0vLgFvsRS7llyyKsUW5HQgDT0ZMhDMMAzU1JrDSTNpitXSuXyyME44Rq gECJP4hvTb6fjAIY/VkRqvkeAHi6eIC3MKG2UOoLWB3Wr7RTXgiCPm+RhDj4G3j/J1Pc 0f6Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=ZVmeLqIDTAttNKYvBRy1xG+2qPCArJ452NSP/iZIQz8=; b=SZlFlPNnedLgNankK6Ra/QatxHYiUiF0HW50rGdnCTSg4Gqx2bQdL0cAY0iGIck1nq F+upzm2TB/SD+AGmWxnXJdMkuT1m3+c0+Gz/SlYT+u9SHpK1B+ReJk9UdAIDX+v6e1PB 9ln/d7ySDwS1LqUxmAYgnkStmdhedmwobyWTYglgsJBD/Niyb7Sd+iHyLE2+UXIzzpBA hEp4dn7SB3vdqkuL4/MZbYyORbTDDN/LNQVpnAWPQTEbTFPgrHbuKUo0v8JJdw5Oysdj 0rzPUpptAMIeoLcSjCq8PJNzcG6u/LzpDm99dJz/B9c3stcrEcQlnKH15/QodR1qVIZ7 NL5Q== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=iki.fi Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s20si15989068pgj.63.2019.06.02.13.48.55; Sun, 02 Jun 2019 13:50:58 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=iki.fi Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726824AbfFBUhM (ORCPT + 99 others); Sun, 2 Jun 2019 16:37:12 -0400 Received: from retiisi.org.uk ([95.216.213.190]:59078 "EHLO hillosipuli.retiisi.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726485AbfFBUhL (ORCPT ); Sun, 2 Jun 2019 16:37:11 -0400 Received: from valkosipuli.localdomain (valkosipuli.retiisi.org.uk [IPv6:2a01:4f9:c010:4572::80:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hillosipuli.retiisi.org.uk (Postfix) with ESMTPS id 77750634C7B; Sun, 2 Jun 2019 23:36:57 +0300 (EEST) Received: from sailus by valkosipuli.localdomain with local (Exim 4.89) (envelope-from ) id 1hXXDt-0000bk-Jh; Sun, 02 Jun 2019 23:36:57 +0300 Date: Sun, 2 Jun 2019 23:36:57 +0300 From: Sakari Ailus To: Janusz Krzysztofik Cc: Sakari Ailus , Mauro Carvalho Chehab , Hans Verkuil , linux-media@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH 4/5] media: ov6650: Fix frame scaling not reset on crop Message-ID: <20190602203657.jirbekewlh7tykmj@valkosipuli.retiisi.org.uk> References: <20190526204758.1904-1-jmkrzyszt@gmail.com> <1933971.yMpNBnsSgY@z50> <20190601223754.65soglqayxrblgzl@mara.localdomain> <11387277.ecJxfdHps5@z50> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11387277.ecJxfdHps5@z50> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Janusz, On Sun, Jun 02, 2019 at 11:58:23AM +0200, Janusz Krzysztofik wrote: > Hi Sakari, > > On Sunday, June 2, 2019 12:37:55 AM CEST Sakari Ailus wrote: > > > > ... I realised that the subtle effect of "media: > > ov6650: Register with asynchronous subdevice framework" is that the driver > > is now responsible for serialising the access to its own data structures > > now. > > Indeed, I must have been not thinking much while preparing it, only following > patterns from other implementations blindly, sorry. No worries. I missed it at the time, too... > > > And it doesn't do that. Could you submit a fix, please? It'd be good to > > get that to 5.2 through the fixes branch. > > How about dropping that V4L2_SUBDEV_FL_HAS_DEVNODE flag for now? I think that > will be the most safe approach for a quick fix. I'd then re-add it together > with proper locking in a separate patch later. What do yo think? Sure. Then we just re-introduce the flag when the driver is ready for that. -- Regards, Sakari Ailus