From: Conor Dooley <conor@kernel.org>
To: "Krzysztof Wilczyński" <kw@linux.com>
Cc: linux-pci@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] dt-bindings: PCI: microchip,pcie-host: fix dma coherency property
Date: Fri, 16 May 2025 14:56:59 +0100 [thread overview]
Message-ID: <20250516-freely-squabble-a2162b60f9c1@spud> (raw)
In-Reply-To: <20250516130659.GA2084811@rocinante>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-05-16 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 9:59 [PATCH v1] dt-bindings: PCI: microchip,pcie-host: fix dma coherency property Conor Dooley
2025-05-16 13:06 ` Krzysztof Wilczyński
2025-05-16 13:56 ` Conor Dooley [this message]
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=20250516-freely-squabble-a2162b60f9c1@spud \
--to=conor@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
/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