From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: "Pandey, Radhey Shyam" <radhey.shyam.pandey@amd.com>
Cc: Rob Herring <robh@kernel.org>,
"andersson@kernel.org" <andersson@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"Simek, Michal" <michal.simek@amd.com>,
"Levinsky, Ben" <ben.levinsky@amd.com>,
"Shah, Tanmay" <tanmay.shah@amd.com>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"git (AMD-Xilinx)" <git@amd.com>
Subject: Re: [PATCH v3] dt-bindings: remoteproc: add Tightly Coupled Memory (TCM) bindings
Date: Mon, 21 Aug 2023 11:58:15 -0600 [thread overview]
Message-ID: <ZOOltyWikpxc/hII@p14s> (raw)
In-Reply-To: <MN0PR12MB5953E72D7950581A8FB5AD82B711A@MN0PR12MB5953.namprd12.prod.outlook.com>
On Sat, Aug 12, 2023 at 12:57:39PM +0000, Pandey, Radhey Shyam wrote:
> > -----Original Message-----
> > From: Rob Herring <robh@kernel.org>
> > Sent: Monday, July 24, 2023 9:47 PM
> > To: Pandey, Radhey Shyam <radhey.shyam.pandey@amd.com>
> > Cc: andersson@kernel.org; mathieu.poirier@linaro.org;
> > krzysztof.kozlowski+dt@linaro.org; conor+dt@kernel.org; Simek, Michal
> > <michal.simek@amd.com>; Levinsky, Ben <ben.levinsky@amd.com>; Shah,
> > Tanmay <tanmay.shah@amd.com>; linux-remoteproc@vger.kernel.org;
> > devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-
> > kernel@vger.kernel.org; git (AMD-Xilinx) <git@amd.com>
> > Subject: Re: [PATCH v3] dt-bindings: remoteproc: add Tightly Coupled
> > Memory (TCM) bindings
> >
> > On Sat, Jul 22, 2023 at 12:11:48AM +0530, Radhey Shyam Pandey wrote:
> > > Introduce bindings for TCM memory address space on AMD-xilinx Zynq
> > > UltraScale+ platform. It will help in defining TCM in device-tree
> > > and make it's access platform agnostic and data-driven.
> >
> > From the subject, it sounds like this is a binding for all of remoteproc for
> > TCMs.
> >
> > Otherwise,
> >
> > Acked-by: Rob Herring <robh@kernel.org>
>
> Thanks for the review. Just checking if this patch will be taken through
> devicetree or remoteproc tree?
Please send the driver changes and I'll pickup everything at once.
Thanks,
Mathieu
next prev parent reply other threads:[~2023-08-21 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 18:41 [PATCH v3] dt-bindings: remoteproc: add Tightly Coupled Memory (TCM) bindings Radhey Shyam Pandey
2023-07-24 16:16 ` Rob Herring
2023-08-12 12:57 ` Pandey, Radhey Shyam
2023-08-21 17:58 ` Mathieu Poirier [this message]
2023-08-21 19:59 ` Tanmay Shah
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=ZOOltyWikpxc/hII@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=ben.levinsky@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=robh@kernel.org \
--cc=tanmay.shah@amd.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).