Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Francesco Dolcini <francesco@dolcini.it>,
	Nishanth Menon <nm@ti.com>, <kamlesh@ti.com>
Cc: <kristo@kernel.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62-main: Remove power-domains from crypto node
Date: Sat, 27 May 2023 12:01:28 +0530	[thread overview]
Message-ID: <d030a431-933d-4f54-ba6a-f7bc5a12f843@ti.com> (raw)
In-Reply-To: <ZG90RS4KYo0bCwF7@francesco-nb.int.toradex.com>



On 25/05/23 8:14 pm, Francesco Dolcini wrote:
> On Mon, Apr 17, 2023 at 08:42:41AM -0500, Nishanth Menon wrote:
>> On 19:03-20230417, kamlesh@ti.com wrote:
>>> From: Kamlesh Gurudasani <kamlesh@ti.com>
>>>
>>> With latest firmware update, we can no longer control power of SA3UL from
>>> main domain.
>>
>> How is this backward compatible?
> 
> I just stumbled across this commit since I had an issue with crypto@40900000
> not being probed on Verdin AM62.
> 
> Not sure how this is supposed to work about backward/forward
> compatibility, however this is needed for having it working with the
> latest firmware.
> 

From what I understand, newer firmware seems to hate SA3UL PD control
requests. But older firmwares just ignored the call as the SA3UL PD is
on by default. So as such, this DT patch alone wont break
forward/backward compatibility.

It looks like newer firmware is broken wrt older kernel which is
unfortunate.

Kamlesh: can you resubmit this patch with appropriate "Fixes" tag so
that it gets backported to stable kernels?

> And if there is a proper way that take care of this, it should be
> backported IMO.
> 
> Francesco
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-05-27  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 13:33 [PATCH] arm64: dts: ti: k3-am62-main: Remove power-domains from crypto node kamlesh
2023-04-17 13:42 ` Nishanth Menon
2023-05-25 14:44   ` Francesco Dolcini
2023-05-27  6:31     ` Vignesh Raghavendra [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d030a431-933d-4f54-ba6a-f7bc5a12f843@ti.com \
    --to=vigneshr@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=francesco@dolcini.it \
    --cc=kamlesh@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox