From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Rob Herring <robh@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Linux-ALSA <alsa-devel@alsa-project.org>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ASoC: dt-bindings: renesas,rsnd: switch to yaml base Documentation
Date: 21 Feb 2020 09:30:04 +0900 [thread overview]
Message-ID: <87tv3ksryd.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <CAL_Jsq+VEQj9Nkyo_85RM3Ku1-D73_ot5BTAjidnJzJv7r1_Sw@mail.gmail.com>
Hi Rob
Thank you for your feedback
> > This needs clock array. Like this
> >
> > clock-frequency = <12288000 11289600>;
>
> Sorry, but the type is already defined in the spec. You'll still get
> warnings from the common schema and you can't override that here.
>
> Not sure what to suggest. Leave it with a fixme or move to
> assigned-clocks-rates instead?
As you know, I'm not familiar with yaml base Documentation :/
I want leave it as your fixme if possible.
> > > > + # For multi OF-graph
> > > > + ports:
> > > > + description: multi OF-Graph subnode
> > > > + type: object
> > > > + patternProperties:
> > > > + "port(@.*)?":
(snip)
> > > > + $ref: "#properties/port"
> > >
> > > Would be more simple to just always have 'ports'.
> >
> > Having "ports" or "port" are case-by-case, not always.
>
> Why?
>
> This:
>
> port {};
>
> and this:
>
> ports {
> port {};
> };
>
> Are treated the same. It's perfectly valid to have 'ports' with a single port.
Yeah, if it needs only 1 port.
If I'm not misunderstanding, We are using it as
ports {
port@0 {
endpoint {}
};
port@1 {
endpoint {}
};
....
};
or simply
port {
endpoint {}
};
And here, sometimes, "port" and "endpoint" both need "reg".
Thank you for your help !!
Best regards
---
Kuninori Morimoto
prev parent reply other threads:[~2020-02-21 0:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 5:12 Kuninori Morimoto
2020-02-19 16:17 ` Rob Herring
2020-02-20 2:16 ` Kuninori Morimoto
2020-02-20 19:33 ` Rob Herring
2020-02-20 19:46 ` Mark Brown
2020-02-21 0:30 ` Kuninori Morimoto [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=87tv3ksryd.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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
all inboxes | Powered by JetHome®