From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Liam Girdwood <lgirdwood@gmail.com>,
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: Thu, 20 Feb 2020 19:46:20 +0000 [thread overview]
Message-ID: <20200220194620.GK3926@sirena.org.uk> (raw)
In-Reply-To: <CAL_Jsq+VEQj9Nkyo_85RM3Ku1-D73_ot5BTAjidnJzJv7r1_Sw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
On Thu, Feb 20, 2020 at 01:33:56PM -0600, Rob Herring wrote:
> On Wed, Feb 19, 2020 at 8:16 PM Kuninori Morimoto
> > > > + clock-frequency:
> > > > + description: for audio_clkout0/1/2/3
> > > > + $ref: /schemas/types.yaml#/definitions/uint32-array
> > > This already has a common definition and this conflicts with that.
> > > 'clock-frequency' is a single uint32 or uint64.
> > 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?
Given that this is an existing schema we should really try to keep
compatibility :/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-20 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 5:12 [PATCH v2] ASoC: dt-bindings: renesas,rsnd: switch to yaml base Documentation 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 [this message]
2020-02-21 0:30 ` Kuninori Morimoto
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=20200220194620.GK3926@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--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;
as well as URLs for NNTP newsgroup(s).