devicetree-spec.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Cc: Mailing List
	<devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Grant Likely
	<grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Subject: Re: [PATCH] Add 'dma-noncoherent' property as a standard property
Date: Mon, 27 Jun 2022 09:14:45 -0600	[thread overview]
Message-ID: <CAL_JsqK20v34ZFWzeicaVoDWmjAsBwPyc89kaV-26Se_1eKtmQ@mail.gmail.com> (raw)
In-Reply-To: <20220619203719.3604757-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>

On Sun, Jun 19, 2022 at 2:37 PM Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org> wrote:
>
> Similar to the 'dma-coherent' property, some architectures may be coherent
> by default with some devices being non-coherent. Add a property for this
> case tool.

Looks fine, but I also need a schema.

Yeah, that's redundant unfortunately. Maybe someday someone will care
enough to generate the spec from the schemas.

>
> Signed-off-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
> ---
> Companion patch to RISC-V Zicbom noncoherent dma support
> https://lore.kernel.org/linux-riscv/20220619203212.3604485-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org/
>
>  source/chapter2-devicetree-basics.rst | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
>
> diff --git a/source/chapter2-devicetree-basics.rst b/source/chapter2-devicetree-basics.rst
> index 47d2fad..bdd7b9f 100644
> --- a/source/chapter2-devicetree-basics.rst
> +++ b/source/chapter2-devicetree-basics.rst
> @@ -832,6 +832,19 @@ Description:
>     coherent DMA operations. Some architectures have coherent DMA by default
>     and this property is not applicable.
>
> +dma-noncoherent
> +~~~~~~~~~~~~
> +
> +Property name: ``dma-noncoherent``
> +
> +Value type: ``<empty>``
> +
> +Description:
> +   For architectures which are by default coherent for I/O, the
> +   *dma-noncoherent* property is used to indicate a device is not capable of
> +   coherent DMA operations. Some architectures have non-coherent DMA by
> +   default and this property is not applicable.
> +
>  name (deprecated)
>  ~~~~~~~~~~~~~~~~~
>
> --
> 2.35.1
>

  parent reply	other threads:[~2022-06-27 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-19 20:37 [PATCH] Add 'dma-noncoherent' property as a standard property Heiko Stuebner
     [not found] ` <20220619203719.3604757-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2022-06-27 15:14   ` Rob Herring [this message]
     [not found]     ` <CAL_JsqK20v34ZFWzeicaVoDWmjAsBwPyc89kaV-26Se_1eKtmQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-27 15:51       ` Heiko Stübner
2022-06-28 11:22         ` Heiko Stübner
2022-07-02  9:30           ` Heiko Stuebner

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=CAL_JsqK20v34ZFWzeicaVoDWmjAsBwPyc89kaV-26Se_1eKtmQ@mail.gmail.com \
    --to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
    --cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).