From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtpbgbr1.qq.com (smtpbgbr1.qq.com [54.207.19.206]) (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 216CD3F0779 for ; Wed, 29 Jul 2026 10:04:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=54.207.19.206 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785319498; cv=none; b=Btuj9DiTNSB1ZaI06XEld8kaHNDItG4XY9T12ZWWY/gxemjOw8dI+w6zV7npqEEGS9gQOnhER7ctLi7piAyyYGJhTXDf5dSFkZCjwZvnlst5Edk0OmrxhmoN5wx+PNwNNFPmcBtrVP3EEypPuWsR+BmNIRu2eSCgaMgMqC4qyoE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785319498; c=relaxed/simple; bh=rdrD93vGw6rglSTXXPTSCOggBebhZR6E67QQaOT9DTw=; h=Mime-Version:Content-Type:Date:Message-Id:Cc:Subject:From:To: References:In-Reply-To; b=syhEnVkq38e42i9OW47IBjFczXzvh6xhNc0//DLrXZgPCQisPAZ3wPKLADVI9mrw3BjrSDqAaGjJ7ytAH91pa0CKYbknxANA5+vzBpATDPBQcljsDRJGSZyHzfBfz/q5koNULxMK2HHc/+XgPXhL0MFmjaYa19nCwrcC2QeDXiU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=linux.spacemit.com; spf=none smtp.mailfrom=linux.spacemit.com; dkim=pass (1024-bit key) header.d=linux.spacemit.com header.i=@linux.spacemit.com header.b=YAKJel7F; arc=none smtp.client-ip=54.207.19.206 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=linux.spacemit.com Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=linux.spacemit.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.spacemit.com header.i=@linux.spacemit.com header.b="YAKJel7F" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.spacemit.com; s=mxsw2412; t=1785319486; bh=rGjRoJY2bcOuoh/YLY1s9eXB07hnFRse6TYTrFiBgo0=; h=Mime-Version:Date:Message-Id:Subject:From:To; b=YAKJel7FXO8TogPTcIV78qvau9p1Zev7iR1XSmCrgSEZNdyrhzNbZdD1e+26vIQKb QOzUI3CSTTlegFZ7ukljyoeLf8get5XnVPnd6xk7qPKDp0Vu/EcTNdRtOIqLkYiwfC SiXkpXh5w69KLclJv4pi7rG7/lbOLhbuZRbNZNX8= X-QQ-mid: zesmtpgz6t1785319483t91deea57 X-QQ-Originating-IP: 5tTKMPmo2435qtvnLyHekoCjA48pilenE9UZy9JvxsA= Received: from localhost ( [120.237.158.181]) by bizesmtp.qq.com (ESMTP) with id ; Wed, 29 Jul 2026 18:04:41 +0800 (CST) X-QQ-SSF: 0000000000000000000000000000000 X-QQ-GoodBg: 0 X-BIZMAIL-ID: 286073189035881177 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Wed, 29 Jul 2026 18:04:41 +0800 Message-Id: Cc: "frank.binns" , "robh" , "krzk+dt" , "conor+dt" , "dlan" , "dri-devel" , "devicetree" , "linux-kernel" , "linux-riscv" , "spacemit" Subject: Re: [PATCH v3 1/2] dt-bindings: gpu: img,powervr-rogue: add spacemit,k3-gpu From: "Baihui Liang" To: "Krzysztof Kozlowski" X-Mailer: aerc 0.17.0 References: <065a229b-e6a8-4cce-8725-9c2e19c8f463@kernel.org> <39f12852-a0d4-4d90-8ea3-dbfa7e1c2059@kernel.org> In-Reply-To: <39f12852-a0d4-4d90-8ea3-dbfa7e1c2059@kernel.org> X-QQ-SENDSIZE: 520 Feedback-ID: zesmtpgz:linux.spacemit.com:qybglogicsvrgz:qybglogicsvrgz6b-0 X-QQ-XMAILINFO: MglA7JX7t2v3mu1ggcnXQvXSnQK6LXYsDZf0P7SfO318wcXzq3eqmD9u HUdQApnw7F6ejl0JhVBAdXjqtfgKXaUBgMkXtJe0yo9J+fZl99N+7ibsvshrzUARVojVDGf 3P3fAOPPIBVm9dRGY1+1DMQtl/iCnzvkbwky+xM7hOzDOxG6CnQRVATOxEtIxIr3WJs13WR /MYlO3iH5wM7otQ950VSrkd0QATbTTJGT7FNjPU/ZMQ5o8A5M2KGWIDtVbkkLO7heouMiOG ggLezgpnvh6PxzQgkAKuCKIcvOzzx/AdvoguzUq649b0jagkWd9RiBRu/ZQ7a4fP6WwA/xB RUOBCn6aDUjxGLFb/S4gUzvp5bfZJeknxRxaV4XRG8CUNNZiI94Ri8Eri4oMUNBb9VWEJy1 Hh7EB0E8zWI9OAAeSCiU9yy4XXZqJn3HLoAegUYFofzIumbEP5iKpVGz+5KEKqtp1PMDxaa yNL8pJyxmXsjtqYmXeTpfE+HTW/pX4FEmXrb2UKU3bfepTZHUWX+CtdnP80/Fp+l03WvR6A ya/PcCMbWeAPIOeNJhVcb4QCYEYpTW84bjM7TDJyo13SriDMGzFAwEyWeyBYD7lD0i4s35s +NFTKkOCOHF8JIp/vEOmBmiJy4BHcODwa56Wu3bsELzewZJMGuifT0GLT2a2t6BEH5ukSUE DatQ7PV5daDe53wkDy/sxj2GJ8Ok/JXzyFORiQctFhKEtfFiSLob7S/weq/kjShmVxK9LiQ fgBcAhGWyB+GtQf/CrPAUZcsb/0FRVwM9SfqCb44lYCIShHcC0f6KhP72weVKv3UYI/65/b IWbyW3j/zVVqE3nSKy8LZKE8dU49YvwFuBn/EZId3nSKDFI8oe0RfEH+9Ylq8e498dwZsij VdwmTzrf8L9l973GCHVebVwqYPaCMPQegrJouwJBNDYqXQjO3z8ehFVwIFS+KhsQfGw9GWx LZO1DxrR8RwLNAHbu40BxuH5xYm4G7rdOwNum5y5L4j8o1ItMgkVMiAvOZjbTM0XCXsWoFq 6LVeb+EUexJyYSpnNBv9Y5nXgUGO5hLaPvONiBmoyoTKKh/0IM X-QQ-XMRINFO: NyFYKkN4Ny6FuXrnB5Ye7Aabb3ujjtK+gg== X-QQ-RECHKSPAM: 0 On Wed Jul 29, 2026 at 5:16 PM CST, Krzysztof Kozlowski wrote: > On 29/07/2026 11:14, Baihui Liang wrote: > > On Wed Jul 29, 2026 at 3:57 PM CST, Krzysztof Kozlowski wrote: > >> On 29/07/2026 09:46, Baihui Liang wrote: > >>> On Tue, Jul 28, 2026, Krzysztof Kozlowski wrote: > >>> > > [...] > >>> > > spacemit,k3-gpu is added to the existing ti,am62-gpu/ti,am6= 2p-gpu/ > >>> > > ti,j721s2-gpu "if" block that restricts clocks to a single = entry, > >>> > > since K3 has the same single-clock requirement. It does not= match any > >>> > > "if" block that constrains power-domains, so that property = falls back > >>> > > >>> > I don't get this explanation. Are you explaining what the patch = is doing > >>> > or explaining WHY you did this that way? > >>> > >>> > >>> That paragraph was describing schema mechanics, which does not belong= in > >>> a commit message. v4 will drop it and state only the hardware facts: = the > >>> K3 integration of the BXM-4-64 has a single "core" clock, and it has = no > >>> software-controllable GPU power domain. > >>> > >>> > >>> > > to this schema's general constraints, where it is optional.= This > >>> > > leaves room for a power-domains provider to be added later = without a > >>> > > further binding change, should one ever be modelled in Linu= x for this > >>> > > SoC. > >>> > > >>> > No, you need to provide constraints now. Please read carefully > >>> > writing-bindings. > >>> > >>> > >>> Understood. spacemit,k3-gpu currently matches no power-domains "if" > >>> block, so it falls back to the top-level 1-2 domains with > >>> power-domain-names "a"/"b". That would let a K3 DT with two power > >>> domains pass validation, which does not describe this hardware. v4 wi= ll > >>> add an explicit "if" block: > >>> > >>> > >>>     - if: > >>>         properties: > >>>           compatible: > >>>             contains: > >>>               const: spacemit,k3-g= pu > >>>       then: > >>>         properties: > >>>           power-domains: false > >>>           power-domain-names: false > >> > >> I understand only half of this. Please fix your email client. > >> > >> And why this reply misses reply-to header which connects it to proper > >> thread? How am I supposed to find the thread now, among 200 I received > >> yesterday? > >=20 > > Sorry -- that went out through a webmail client which sent HTML, so the > > quoting and the YAML indentation were destroyed, and it composed a new > > message instead of replying in place, which is why it lost the thread. > > I have switched to git send-email over our own SMTP; this reply should > > be plain text and properly threaded. > >=20 > >> So your name is presented here as "Baihui Liang" then why do you use > >> some fake company name? > >=20 > > liangbaihui@linux.spacemit.com is my real work address at SpacemiT. It = is > > now sent through the company's own mail server. > > Again: then why do you use fake company name as name? Actually not a > company name, but laminated product of some company? > > What is Sterling-Ash? > > Best regards, > Krzysztof Sorry, I misread what you were asking and answered the wrong question. "Sterling-Ash" is not a company and not a product name. It was a personal nickname left over in my git config, and I did not notice it was being used as the author name on the patches until you asked. It is not my name and should not have appeared there. The git config is fixed, and v4 will be sent with: From: Baihui Liang Signed-off-by: Baihui Liang Best regards, Baihui Liang