Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1298068pxj; Fri, 4 Jun 2021 10:39:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwMCrOYIkhpKmrO/Uuu+o3HPW9y372fKaw9MEAKXcdn9LKctWZN9Sn8Q4dQ4vwPZdCdAsHJ X-Received: by 2002:a17:906:b2c1:: with SMTP id cf1mr5195196ejb.544.1622828385769; Fri, 04 Jun 2021 10:39:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1622828385; cv=none; d=google.com; s=arc-20160816; b=Q35u7kAg56eWM8ZL2tRHWpBdr+++1bOx0Mn+YdnARvbqzKwKP7qjSLA3yHhbj5NdS/ XfLR4Exhwj4yfh55pC50sXzm+fNz8AtldQ4O7++rnm7gZs63O0aaJC8Tuv9aB8g5wkva JHN38+ScRFubwptX46cGJJrRLKs8iY+EzxmSksVEDmHOBpo/9V41SQBUH6YBZ93qsxZ2 +a8PlAeCLZDFVVjNsvN3mt+DHu6wcWl1Q0vHGy5PH9y9ChzN+DjQ63C9tH1m0/SDB+hC iiixAJWWOE/038nVlW9xwg3aOu/9bKYeKNlxn6NzkFIqgON1DisW/1QFC7LNBhSA4cgO vVAA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:organization:references:in-reply-to:date:cc:to:from :subject:message-id; bh=0GZLnwt61O/PTuB9NgS4R0gz41mgjLCzqBO/wDXzflI=; b=FC/43ifEHG7ji24MrWn1d86zuT9uX0I4eyBSXxYdiG11Tu8m21IawFbRJQ2UaPdYQC EaENQ0yxipjkQ1kZIQtvF4Zt5Z1d7rD0uALkcILdt3ylI/jrIY4F14p1VAl+XZm1CaL7 VloaEiYcdl8qfgpub9kh4biQWpOjpp3Sk5dz/oloXqSw1PX6EeX9yagMe2pMy4iHCnNw qoN/QllERKoHw859RaZ4nFk8O9seHZTuMJ7vRQAVh/x/zAjKrZpUNTWVtINhGTlyAx7P GLOBcnavQPMmR1pDg1k7QJNqk7KD+5LyD5MsM7qz83cn3oycxgpIYM9UPRUXOLc6JhV4 HSOw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k9si5350907edv.565.2021.06.04.10.39.22; Fri, 04 Jun 2021 10:39:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231177AbhFDRjD (ORCPT + 99 others); Fri, 4 Jun 2021 13:39:03 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:38096 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229690AbhFDRjD (ORCPT ); Fri, 4 Jun 2021 13:39:03 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: ezequiel) with ESMTPSA id 65E551F439E4 Message-ID: <943276000b13f51e0e746b4f29f2a28d7e435622.camel@collabora.com> Subject: Re: [PATCH v9 03/13] media: hantro: Use syscon instead of 'ctrl' register From: Ezequiel Garcia To: Lucas Stach , Benjamin Gaignard , p.zabel@pengutronix.de, mchehab@kernel.org, robh+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de, festevam@gmail.com, lee.jones@linaro.org, gregkh@linuxfoundation.org, mripard@kernel.org, paul.kocialkowski@bootlin.com, wens@csie.org, jernej.skrabec@siol.net, hverkuil-cisco@xs4all.nl, emil.l.velikov@gmail.com, "Peng Fan (OSS)" , Jacky Bai Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org, linux-imx@nxp.com, kernel@pengutronix.de, kernel@collabora.com, cphealy@gmail.com, linux-arm-kernel@lists.infradead.org, linux-media@vger.kernel.org Date: Fri, 04 Jun 2021 14:37:02 -0300 In-Reply-To: <72fef3d9f79194876f2035e996bb83f9f8b12902.camel@pengutronix.de> References: <20210407073534.376722-1-benjamin.gaignard@collabora.com> <20210407073534.376722-4-benjamin.gaignard@collabora.com> <7bcbb787d82f21d42563d8fb7e3c2e7d40123932.camel@pengutronix.de> <831a59b052df02e9860b9766e631a7ab6a37c46a.camel@collabora.com> <72fef3d9f79194876f2035e996bb83f9f8b12902.camel@pengutronix.de> Organization: Collabora Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.2-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Lucas, On Mon, 2021-05-17 at 12:52 +0200, Lucas Stach wrote: > Hi Ezequiel, > > Am Sonntag, dem 16.05.2021 um 19:40 -0300 schrieb Ezequiel Garcia: > > Hi Lucas, > > > > On Fri, 2021-04-16 at 12:54 +0200, Lucas Stach wrote: > > > Am Mittwoch, dem 07.04.2021 um 09:35 +0200 schrieb Benjamin Gaignard: > > > > In order to be able to share the control hardware block between > > > > VPUs use a syscon instead a ioremap it in the driver. > > > > To keep the compatibility with older DT if 'nxp,imx8mq-vpu-ctrl' > > > > phandle is not found look at 'ctrl' reg-name. > > > > With the method it becomes useless to provide a list of register > > > > names so remove it. > > > > > > Sorry for putting a spoke in the wheel after many iterations of the > > > series. > > > > > > We just discussed a way forward on how to handle the clocks and resets > > > provided by the blkctl block on i.MX8MM and later and it seems there is > > > a consensus on trying to provide virtual power domains from a blkctl > > > driver, controlling clocks and resets for the devices in the power > > > domain. I would like to avoid introducing yet another way of handling > > > the blkctl and thus would like to align the i.MX8MQ VPU blkctl with > > > what we are planning to do on the later chip generations. > > > > > > CC'ing Jacky Bai and Peng Fan from NXP, as they were going to give this > > > virtual power domain thing a shot. > > > > > > > It seems the i.MX8MM BLK-CTL series are moving forward: > > > > https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=479175 > > > > ... but I'm unable to wrap my head around how this affects the > > devicetree VPU modelling for i.MX8MQ (and also i.MX8MM, i.MX8MP, ...). > > > > > For the i.MX8MQ we want to have the same virtual power-domains provided > by a BLK-CTRL driver for the VPUs, as on i.MX8MM. This way we should be > able to use the same DT bindings for the VPUs on i.MX8MQ and i.MX8MM, > even though the SoC integration with the blk-ctrl is a little > different. > > > Can you clarify that? > > > I'm planning on sending some patches adding i.MX8MQ VPU support to the > BLK-CTRL driver in the next few days. I guess that should clarify > things. :) > As a gentle reminder, Hans sent the i.MX8MQ G2 HEVC support pull request and Benjamin just posted a series adding support for more features. Do you think we could have the blk-ctrl support landing in v5.14? If you work on the patches, and you happen to test the G1 and G2 on i.MX8MM it would be great to add that too. Meanwhile, our next steps would be to improve the HEVC V4L2 uAPI itself. Thanks a lot! Ezequiel