From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jayesh Choudhary <j-choudhary@ti.com>,
alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
devicetree@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH] ASoC: dt-bindings: davinci-mcasp: Fix interrupts property
Date: Thu, 3 Oct 2024 10:23:47 +0200 [thread overview]
Message-ID: <20241003102347.0f95e48d@xps-13> (raw)
In-Reply-To: <a67e031b-5685-48f2-b3b0-5181dd7371f2@gmail.com>
Hi Péter,
peter.ujfalusi@gmail.com wrote on Wed, 2 Oct 2024 11:43:56 +0300:
> Hi,
>
> On 01/10/2024 23:47, Miquel Raynal wrote:
> > My understanding of the interrupts property is that it can either be:
> > 1/ - TX
> > 2/ - TX
> > - RX
> > 3/ - Common/combined.
> >
> > There are very little chances that either:
> > - TX
> > - Common/combined
> > or even
> > - TX
> > - RX
> > - Common/combined
> > could be a thing.
>
> For interrupt these are the valid onesÉ
> - Common only
> - TX and RX
> - TX only
> - RX only
Thanks for the input!
AFAIU, Rx only is currently not a valid description. As you are
providing a description list with minItems = <1>, I think it expects
either the first item or nothing. When I change the example in the yaml
to only give the "rx" interrupt, make dt_binding_check errors out.
I will propose an update.
Thanks,
Miquèl
next prev parent reply other threads:[~2024-10-03 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 20:47 [PATCH] ASoC: dt-bindings: davinci-mcasp: Fix interrupts property Miquel Raynal
2024-10-02 6:34 ` Krzysztof Kozlowski
2024-10-02 6:56 ` Miquel Raynal
2024-10-02 7:23 ` Krzysztof Kozlowski
2024-10-02 8:43 ` Péter Ujfalusi
2024-10-03 8:23 ` Miquel Raynal [this message]
2024-10-02 17:37 ` Mark Brown
2024-10-03 8:25 ` Miquel Raynal
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=20241003102347.0f95e48d@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-choudhary@ti.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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.