Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2865342pxj; Mon, 17 May 2021 11:38:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy9VwxmqNJkbUvjRbVYC0DTbpWfvVizF9w/JV6wkaA/ECI63k2OfFQoDbkVcLwFDhvUKnpP X-Received: by 2002:a05:6402:2802:: with SMTP id h2mr1599049ede.243.1621276711184; Mon, 17 May 2021 11:38:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621276711; cv=none; d=google.com; s=arc-20160816; b=xZmtGqtKzDqYeiImWrcgH3z1cSdtGnCOdxU5B8Yc1slZ45kK7TDWGiYpVmZUGTfHMy qeZPRlBitzTyEgGtO0BZxHv4fDw4dscviBQz2njjBIdJOH4iss+oRea0sJHmZ671gpyo 7w0TmdxVnb5bFqOWGU0j8RHGIs5FzbrrbWBfKb0+lEaNbDZCsRqkXSzVEPUPUlSz/cS/ IlUwWyqLFTwLXb4LCVyP+TEDVcByYAKs5n5fkt66WshX12RCgFmIxA308RoYWhAB9JfP Qs3kSi27S3Ueo/Rfs1ADrTOPPQExBCpMfMJTLB+Zkdyfw4UtHJubXtOlPnejaiCcQTtS v6IQ== 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=KX63NNvUkXOlo/Rn0vRND7mko7pXrtT9tqGVFZkxNpQ=; b=mBfMeCfDRQ88ewnFYUZ+ZxP9+vOwQoctTRcOv4OVTd5sCLCLnHGlI1zMUJZXzxZY8T Dq87LlRIQIRUCLM5/mFXK+3/oR5Wc792i1FzClnmgU3ZiaaLcPkXBr/H8Xowmo7EcxxE d6MQ6RH6rzWs9LogOalzA1aThVj7xakjbRGnG7fFGLB8UJ2vUM3bB+ZmIR0zxdrU0V63 tNKxl4jQoPnKdeVbYdGmMiBVMCLl2UHYZEWYsHMMiUagDTH6+R4EmunT7i/5KoI5QDO5 +5RS2CUx8B7k4e/8j0YXNzAAgE/oXUz9akz35DGmTayd3dsHuJrpwYo9EcEkbJnpCORF +W9g== 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 p15si14566858ejj.88.2021.05.17.11.38.07; Mon, 17 May 2021 11:38:31 -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 S234106AbhEQNYt (ORCPT + 99 others); Mon, 17 May 2021 09:24:49 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:51428 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233552AbhEQNYp (ORCPT ); Mon, 17 May 2021 09:24:45 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: ezequiel) with ESMTPSA id 8FFC11F41DE7 Message-ID: <5aa5700b862234895a7a6eb251ca3c80fdc1a6d3.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: Mon, 17 May 2021 10:23:14 -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 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. > AFAICS, there's not support for i.MX8MP VPU power domains. I suppose we should make sure we'll be able to cover those as well. Will i.MX8MP need its own driver as well? > > 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. :) > Great. Thanks a lot, Ezequiel