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=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED 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 496ACC433E0 for ; Wed, 10 Jun 2020 19:33:43 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 1B4D12072E for ; Wed, 10 Jun 2020 19:33:43 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="VSnAaWsH"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="fL/P90Lf" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1B4D12072E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=chromium.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=UdOIVMXRdTtvNoaGUt640p+qG48GvJGdCOeoIbnTIcQ=; b=VSnAaWsHqm5B4d oGNLzNsat+UaVswQV/w0dm/nBZETipmQdlobZQMLD7d/fXi0BVHMBWj3069bsXg3/2SxpY1kWzxvN qoh/2+mlTRAZeDhxdSojlls5X/767Qxw4LhbsmTwsEjEXjdfEX9IMU5x4GCosifAvcvCVFsCMsEE6 erv2M2sKYjhrqWtzu5YWAPT07I+qfxY7CA8lEatmQ50SmPzjMO1M/Y6OWCouvItMAiB57vXwoXXnX GjlXOCzxvhjnXeXjr/oaJInGShK4LIRlhNselWJsQNGpZO8+jcHjZze9yzPM1T2oY+p6iuMAYE7Qc M5ShU/gmM8kD+34k0U8w==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jj6Tm-0004Mw-HP; Wed, 10 Jun 2020 19:33:42 +0000 Received: from mail-lj1-x243.google.com ([2a00:1450:4864:20::243]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jj6Ti-0004MV-R3 for linux-arm-kernel@lists.infradead.org; Wed, 10 Jun 2020 19:33:40 +0000 Received: by mail-lj1-x243.google.com with SMTP id z9so3953222ljh.13 for ; Wed, 10 Jun 2020 12:33:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qqYiZ6Y6itIrxnPxpSfJPzKeOxIw44n8uIkZaVxE90c=; b=fL/P90LfHU2hZvRP7iyIKCFTn9IBz4A7+xlXDwNOH2xsnwUUftY5YRDCrjt+xCisu3 jP26qKwO7lNPFaujkpx5nsxM1vL5CNqj/J743n2KZwO78uUi6SQTBobQmgFzn1NW4EQn vYcVhGWb0B+2Ecll8PhdZcHqUZ/A/o04wmYIg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qqYiZ6Y6itIrxnPxpSfJPzKeOxIw44n8uIkZaVxE90c=; b=Exsr1x2OuJG2L8dnP/f2JEwd8jZviLbxGG4p9H/jUlMPjjZ0UBZq9ebCls14/z1czc KPFhfjfO8DpcNuxtQek1/wQiXg4uYQouVFjhr+qq9hd1nZy5X7jx7yeacSV8T1tubA0V shRhZ5TPYzIMrUZx5n2mDrAB3Uq2Ip0lbfFw54+5qW8+5l+/SEqFgsXaeDniPMcBZf1B 56+o7EzrKL45KlzJflNF+6NByEJxYri9LxW0+NKeiokJyc5x1Pc162PQ+kHRxXhjRoN7 rfGDwBi11RhCZbx+66oM16GVS23T8ZYp8zsXBgsbcFhOGuhGGSOb8EMifZUa6k+73oLN y1RQ== X-Gm-Message-State: AOAM533YUfXKqVNr5d4GSTmSAVxzZ5ucs+xioEn9KaP86jk4D7SQH5m7 iY9IQwNhnqEWAGPUjxKZR/0rSMF0eu0C+w== X-Google-Smtp-Source: ABdhPJxY4WR5vxdIU5uw1/zYqLiP3iFfCQFhWAL7ogk5Ak+/E1jxudAbAFSTbhHk9gIQ59eqL+41HA== X-Received: by 2002:a2e:7313:: with SMTP id o19mr2557934ljc.27.1591817615460; Wed, 10 Jun 2020 12:33:35 -0700 (PDT) Received: from mail-lf1-f44.google.com (mail-lf1-f44.google.com. [209.85.167.44]) by smtp.gmail.com with ESMTPSA id h26sm160329lji.42.2020.06.10.12.33.34 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 10 Jun 2020 12:33:35 -0700 (PDT) Received: by mail-lf1-f44.google.com with SMTP id e125so2165478lfd.1 for ; Wed, 10 Jun 2020 12:33:34 -0700 (PDT) X-Received: by 2002:a5d:6750:: with SMTP id l16mr5316439wrw.295.1591817201284; Wed, 10 Jun 2020 12:26:41 -0700 (PDT) MIME-Version: 1.0 References: <20191204124732.10932-1-Jerry-Ch.chen@mediatek.com> <20191204124732.10932-2-Jerry-Ch.chen@mediatek.com> <20200521171101.GA243874@chromium.org> <20200610190356.GJ201868@chromium.org> In-Reply-To: From: Tomasz Figa Date: Wed, 10 Jun 2020 21:26:28 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC PATCH V4 1/4] media: v4l2-mem2mem: add v4l2_m2m_suspend, v4l2_m2m_resume To: Ezequiel Garcia X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200610_123338_893819_0C8554F1 X-CRM114-Status: GOOD ( 37.09 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-devicetree , =?UTF-8?B?U2VhbiBDaGVuZyAo6YSt5piH5byYKQ==?= , Laurent Pinchart , =?UTF-8?B?UnlubiBXdSAo5ZCz6IKy5oGpKQ==?= , zwisler@chromium.org, srv_heupstream , Jerry-ch Chen , Jerry-ch Chen , Hans Verkuil , =?UTF-8?B?SnVuZ28gTGluICjmnpfmmI7kv4op?= , Sj Huang , yuzhao@chromium.org, "moderated list:ARM/Mediatek SoC support" , Pi-Hsun Shih , =?UTF-8?B?RnJlZGVyaWMgQ2hlbiAo6Zmz5L+K5YWDKQ==?= , Matthias Brugger , =?UTF-8?B?Q2hyaXN0aWUgWXUgKOa4uOmbheaDoCk=?= , Mauro Carvalho Chehab , "list@263.net:IOMMU DRIVERS , Joerg Roedel , " , Linux Media Mailing List Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Jun 10, 2020 at 9:14 PM Ezequiel Garcia wrote: > > On Wed, 10 Jun 2020 at 16:03, Tomasz Figa wrote: > > > > On Wed, Jun 10, 2020 at 03:52:39PM -0300, Ezequiel Garcia wrote: > > > Hi everyone, > > > > > > Thanks for the patch. > > > > > > On Wed, 10 Jun 2020 at 07:33, Tomasz Figa wrote: > > > > > > > > On Wed, Jun 10, 2020 at 12:29 PM Hans Verkuil wrote: > > > > > > > > > > On 21/05/2020 19:11, Tomasz Figa wrote: > > > > > > Hi Jerry, > > > > > > > > > > > > On Wed, Dec 04, 2019 at 08:47:29PM +0800, Jerry-ch Chen wrote: > > > > > >> From: Pi-Hsun Shih > > > > > >> > > > > > >> Add two functions that can be used to stop new jobs from being queued / > > > > > >> continue running queued job. This can be used while a driver using m2m > > > > > >> helper is going to suspend / wake up from resume, and can ensure that > > > > > >> there's no job running in suspend process. > > [snip] > > > > > > > > > > I assume this will be part of a future patch series that calls these new functions? > > > > > > > > The mtk-jpeg encoder series depends on this patch as well, so I guess > > > > it would go together with whichever is ready first. > > > > > > > > I would also envision someone changing the other existing drivers to > > > > use the helpers, as I'm pretty much sure some of them don't handle > > > > suspend/resume correctly. > > > > > > > > > > This indeed looks very good. If I understood the issue properly, > > > the change would be useful for both stateless (e.g. hantro, et al) > > > and stateful (e.g. coda) codecs. > > > > > > Hantro uses pm_runtime_force_suspend, and I believe that > > > could is enough for proper suspend/resume operation. > > > > Unfortunately, no. :( > > > > If the decoder is already decoding a frame, that would forcefully power > > off the hardware and possibly even cause a system lockup if we are > > unlucky to gate a clock in the middle of a bus transaction. > > > > pm_runtime_force_suspend calls pm_runtime_disable, which > says: > > """ > Increment power.disable_depth for the device and if it was zero previously, > cancel all pending runtime PM requests for the device and wait for all > operations in progress to complete. > """ > > Doesn't this mean it waits for the current job (if there is one) and > prevents any new jobs to be issued? > I'd love if the PM runtime subsystem handled job management of all the driver subsystems automatically, but at the moment it's not aware of any jobs. :) The description says as much as it says - it stops any internal jobs of the PM subsystem - i.e. asynchronous suspend/resume requests. It doesn't have any awareness of V4L2 M2M jobs. > > I just inspected the code now and actually found one more bug in its > > power management handling. device_run() calls clk_bulk_enable() before > > pm_runtime_get_sync(), but only the latter is guaranteed to actually > > power on the relevant power domains, so we end up clocking unpowered > > hardware. > > > > How about we just move clk_enable/disable to runtime PM? > > Since we use autosuspend delay, it theoretically has > some impact, which is why I was refraining from doing so. > > I can't decide if this impact would be marginal or significant. > I'd also refrain from doing this. Clock gating corresponds to the bigger part of the power savings from runtime power management, since it stops the dynamic power consumption and only leaves the static leakage. That said, the Hantro IP blocks have some internal clock gating as well, so it might not be as pronounced, depending on the custom vendor integration logic surrounding the Hantro hardware. Actually even if autosuspend is not used, the runtime PM subsystem has some internal back-off mechanism based on measured power on and power off latencies. The driver should call pm_runtime_get_sync() first and then enable any necessary clocks. I can see that currently inside the resume callback we have some hardware accesses. If those really need to be there, they should be surrounded with appropriate clock enable and clock disable calls. > > > > > > I'm not seeing any code in CODA to handle this, so not sure > > > how it's handling suspend/resume. > > > > > > Maybe we can have CODA as the first user, given it's a well-maintained > > > driver and should be fairly easy to test. > > > > I remember checking a number of drivers using the m2m helpers randomly > > and none of them implemented suspend/resume correctly. I suppose that > > was not discovered because normally the userspace itself would stop the > > operation before the system is suspended, although it's not an API > > guarantee. > > > > Indeed. Do you have any recomendations for how we could > test this case to make sure we are handling it correctly? I'd say that a simple offscreen command line gstreamer/ffmpeg decode with suspend/resume loop in another session should be able to trigger some issues. Best regards, Tomasz _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel