From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski@linaro.org>,
<krzysztof.kozlowski+dt@linaro.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <srk@ti.com>,
<s-vadapalli@ti.com>
Subject: Re: [PATCH 0/2] Enable MCU CPSW2G on J7AHP
Date: Tue, 14 Mar 2023 17:34:31 +0530 [thread overview]
Message-ID: <e112ada0-ae7d-8f5e-cdf9-9844bf42a9a0@ti.com> (raw)
In-Reply-To: <20230314104055.1475054-1-s-vadapalli@ti.com>
Hello,
On 14-03-2023 16:10, Siddharth Vadapalli wrote:
> Hello,
>
> This series adds missing device id property in mcu_navss device-tree node.
> Also, the device-tree support for enabling MCU CPSW2G is added.
>
> ---
> NOTE: While this series does not depend on any other series for being,
> merged it depends on the following series for MCU CPSW2G functionality:
> 1. https://lore.kernel.org/r/20230314085500.10597-1-j-choudhary@ti.com/
> 2. https://lore.kernel.org/r/20230308201513.116638-1-j-choudhary@ti.com/
Please do not merge this series until the above two series have been
merged. Otherwise, it will result in an indefinite probe deferral during
boot. By saying that this series does not depend on other series for
being merged, I meant to say that this series will apply cleanly without
any dependencies.
Regards,
Siddharth.
>
> Siddharth Vadapalli (2):
> arm64: dts: ti: k3-j784s4-mcu-wakeup: Add device id property for
> mcu_navss
> arm64: dts: ti: k3-j784s4-evm: Enable MCU CPSW2G
>
> arch/arm64/boot/dts/ti/k3-j784s4-evm.dts | 47 +++++++++++++++++++
> .../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 2 +
> 2 files changed, 49 insertions(+)
>
prev parent reply other threads:[~2023-03-14 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 10:40 Siddharth Vadapalli
2023-03-14 10:40 ` [PATCH 1/2] arm64: dts: ti: k3-j784s4-mcu-wakeup: Add device id property for mcu_navss Siddharth Vadapalli
2023-03-14 13:26 ` Nishanth Menon
2023-03-14 13:29 ` Nishanth Menon
2023-03-14 14:35 ` Jayesh Choudhary
2023-03-14 10:40 ` [PATCH 2/2] arm64: dts: ti: k3-j784s4-evm: Enable MCU CPSW2G Siddharth Vadapalli
2023-03-14 22:10 ` Andrew Davis
2023-03-15 4:02 ` Siddharth Vadapalli
2023-03-14 12:04 ` Siddharth Vadapalli [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=e112ada0-ae7d-8f5e-cdf9-9844bf42a9a0@ti.com \
--to=s-vadapalli@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=srk@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
all inboxes | Powered by JetHome®