linux-kernel - Re: [PATCH v1] dt-bindings: PCI: microchip,pcie-host: fix dma coherency property

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250516130659.GA2084811@rocinante>
Date: Fri, 16 May 2025 22:06:59 +0900
From: Krzysztof Wilczyński <kw@...ux.com>
To: Conor Dooley <conor@...nel.org>
Cc: linux-pci@...r.kernel.org, Conor Dooley <conor.dooley@...rochip.com>,
	Daire McNamara <daire.mcnamara@...rochip.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Lorenzo Pieralisi <lpieralisi@...nel.org>,
	Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
	Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] dt-bindings: PCI: microchip,pcie-host: fix dma
 coherency property

Hello,

> PolarFire SoC may be configured in a way that requires non-coherent DMA
> handling. On RISC-V, buses are coherent by default & the dma-noncoherent
> property is required to denote buses or devices that are non-coherent.
> For some reason, instead of adding dma-noncoherent to the binding
> the pointless, NOP, property dma-coherent was. Swap dma-coherent for
> dma-noncoherent.

I have favour to ask.  Can you capitalise (so-called "title case") the
subject when submitting patches that are PCI-specific DT bindings?

This is the preferred style for PCI, at least at the moment.

Also, it would save us the need to do it every time. :)

Thank you!

	Krzysztof