From: Nishanth Menon <nm@ti.com>
To: Hari Nagalla <hnagalla@ti.com>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-j784s4-main: disable remote proc nodes
Date: Thu, 10 Aug 2023 13:38:25 -0500 [thread overview]
Message-ID: <20230810183825.2qtfno7ggdredpsu@glucose> (raw)
In-Reply-To: <2f0e9dde-0c6c-b808-02a0-c4ec659fc622@ti.com>
On 10:38-20230810, Hari Nagalla wrote:
> On 8/9/23 20:10, Nishanth Menon wrote:
> > > Disable the dsp and r5f subsystem nodes by default. Proper functioning
> > > of remote processors with ipc need mailbox configurations which can
> > > vary between board configurations and applications. Hence move enabling
> > > the remote processor device nodes to where the required configurations
> > > are complete.
> > >
> > > Signed-off-by: Hari Nagalla<hnagalla@ti.com>
> > > ---
> > > This patch fixes the remote proc yamllint errors for am69-sk board
> > Fixes tag?
> As such this yamllint errors for am69-sk.dtb were present in several earlier
> tags of linux-next. Checked with latest tag: next-20230809.
>
> Please let me know if you would need v2 with the tag specified in comments.
>
Please rebase on
https://lore.kernel.org/all/5ec8b817-e63f-3d76-894d-8af4f4e880db@ti.com/
series.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2023-08-10 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 0:56 [PATCH] arm64: dts: ti: k3-j784s4-main: disable remote proc nodes Hari Nagalla
2023-08-10 1:10 ` Nishanth Menon
2023-08-10 15:38 ` Hari Nagalla
2023-08-10 18:38 ` Nishanth Menon [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=20230810183825.2qtfno7ggdredpsu@glucose \
--to=nm@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@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=robh+dt@kernel.org \
--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