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 E3B9DC27C65 for ; Tue, 11 Jun 2024 18:16:46 +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=NfjWH45RCKVDAEvdfe/QFWLz3OCJ1MBwo8WlzQ6TLD0=; b=z8JJhi412h/LTjBE2XJX7vQTb0 OC7v236V6WDOtMsP45ptRSga8x82+2SYav0bftTq5vO5j7iK+FqdvCwDaIuCyklxubkzSeR0zIfOS u4aoTf4vo4rZpsJjw1bvkPWdpf7vBbJvrIVesXwJACXsZjBS5jbeGR6kB9Wn2TdUt7eThSXa3KefI 2f8LrZ37emWhUdhIq5oP0mJWMjsiNhyhfu888eMrMRLZBeJOx2cx/JWTWoZ6B2vAeepNzMke0/qvV oFbxbnUPT/+tUOAv/NmHobLhptWWtJqIvxEEDPVkQ8ZVvUaxRRv6rD00NwrqyQfTDUrrVsp4l3Ii1 Kewz8RZw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sH62u-00000009oWs-0vEI; Tue, 11 Jun 2024 18:16:36 +0000 Received: from sin.source.kernel.org ([145.40.73.55]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sH62q-00000009oUf-0Pvg for linux-arm-kernel@lists.infradead.org; Tue, 11 Jun 2024 18:16:34 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id F0855CE0D07; Tue, 11 Jun 2024 18:16:29 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 08239C2BD10; Tue, 11 Jun 2024 18:16:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1718129789; bh=QhiccRUa8nUsNwUtkF0DHVHRaqAFjgzP5RrKB+6T1JY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pEPxnzB8t7dMfbQEPHmexKo0L4OWfieS9RXtZ4ZFc3/2fSzLcXqPQepAcvTrqtHLd swqvZEK56Eai0ZNq9HFFFks6VlBoARyn+FIZNySty+FPp2GocnCdVhAkdDnOqpDRQs wq1MUYKD6OWlM+vNeRH3hkV8OrzY7PU5ZVj/Ywnk0A2sbb0MsoC+LXX9uyoryiqRgg Z7HVuzfDTubzLDmHXjYRWFW5rqFEtNiHOB3Au83wdMtTIR7+7QxfqhxnmAGVN2GAp3 A1lCO5FZvpfLxspUkn5zrF+iLAmcXC3F/AH7mhrHGwAAyu5UIKGM6C4/DfmLcDArhI NoX7FEHV+mhuA== Date: Tue, 11 Jun 2024 19:16:24 +0100 From: Conor Dooley To: Valentin Caron Cc: Alexandre Belloni , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Alexandre Torgue , linux-rtc@vger.kernel.org, devicetree@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] dt-bindings: rtc: stm32: introduce new st,stm32mp25-rtc compatible Message-ID: <20240611-sample-remold-a75d6f6515d8@spud> References: <20240611161958.469209-1-valentin.caron@foss.st.com> <20240611161958.469209-2-valentin.caron@foss.st.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="KKwSS3olauYNtTau" Content-Disposition: inline In-Reply-To: <20240611161958.469209-2-valentin.caron@foss.st.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240611_111632_539207_2CA7B7C4 X-CRM114-Status: GOOD ( 17.18 ) 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 --KKwSS3olauYNtTau Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 11, 2024 at 06:19:57PM +0200, Valentin Caron wrote: > Introduce new st,stm32mp25-rtc compatible. It is based on st,stm32mp1-rtc. >=20 > Difference is that stm32mp25 SoC implements a triple protection on RTC > registers: > - Secure bit based protection > - Privileged context based protection > - Compartment ID filtering based protection > This driver will now check theses configurations before probing to avoid > exceptions and fake reads on register. >=20 > Link: https://www.st.com/resource/en/reference_manual/rm0457-stm32mp25xx-= advanced-armbased-3264bit-mpus-stmicroelectronics.pdf#page=3D4081 > Signed-off-by: Valentin Caron > --- > Documentation/devicetree/bindings/rtc/st,stm32-rtc.yaml | 5 ++++- > 1 file changed, 4 insertions(+), 1 deletion(-) >=20 > diff --git a/Documentation/devicetree/bindings/rtc/st,stm32-rtc.yaml b/Do= cumentation/devicetree/bindings/rtc/st,stm32-rtc.yaml > index 4703083d1f11f..65a8a93ef5753 100644 > --- a/Documentation/devicetree/bindings/rtc/st,stm32-rtc.yaml > +++ b/Documentation/devicetree/bindings/rtc/st,stm32-rtc.yaml > @@ -15,6 +15,7 @@ properties: > - st,stm32-rtc > - st,stm32h7-rtc > - st,stm32mp1-rtc > + - st,stm32mp25-rtc > =20 > reg: > maxItems: 1 > @@ -90,7 +91,9 @@ allOf: > properties: > compatible: > contains: > - const: st,stm32mp1-rtc > + anyOf: > + - const: st,stm32mp1-rtc anyOf: - const: foo - const: bar is just the same as using enum: - foo - bar Thanks, Conor. > + - const: st,stm32mp25-rtc > =20 > then: > properties: > --=20 > 2.25.1 >=20 --KKwSS3olauYNtTau Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZmiUeAAKCRB4tDGHoIJi 0vaeAP40eEjU5fOjvpKKJDIRxVKhVBgtjG8rxLq1chsBTt6ukQEAoXjCusbWQHYQ 5OMNChI7TBH/+N8h7CaL9XazCcw9CwY= =91pq -----END PGP SIGNATURE----- --KKwSS3olauYNtTau--