From: "Shah, Tanmay" <tanmays@amd.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <tanmay.shah@amd.com>,
Ben Levinsky <blevinsk@amd.com>
Cc: "jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>,
"andersson@kernel.org" <andersson@kernel.org>,
"mathieu.poirier@linaro.org" <mathieu.poirier@linaro.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"Simek, Michal" <michal.simek@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>,
"Levinsky, Ben" <ben.levinsky@amd.com>
Subject: Re: [PATCH 3/6] dt-bindings: mailbox: Add AMD PL Mailbox IP
Date: Fri, 16 Oct 2026 09:11:56 -0500 [thread overview]
Message-ID: <d89b656d-44cf-440a-8e06-6e13cef2dbe9@amd.com> (raw)
In-Reply-To: <cbd2e370-c8f1-46c1-87a8-fa25fdf6ea97@kernel.org>
On 10/16/2026 8:59 AM, Krzysztof Kozlowski wrote:
> On 15/10/2026 17:31, Shah, Tanmay wrote:
>> We use 'amd' vendor prefix for all new drivers & bindings. Also, there
>> is dedicated IPI hardware which can be used as mailbox too, and we
>> should distinguish it with this PL mailbox. So I that is included in the
>> compatible string. (pl-mbox).
>>
>> If we are also to include SOC name as well (per compatible property
>> guideline), then we should include one of the SOC name as well:
>>
>> So, I think 'amd,zynqmp-pl-mbox-2.1' is good.
>>
>> Krzysztof, are you okay with above name? The 2.1 is FPGA IP design
>> version number and not the SOC version number. So in future let's say
>> that FPGA IP design is improved then the name (pl-mbox) will remain
>> same, but only version number will be updated i.e. (from 2.1 to 3.0). Is
>> it okay if we explicitly mention this in the binding description?
>
> So you will release the same SoC with different versions of the block?
>
Yes correct.
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2026-10-16 14:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 21:34 [PATCH 0/6] Add AMD PL Mailbox and RPMsg support for the AMD BRAM remoteproc Ben Levinsky
2026-10-14 21:34 ` [PATCH 1/6] remoteproc: amd_mbv_bram: Bound device name formatting Ben Levinsky
2026-10-14 21:48 ` sashiko-bot
2026-10-14 21:34 ` [PATCH 2/6] remoteproc: amd_mbv_bram: Restore reset GPIO direction after PL reconfig Ben Levinsky
2026-10-14 21:44 ` sashiko-bot
2026-10-14 21:34 ` [PATCH 3/6] dt-bindings: mailbox: Add AMD PL Mailbox IP Ben Levinsky
2026-10-15 9:46 ` Krzysztof Kozlowski
[not found] ` <DM4PR12MB644859F1CA3A936684A3338B839C2@DM4PR12MB6448.namprd12.prod.outlook.com>
2026-10-15 14:29 ` Ben Levinsky
2026-10-15 15:31 ` Shah, Tanmay
2026-10-16 13:59 ` Krzysztof Kozlowski
2026-10-16 14:11 ` Shah, Tanmay [this message]
2026-10-16 13:57 ` Krzysztof Kozlowski
2026-10-14 21:34 ` [PATCH 4/6] mailbox: Add AMD PL Mailbox soft IP controller Ben Levinsky
2026-10-14 21:41 ` sashiko-bot
2026-10-15 9:48 ` Krzysztof Kozlowski
[not found] ` <DM4PR12MB6448B4B18D0B45CCA678814F839C2@DM4PR12MB6448.namprd12.prod.outlook.com>
2026-10-15 14:30 ` Ben Levinsky
2026-10-16 14:54 ` Shah, Tanmay
2026-10-16 14:56 ` Krzysztof Kozlowski
2026-10-16 15:02 ` Ben Levinsky
2026-10-14 21:34 ` [PATCH 5/6] dt-bindings: remoteproc: Add RPMsg resources to AMD BRAM rproc Ben Levinsky
2026-10-15 9:49 ` Krzysztof Kozlowski
[not found] ` <DM4PR12MB64480F027338BA7A1EF91E17839C2@DM4PR12MB6448.namprd12.prod.outlook.com>
2026-10-15 14:32 ` Ben Levinsky
2026-10-14 21:34 ` [PATCH 6/6] remoteproc: amd_mbv_bram: Add RPMsg support Ben Levinsky
2026-10-14 21:45 ` sashiko-bot
2026-10-15 9:51 ` Krzysztof Kozlowski
[not found] ` <DM4PR12MB6448FDE3208DB753A37EF3F9839C2@DM4PR12MB6448.namprd12.prod.outlook.com>
2026-10-15 14:33 ` Ben Levinsky
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=d89b656d-44cf-440a-8e06-6e13cef2dbe9@amd.com \
--to=tanmays@amd.com \
--cc=andersson@kernel.org \
--cc=ben.levinsky@amd.com \
--cc=blevinsk@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox