Received: by 2002:a05:7412:e794:b0:fa:551:50a7 with SMTP id o20csp841102rdd; Wed, 10 Jan 2024 00:40:37 -0800 (PST) X-Google-Smtp-Source: AGHT+IFG2GhZjQ7Jc9JLmGxkpWuiA1kRzcrp0TdGEcIySK3B1V5qMR4N7yZysgsROsT7xK9FtNkZ X-Received: by 2002:a05:6a20:6295:b0:199:b23b:683e with SMTP id o21-20020a056a20629500b00199b23b683emr329616pze.111.1704876037216; Wed, 10 Jan 2024 00:40:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1704876037; cv=none; d=google.com; s=arc-20160816; b=mVzDX506L4S0Bv1+NgBRi1darbSEU51etZugMpzjjVAzV6kgyFYPgCZAaC629xdVD8 lEEcJWS8IXRzupSctDl6bisJNidivuiZFBdu1M9ao2JyJfCy/1OjpgO0Xo20O1tvdRx6 sBZDV2q/uy2enqOMiNa1kEYcGPnwMD5sQHCsemFV4FcOVqo49uO9XxjifnNlCmP62kre uVyKwZ90kp4f/d/VJpLfJN1jJ1+QbtE9e0vCasiXDeXiewbT4eoDO2RlouyZ049OCshf 4/oNG9rVsHZQ5BwFxN/ctd+iaGK24QuCp6Xek6uQLWfHzYu7C60ZQ1h1fibRG1OCe6vA 5Ivg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:message-id:subject:cc :to:from:date:dkim-signature; bh=7j4mhkBLWboPjTrwGEN2ixQvVlyH3Cv1yLGrCIHvrVs=; fh=6RAoLR96bCRSSwS8kj3s4xl4E4WW8+IrKVfXc11pxkE=; b=JETl++Pwb0rlOIDvHtDTJKuMBw33WDILO5CLNkgEgJYz/MzZBM/srTvU9jPY+xNciq bCmmocF3Tb3C6zEX70UFU8qEEFrxmY9B9IJCk9EOmcc67CjtQ9SYTimF0tI4rpATKfrz +ZS28rABPoxOy60xXsbv2zshQxoiNir8wBNjVCdpBIr/xbVD4ahTCmpi0fkMQSTNKskf 0/KakQxq/X3GsokYsQM9HZwBMhoqMYwtu+9XIQz3t8bd+PknhCKk+eEFbDIS65G7C8Cq YC6apFV9/RUJWd5YegxN6RsRMn6BC476JngrughgxBzkHDVdh9xICPxL42I4Egsr+F4L 7vMQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@atomide.com header.s=25mailst header.b=lI0HjohH; spf=pass (google.com: domain of linux-kernel+bounces-21855-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-21855-linux.lists.archive=gmail.com@vger.kernel.org" Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [2604:1380:45e3:2400::1]) by mx.google.com with ESMTPS id ob17-20020a17090b391100b0028dc7c0c5d5si197018pjb.57.2024.01.10.00.40.36 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 10 Jan 2024 00:40:37 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-21855-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1; Authentication-Results: mx.google.com; dkim=pass header.i=@atomide.com header.s=25mailst header.b=lI0HjohH; spf=pass (google.com: domain of linux-kernel+bounces-21855-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-21855-linux.lists.archive=gmail.com@vger.kernel.org" Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id C9A8828890D for ; Wed, 10 Jan 2024 08:40:07 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 9839D33CFD; Wed, 10 Jan 2024 08:39:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=atomide.com header.i=@atomide.com header.b="lI0HjohH" Received: from mail5.25mail.st (mail5.25mail.st [74.50.62.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 99370360AD; Wed, 10 Jan 2024 08:39:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=atomide.com Authentication-Results: smtp.subspace.kernel.org; spf=fail smtp.mailfrom=atomide.com Received: from localhost (91-158-86-216.elisa-laajakaista.fi [91.158.86.216]) by mail5.25mail.st (Postfix) with ESMTPSA id 081BB6050F; Wed, 10 Jan 2024 08:38:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=atomide.com; s=25mailst; t=1704875996; bh=wG6D9r+AI35mwEbnFd6ymRyQAT79Vq6rM5ctoGLtHBU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=lI0HjohHY5ZqItxAs8wT161JVYpJtAgnjXEDs+XAyJc9k4uwAIKZILCoxniGxeHM7 NMpL2XdZBWs7+S3w/NZWsNimkeJR16R95GGWUpKizv2Adtqb7FXYWlzxwi2V8+nFoP RTiflB6mFHXKPGPj2+TZa7Ttqzte47OVO5wCtpk/a3jM3EtOWoczIwawN0tSH8TgEZ p+8904d/1MpIM6uukmZIHlwKjUrgcv3Hn6jYHHrOMm5heZJAuYWXVcNuvp1ITYC3H5 5YZX2Q1DTS1LnZJLB3LqYmb7VI5cGaZX5FqpnZ+7cjS6IsYI7KpDEbaMmJIcktwVcV lgNioh8C/jw9w== Date: Wed, 10 Jan 2024 10:38:57 +0200 From: Tony Lindgren To: Krzysztof Kozlowski Cc: Andrew Davis , Frank Binns , Matt Coster , "H . Nikolaus Schaller" , Adam Ford , Ivaylo Dimitrov , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Chen-Yu Tsai , Jernej Skrabec , Samuel Holland , =?utf-8?Q?Beno=C3=AEt?= Cousson , Nishanth Menon , Vignesh Raghavendra , Tero Kristo , Paul Cercueil , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-sunxi@lists.linux.dev, linux-omap@vger.kernel.org, linux-mips@vger.kernel.org Subject: Re: [PATCH 02/11] dt-bindings: gpu: Add PowerVR Series5 SGX GPUs Message-ID: <20240110083857.GB5185@atomide.com> References: <20240109171950.31010-1-afd@ti.com> <20240109171950.31010-3-afd@ti.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: * Krzysztof Kozlowski [240109 19:53]: > On 09/01/2024 18:19, Andrew Davis wrote: > > The Imagination PowerVR Series5 "SGX" GPU is part of several SoCs from > > multiple vendors. Describe how the SGX GPU is integrated in these SoC, > > including register space and interrupts. Clocks, reset, and power domain > > information is SoC specific. > > > > Signed-off-by: Andrew Davis > > Reviewed-by: Javier Martinez Canillas > > > > + clock-names: > > + minItems: 1 > > + items: > > + - const: core > > + - const: mem > > + - const: sys > > There are no devices currently using third clock, but I assume it is > expected or possible. I think the third clock is typically merged with one of the two clocks but yeah possibly it's a separate clocke in some cases. > Reviewed-by: Krzysztof Kozlowski Looks good to me too. So for merging these, as many of the changes touch the omap variants, I could set up an immutable branch with all the changes after -rc1. Or I can ack the patches too if somebody has better ideas. Regards, Tony