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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 10694C5518F for ; Tue, 4 Aug 2026 07:39:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=2AeDuer+2UelmfR9XEG62yP5qp3AurNJprWOUQVKWCY=; b=xWtec7dDVaO3ysiHmlM/ysr4bT JR+2SyCbyoC2PhzmrQ5iGqIO6VQ+QpFv7VmIWPvUF0yub7237JJ05rdaqTCjRE3YEHXVd1e3YLBSi h/wPZqcL/BcrqbRB3uF+hZYhWH2R7T8NWyTQplyVQ7BkMSeIzOCjkjfRFntcB87F3csh9ZntUcAeG /ixbMSvD28xhv2xrU1eSCX6Zh0A1bVHEwsErQ59F3UKfNdnEiZht7xpmkMVpw0tuKalcdXlEMl8cr J4bWvWhI3xl1yeq3RekhTTDInlweddapU/di6TcWxcd9mTtbQ10oWaEw9x1KjrHMtQrbQTY0rojNw ZC2+rihg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wr9k9-00000001Fk7-3mJ7; Tue, 04 Aug 2026 07:39:21 +0000 Received: from tor.source.kernel.org ([172.105.4.254]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wr9k8-00000001Fjh-04RB; Tue, 04 Aug 2026 07:39:20 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id EBD0260A59; Tue, 4 Aug 2026 07:39:18 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A8A591F000E9; Tue, 4 Aug 2026 07:39:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1785829158; bh=2AeDuer+2UelmfR9XEG62yP5qp3AurNJprWOUQVKWCY=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=GyUFC+ohAAdUri+1fDm1dNxP9bAs/l/YIbDW8K96haCeLX4Yro5UtmiyRlPhQHh2w 3nXSWYzLyv1FypUKc23T0ZI6bcY4/ooiCfRil3C3B6GxkX+V+XH1NcNZQIonBNNtIX Wm4s/b6iivqXkvi4iM2dPiD9WYruJnRpLOkPIPxMsD113Ke+nXygYyObmOLOBrvCej PcBzJeKolpo+GmZn4myTXtDGqTllj9neky+A0Di/Y8GCaxpkmrGB4pqqQ/6oonRfYj iOf2FDoyOhVCL8b906Y3VlS0oqNoatXWZenjEI1QGf/JsT5v5Ie40zdl7MwCdFyjHm fE99r3SLMKBCA== Date: Tue, 4 Aug 2026 09:39:15 +0200 From: Krzysztof Kozlowski To: Hrushiraj Gandhi Cc: Srinivas Kandagatla , Heiko Stuebner , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Liam Girdwood , Mark Brown , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/2] dt-bindings: nvmem: rockchip-efuse: add optional vqps supply Message-ID: <20260804-witty-screeching-cicada-9e0df0@quoll> References: <20260729085856.226001-1-hrushirajg23@gmail.com> <20260729085856.226001-2-hrushirajg23@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20260729085856.226001-2-hrushirajg23@gmail.com> X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Jul 29, 2026 at 02:28:55PM +0530, Hrushiraj Gandhi wrote: > Add an optional vqps-supply property for the eFuse programming supply > voltage (VQPS). > > Per RK3399 TRM section 21.6.1, table 21-3, VQPS must be 0V during reads > and 1.8V to 1.98V during A_PGM mode writes. The presence of this supply > declares that the board hardware supports software-initiated eFuse > programming and provides the requisite programming supply. > > Signed-off-by: Hrushiraj Gandhi > --- > Documentation/devicetree/bindings/nvmem/rockchip-efuse.yaml | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/Documentation/devicetree/bindings/nvmem/rockchip-efuse.yaml b/Documentation/devicetree/bindings/nvmem/rockchip-efuse.yaml > index b80fd8d1ae5b..25f209fd881e 100644 > --- a/Documentation/devicetree/bindings/nvmem/rockchip-efuse.yaml > +++ b/Documentation/devicetree/bindings/nvmem/rockchip-efuse.yaml > @@ -27,6 +27,11 @@ properties: > # Deprecated: old compatible value for rk3066a, rk3188 and rk3288 > - rockchip,rockchip-efuse > > + vqps-supply: Odd placement. reg always follows the compatible, see DTS coding style. This is not even alphabetical. What is the logic? Best regards, Krzysztof