From: Jan Kiszka <jan.kiszka@siemens.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Siddharth Vadapalli <s-vadapalli@ti.com>,
Bao Cheng Su <baocheng.su@siemens.com>,
Hua Qian Li <huaqian.li@siemens.com>,
Diogo Ivo <diogo.ivo@siemens.com>
Subject: Re: [PATCH v2 3/6] dt-bindings: PCI: ti,am65: Extend for use with PVU
Date: Tue, 27 Aug 2024 11:32:02 +0200 [thread overview]
Message-ID: <2bb6b337-d83b-4cbe-aff2-bbd0c7d17c2b@siemens.com> (raw)
In-Reply-To: <0ca0fc20-421e-4bbc-bcda-9e5c2ea3b1b4@kernel.org>
On 27.08.24 11:29, Krzysztof Kozlowski wrote:
> On 27/08/2024 11:22, Jan Kiszka wrote:
>> On 27.08.24 08:37, Krzysztof Kozlowski wrote:
>>> On Mon, Aug 26, 2024 at 11:50:04PM +0200, Jan Kiszka wrote:
>>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>>
>>>> Describe also the VMAP registers which are needed in order to make use
>>>> of the PVU with this PCI host. Furthermore, permit to specify a
>>>> restricted DMA pool by phandle.
>>>
>>> That's an ABI break without explanation why it is necessary.
>>>
>>
>> It is needed in order to support the PVU, as written above.
>
> Above say only that you want a new feature and that's not really
> suitable explanation for ABI break, because answer to this is: add new
> feature without breaking existing users. But maybe there is a bug or
> something does not work or never work or there are no users, don't know.
>
>>
>> Previous versions of this binding likely didn't consider this use case
>> and therefore didn't describe all registers associated with the hardware.
>>
>> BTW, if you see a way to add the required registers without breaking
>> more than needed, I'm all ears. At least the kernel driver will continue
>> to work with older DTs when you disable PVU support or do not add a DMA
>> pool to the DT.
>
> If there is no ABI break, because driver still handles correctly old
> DTB, then mention it in the commit msg.
Well, this is strictly spoken not a topic for this commit because this
one should have no clue about what drivers do with DTs according to this
binding. But I can put a hint and go into details in the driver patch.
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-08-27 9:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 21:50 [PATCH v2 0/6] soc: ti: Add and use PVU on K3-AM65 for DMA isolation Jan Kiszka
2024-08-26 21:50 ` [PATCH v2 1/6] dt-bindings: soc: ti: Add AM65 peripheral virtualization unit Jan Kiszka
2024-08-27 6:36 ` Krzysztof Kozlowski
2024-08-27 9:29 ` Jan Kiszka
2024-08-27 10:35 ` Krzysztof Kozlowski
2024-08-26 21:50 ` [PATCH v2 2/6] soc: ti: Add IOMPU-like PVU driver Jan Kiszka
2024-08-26 21:50 ` [PATCH v2 3/6] dt-bindings: PCI: ti,am65: Extend for use with PVU Jan Kiszka
2024-08-27 6:37 ` Krzysztof Kozlowski
2024-08-27 9:22 ` Jan Kiszka
2024-08-27 9:29 ` Krzysztof Kozlowski
2024-08-27 9:32 ` Jan Kiszka [this message]
2024-08-27 10:06 ` Siddharth Vadapalli
2024-08-27 10:46 ` Jan Kiszka
2024-08-27 10:54 ` Krzysztof Kozlowski
2024-08-27 10:44 ` Jan Kiszka
2024-08-27 10:55 ` Krzysztof Kozlowski
2024-08-26 21:50 ` [PATCH v2 4/6] arm64: dts: ti: k3-am65-main: Add VMAP registers to PCI root complexes Jan Kiszka
2024-08-26 21:50 ` [PATCH v2 5/6] PCI: keystone: Add supported for PVU-based DMA isolation on AM654 Jan Kiszka
2024-08-26 21:50 ` [PATCH v2 6/6] arm64: dts: ti: iot2050: Enforce DMA isolation for devices behind PCI RC Jan Kiszka
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=2bb6b337-d83b-4cbe-aff2-bbd0c7d17c2b@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=baocheng.su@siemens.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diogo.ivo@siemens.com \
--cc=huaqian.li@siemens.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=ssantosh@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;
as well as URLs for NNTP newsgroup(s).