From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@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: Sat, 02 Jul 2022 11:30:20 +0200 [thread overview]
Message-ID: <4344746.jZfb76A358@phil> (raw)
In-Reply-To: <1729137.VLH7GnMWUR@diego>
Hi Rob,
Am Dienstag, 28. Juni 2022, 13:22:31 CEST schrieb Heiko Stübner:
> Am Montag, 27. Juni 2022, 17:51:51 CEST schrieb Heiko Stübner:
> > Am Montag, 27. Juni 2022, 17:14:45 CEST schrieb Rob Herring:
> > > 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.
> >
> > No worries and sorry I didn't think of where the schema comes from
> > in the first place. I'll do the relevant schema work as well.
>
> Done in https://github.com/devicetree-org/dt-schema/pull/78 .
>
> I wasn't sure about the "development model" of dt-schema [0] but there
> were already github pull-requests pending, so I've added another one
> for the new property :-) .
so as the dt-schema patch did go through the github-pull,. I've converted
this patch as well, so there is now a matching pull-request on github for
the spec addition.
Heiko
prev parent reply other threads:[~2022-07-02 9:30 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
[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 [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=4344746.jZfb76A358@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=robh-DgEjT+Ai2ygdnm+yROfE0A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.