From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Devarsh Thakkar <devarsht@ti.com>,
andersson@kernel.org, devicetree@vger.kernel.org,
mathieu.poirier@linaro.org, p.zabel@pengutronix.de,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
s-anna@ti.com
Cc: hnagalla@ti.com, praneeth@ti.com, nm@ti.com, vigneshr@ti.com,
a-bhatia1@ti.com, j-luthra@ti.com
Subject: Re: [PATCH v3 1/2] dt-bindings: remoteproc: ti: Add new compatible for AM62 SoC family
Date: Fri, 23 Dec 2022 13:05:50 +0100 [thread overview]
Message-ID: <258196d4-5279-daf8-0b9d-b4847149fe9c@linaro.org> (raw)
In-Reply-To: <20221223115638.20192-2-devarsht@ti.com>
On 23/12/2022 12:56, Devarsh Thakkar wrote:
> AM62 family of devices don't have a R5F cluster, instead
> they have single core DM R5F.
> Add new compatible string ti,am62-r5fss to support this scenario.
>
> When this new compatible is used don't allow cluster-mode
> property usage in device-tree as this implies that there
> is no R5F cluster available and only single R5F core
> is present.
It's v3 but addresses are still not correct.
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-12-23 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 11:56 [PATCH v3 0/2] Add single core R5F IPC for AM62 SoC family Devarsh Thakkar
2022-12-23 11:56 ` [PATCH v3 1/2] dt-bindings: remoteproc: ti: Add new compatible " Devarsh Thakkar
2022-12-23 12:05 ` Krzysztof Kozlowski [this message]
2022-12-26 12:18 ` Krzysztof Kozlowski
2022-12-27 9:38 ` Devarsh Thakkar
2022-12-27 9:50 ` Krzysztof Kozlowski
2022-12-23 11:56 ` [PATCH v3 2/2] remoteproc: k3-r5: Use separate compatible string for TI " Devarsh Thakkar
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=258196d4-5279-daf8-0b9d-b4847149fe9c@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=a-bhatia1@ti.com \
--cc=andersson@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=j-luthra@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=nm@ti.com \
--cc=p.zabel@pengutronix.de \
--cc=praneeth@ti.com \
--cc=s-anna@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;
as well as URLs for NNTP newsgroup(s).