From: Nishanth Menon <nm@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jayesh Choudhary <j-choudhary@ti.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Tero Kristo" <t-kristo@ti.com>, Keerthy <j-keerthy@ti.com>,
Kamlesh Gurudasani <kamlesh@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Rob Herring <robh@kernel.org>, <linux-crypto@vger.kernel.org>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v5 0/2] Remove power-domains property for devices with compatible ti,am62-sa3ul
Date: Tue, 25 Jul 2023 06:39:48 -0500 [thread overview]
Message-ID: <169028509342.1718778.15078093695331558450.b4-ty@ti.com> (raw)
In-Reply-To: <20230614-sa3ul-v5-0-29dd2366fba3@ti.com>
Herbert,
I am going to assume that you are ok with me picking this series up as this
results in a few broken boots for various boards. Let me know if that is not
the case, and I will drop the series from my tree.
Hi Kamlesh Gurudasani,
On Fri, 14 Jul 2023 14:42:40 +0530, Kamlesh Gurudasani wrote:
> SYSFW don't allow access to power of devices with compatible ti,am62-sa3ul
> from main domain.
>
> Power-domains property, if present will try to access the power of the
> device, which will result into failure in probing of driver for that
> device.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/2] dt-bindings: crypto: ti,sa2ul: make power-domains conditional
commit: e1f7d17a734c5c617d05c3d188939d5032d3d5a2
[2/2] arm64: dts: ti: k3-am62-main: Remove power-domains from crypto node
commit: b573bf35ef3f113c1717fa22cefdfdfbb83aec70
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2023-07-25 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 9:12 [PATCH v5 0/2] Remove power-domains property for devices with compatible ti,am62-sa3ul Kamlesh Gurudasani
2023-07-14 9:12 ` [PATCH v5 1/2] dt-bindings: crypto: ti,sa2ul: make power-domains conditional Kamlesh Gurudasani
2023-07-24 16:45 ` Nishanth Menon
2023-07-14 9:12 ` [PATCH v5 2/2] arm64: dts: ti: k3-am62-main: Remove power-domains from crypto node Kamlesh Gurudasani
2023-07-25 11:39 ` Nishanth Menon [this message]
2023-07-26 0:29 ` [PATCH v5 0/2] Remove power-domains property for devices with compatible ti,am62-sa3ul Herbert Xu
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=169028509342.1718778.15078093695331558450.b4-ty@ti.com \
--to=nm@ti.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=j-choudhary@ti.com \
--cc=j-keerthy@ti.com \
--cc=kamlesh@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=t-kristo@ti.com \
--cc=vigneshr@ti.com \
/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