From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A8806C2D0DB for ; Fri, 31 Jan 2020 19:38:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8603120707 for ; Fri, 31 Jan 2020 19:38:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726154AbgAaTil (ORCPT ); Fri, 31 Jan 2020 14:38:41 -0500 Received: from bhuna.collabora.co.uk ([46.235.227.227]:59674 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726001AbgAaTik (ORCPT ); Fri, 31 Jan 2020 14:38:40 -0500 Received: from [IPv6:2003:cb:8716:6a00:1956:2e0:5d2c:ff7c] (p200300CB87166A00195602E05D2CFF7C.dip0.t-ipconnect.de [IPv6:2003:cb:8716:6a00:1956:2e0:5d2c:ff7c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: dafna) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id 4D99026068C; Fri, 31 Jan 2020 19:38:37 +0000 (GMT) Subject: Re: [PATCH v8 05/14] media: rkisp1: add Rockchip ISP1 subdev driver To: Sakari Ailus , Helen Koike Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org, eddie.cai.linux@gmail.com, mchehab@kernel.org, heiko@sntech.de, jacob2.chen@rock-chips.com, jeffy.chen@rock-chips.com, zyc@rock-chips.com, linux-kernel@vger.kernel.org, tfiga@chromium.org, hans.verkuil@cisco.com, laurent.pinchart@ideasonboard.com, kernel@collabora.com, ezequiel@collabora.com, linux-media@vger.kernel.org, linux-arm-kernel@lists.infradead.org, zhengsq@rock-chips.com, Jacob Chen , Allon Huang , Dafna Hirschfeld References: <20190730184256.30338-1-helen.koike@collabora.com> <20190730184256.30338-6-helen.koike@collabora.com> <20190808091406.GQ21370@paasikivi.fi.intel.com> <20190815082422.GM6133@paasikivi.fi.intel.com> <20190815131748.GS6133@paasikivi.fi.intel.com> From: Dafna Hirschfeld Message-ID: <78856358-1afd-31a7-86dd-22f7d6d7fb05@collabora.com> Date: Fri, 31 Jan 2020 20:38:34 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <20190815131748.GS6133@paasikivi.fi.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Hi, I (Dafna Hirschfeld) will work in following months with Helen Koike to fix the issues in the TODO file of this driver: drivers/staging/media/rkisp1/TODO On 15.08.19 15:17, Sakari Ailus wrote: > On Thu, Aug 15, 2019 at 11:24:22AM +0300, Sakari Ailus wrote: >> Hi Helen, >> >> On Wed, Aug 14, 2019 at 09:58:05PM -0300, Helen Koike wrote: >> >> ... >> >>>>> +static int rkisp1_isp_sd_set_fmt(struct v4l2_subdev *sd, >>>>> + struct v4l2_subdev_pad_config *cfg, >>>>> + struct v4l2_subdev_format *fmt) >>>>> +{ >>>>> + struct rkisp1_device *isp_dev = sd_to_isp_dev(sd); >>>>> + struct rkisp1_isp_subdev *isp_sd = &isp_dev->isp_sdev; >>>>> + struct v4l2_mbus_framefmt *mf = &fmt->format; >>>>> + >>>> >>>> Note that for sub-device nodes, the driver is itself responsible for >>>> serialising the access to its data structures. >>> >>> But looking at subdev_do_ioctl_lock(), it seems that it serializes the >>> ioctl calls for subdevs, no? Or I'm misunderstanding something (which is >>> most probably) ? >> >> Good question. I had missed this change --- subdev_do_ioctl_lock() is >> relatively new. But setting that lock is still not possible as the struct 'the struct' - do you mean the 'vdev' struct allocated in 'v4l2_device_register_subdev_nodes' ? >> is allocated in the framework and the device is registered before the >> driver gets hold of it. It's a good idea to provide the same serialisation >> for subdevs as well. >> >> I'll get back to this later. > > The main reason is actually that these ops are also called through the > sub-device kAPI, not only through the uAPI, and the locks are only taken > through the calls via uAPI. actually it seems that although 'subdev_do_ioctl_lock' exit, I wonder if any subdevice uses that vdev->lock in subdev_do_ioctl_lock. It is not initialized in v4l2_device_register_subdev_nodes where the vdev is allocated and I wonder if any subdevice actually initialize it somewhere else. For example it is null in this driver and in vimc. > > So adding the locks to uAPI calls alone would not address the issue. What I can do is add a mutex to every struct of a subdevice and lock it at the beginning of each subdevice operation. Is this an acceptable solution? Thanks, Dafna >