From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx4.wp.pl (mx4.wp.pl [212.77.101.11]) (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 CD3EA1A9FA7 for ; Sun, 11 Jan 2026 13:37:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=212.77.101.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768138623; cv=none; b=DTufktIYAR0cca6q96ZurbJlQp+wvKqX77gsQ/XWKIPLCaHVRmnOwsVoyxsZt3kl1ODDadPWj9Jlfx8PDD32kGg+MgDEWoAy4QsJx0ocoHkZQ4Y91ML5kgKxCdKg7pNrYRF/S2sLMXvczcyHnwRWOVFpn+IUy2F2/Qpymu60jJg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768138623; c=relaxed/simple; bh=L4LzBSCQkIyCpywcTE76ousRl3nswdZ42B2G/moD+ns=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=aM0nRlFEePc6er2u8iLJlmdsRB6zewHBB38VEAc0pG4cck1JlmmpyTwq/BIhyRaOjaldJZ3y7ZLCJgxUyG85wIASWs4I8UkUSNvkZHrng57RcV/5GvvIQuuphULun5jj53Z9pK/Jg3544Jrg/oWo0tFCPaqWBYNV8eNyzQmDbrw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=wp.pl; spf=pass smtp.mailfrom=wp.pl; dkim=pass (2048-bit key) header.d=wp.pl header.i=@wp.pl header.b=CUf/UaTe; arc=none smtp.client-ip=212.77.101.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=wp.pl Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=wp.pl Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=wp.pl header.i=@wp.pl header.b="CUf/UaTe" Received: (wp-smtpd smtp.wp.pl 13958 invoked from network); 11 Jan 2026 14:36:53 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wp.pl; s=20241105; t=1768138613; bh=GyrKJz6PMKwk5qm2HTkDflwTnAv1RI+K3notTIpruY0=; h=Subject:To:Cc:From; b=CUf/UaTedZOach20SFWH5Rs2F6kFXyWzcq6gxSvgPcDtMvWxO495Z5hRJRNxdQDsB rI56nFeVub6DBMVw6Eg1bw4iOvFMjCLzVunmpqYzebB4ZsqjY3e6jkFCw3RvT+L8Tp GitqJ0go56cUnEXOh4lUB0tCbFdKBtSgB5VMWXXZa93VFzfX+NwmTgrJxSqThgvXp4 J7EOBF1vNH7J4I0P91c9Gto3rh1RBeX70lV6YsDK5T6YqyqdhOW13s/en5H2no+QE+ PYREkxQzh+hBW97oqXHiAM/3HGbpWKXGhUBgAo5V1F/GfM60WQxlOT9o6Q8Ir4X0+v rN8y7m9wMVJtQ== Received: from 83.5.241.112.ipv4.supernova.orange.pl (HELO [192.168.3.246]) (olek2@wp.pl@[83.5.241.112]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with TLS_AES_256_GCM_SHA384 encrypted SMTP for ; 11 Jan 2026 14:36:53 +0100 Message-ID: Date: Sun, 11 Jan 2026 14:36:52 +0100 Precedence: bulk X-Mailing-List: linux-mips@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v3 1/3] dt-bindings: crypto: eip93: add clock gate and reset line To: Krzysztof Kozlowski Cc: benjamin.larsson@genexis.eu, chester.a.unal@arinc9.com, davem@davemloft.net, angelogioacchino.delregno@collabora.com, ansuelsmth@gmail.com, conor+dt@kernel.org, herbert@gondor.apana.org.au, krzk+dt@kernel.org, matthias.bgg@gmail.com, robh@kernel.org, sergio.paracuellos@gmail.com, tsbogend@alpha.franken.de, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-mips@vger.kernel.org References: <20260102155341.3682013-1-olek2@wp.pl> <20260103-sweet-micro-manul-12eaee@quoll> Content-Language: en-US From: Aleksander Jan Bajkowski In-Reply-To: <20260103-sweet-micro-manul-12eaee@quoll> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-WP-MailID: 2fd5ca6ba679e5b337689a6786cb36fe X-WP-AV: skaner antywirusowy Poczty Wirtualnej Polski X-WP-SPAM: NO 0000008 [4Zuy] Hi Krzysztof, On 1/3/26 15:11, Krzysztof Kozlowski wrote: > On Fri, Jan 02, 2026 at 04:47:33PM +0100, Aleksander Jan Bajkowski wrote: >> Add the clock gate and reset line, both of which are available >> on the Airoha AN7581. >> >> Signed-off-by: Aleksander Jan Bajkowski >> --- >> v3: >> - introduce patch >> --- >> .../crypto/inside-secure,safexcel-eip93.yaml | 14 ++++++++++++++ >> 1 file changed, 14 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml b/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml >> index 997bf9717f9e..c6c99c08dc68 100644 >> --- a/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml >> +++ b/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml >> @@ -48,20 +48,34 @@ properties: >> interrupts: >> maxItems: 1 >> >> + clocks: >> + maxItems: 1 >> + >> + resets: >> + maxItems: 1 >> + >> required: >> - compatible >> - reg >> - interrupts >> + - clocks >> + - resets > That's ABI break without explanation in the commit msg. > I think that the reset line and clock gate are available on all SoCs with this IP Core. Should the reset line and clock gate only be required for newly added SoCs, and remain optional for existing ones? Best regards, Aleksander