[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250516-freely-squabble-a2162b60f9c1@spud>
Date: Fri, 16 May 2025 14:56:59 +0100
From: Conor Dooley <conor@...nel.org>
To: Krzysztof Wilczyński <kw@...ux.com>
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
On Fri, May 16, 2025 at 10:06:59PM +0900, Krzysztof Wilczyński wrote:
> 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?
Sure, I can add that to my list of things I try to remember while
submitting for PCI.
>
> 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
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists