From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rob Herring <robh@kernel.org>
Cc: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
Vinod Koul <vkoul@kernel.org>, Heng Sia <jee.heng.sia@intel.com>,
dmaengine <dmaengine@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: dma: snps,dw-axi-dmac: Group tuples in snps properties
Date: Thu, 2 Dec 2021 11:04:16 +0100 [thread overview]
Message-ID: <CAMuHMdWaW2Bv4Q7LPkVDeYngRWoTMztzUHZEvpLWbDkn9epH_A@mail.gmail.com> (raw)
In-Reply-To: <Yaf6wa5tyO/oCCeK@robh.at.kernel.org>
Hi Rob,
On Wed, Dec 1, 2021 at 11:44 PM Rob Herring <robh@kernel.org> wrote:
> On Thu, Nov 25, 2021 at 04:19:18PM +0100, Geert Uytterhoeven wrote:
> > To improve human readability and enable automatic validation, the tuples
> > in "snps,block-size" and "snps,priority" properties should be grouped
> > using angle brackets.
>
> For these, the tools should allow either way. Where are you seeing an
> error?
Good to know. I'm not seeing any errors.
> I tried to rationalize which way should be 'correct' and gave up. I
> think bracketing only makes sense for matrix and phandle+arg cases.
That makes sense. And "interrupts" is special, because it's really a
short-hand for "interrupts-extended", with the phandle specified by
"interrupt-parent" at the same or a higher level.
Hence I'll drop this patch.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2021-12-02 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 15:19 [PATCH] dt-bindings: dma: snps,dw-axi-dmac: Group tuples in snps properties Geert Uytterhoeven
2021-12-01 22:44 ` Rob Herring
2021-12-02 10:04 ` Geert Uytterhoeven [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=CAMuHMdWaW2Bv4Q7LPkVDeYngRWoTMztzUHZEvpLWbDkn9epH_A@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jee.heng.sia@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).