From: Ben Levinsky <blevinsk@amd.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Ben Levinsky <ben.levinsky@amd.com>
Cc: andersson@kernel.org, mathieu.poirier@linaro.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, tanmay.shah@amd.com,
michal.simek@amd.com
Subject: Re: [PATCH v4 1/2] dt-bindings: remoteproc: document AMD BRAM-based rproc
Date: Tue, 30 Jun 2026 06:47:19 -0700 [thread overview]
Message-ID: <ff690a87-1929-400f-b566-74458c3c7da5@amd.com> (raw)
In-Reply-To: <20260630-porcelain-skunk-of-modernism-2bf87a@quoll>
Hi Krzysztof,
I apologize if this came off as my ignoring your emails.
In the v3 you had said:
> + - enum:
> + - xlnx,versal-bram-rproc
> + - xlnx,versal-net-bram-rproc
> + - amd,versal2-bram-rproc
If there is going to be a new version, this should be sorted by name.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
I was uncomfortable in adding the Reviewed-by if that is what you meant.
In this v4 I believe your review comment to sort by name was addressed.
Apologies for my misunderstanding.
Respectfully,
Ben Levinsky
On 6/29/26 11:53 PM, Krzysztof Kozlowski wrote:
> On Mon, Jun 29, 2026 at 09:40:02AM -0700, Ben Levinsky wrote:
>> Describe an AMD BRAM-based remote processor controlled through the
>> remoteproc framework.
>>
>> The binding models a soft-core processor subsystem instantiated in AMD
>> programmable logic and using dual-port BRAM for firmware storage and
>> execution. The remoteproc device is represented as a child node whose
>> reg property describes the firmware memory window in the processor-local
>> address space. The parent bus node provides standard devicetree address
>> translation through ranges so Linux can access the same BRAM through the
>> system physical address space.
>>
>> A clock input feeds the soft-core processor subsystem, and an active-low
>> reset GPIO holds the processor in reset until firmware loading
>> completes. The firmware-name property is optional.
>>
>> Signed-off-by: Ben Levinsky <ben.levinsky@amd.com>
>
> So you are going to ignore my emails? You know, it can work both ways.
>
> I drop this from Patchwork.
>
> Best regards,
>
>
next prev parent reply other threads:[~2026-06-30 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 16:40 [PATCH v4 0/2] remoteproc: add AMD BRAM-based remote processor driver Ben Levinsky
2026-06-29 16:40 ` [PATCH v4 1/2] dt-bindings: remoteproc: document AMD BRAM-based rproc Ben Levinsky
2026-06-30 6:53 ` Krzysztof Kozlowski
2026-06-30 13:47 ` Ben Levinsky [this message]
2026-06-30 14:27 ` Krzysztof Kozlowski
2026-06-30 14:38 ` Ben Levinsky
2026-06-29 16:40 ` [PATCH v4 2/2] remoteproc: add AMD BRAM-based remote processor driver Ben Levinsky
2026-06-29 18:59 ` sashiko-bot
2026-07-03 16:39 ` Mathieu Poirier
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=ff690a87-1929-400f-b566-74458c3c7da5@amd.com \
--to=blevinsk@amd.com \
--cc=andersson@kernel.org \
--cc=ben.levinsky@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=michal.simek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.