From: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>
To: Mithil <bavishimithil@gmail.com>, Krzysztof Kozlowski <krzk@kernel.org>
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>,
Lopez Cruz <misael.lopez@ti.com>,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] ASoC: dt-bindings: omap-mcpdm: Convert to DT schema
Date: Wed, 22 May 2024 21:49:41 +0300 [thread overview]
Message-ID: <bcbe109d-5974-428d-b74e-c29bec9f68b0@gmail.com> (raw)
In-Reply-To: <CAGzNGRmTR_nK0SoWG8uqDfRzDShs7sR+Mc+44__SBi0CR5LKEg@mail.gmail.com>
Hi,
On 22/05/2024 20:47, Mithil wrote:
> My apologies, misunderstood the error.
> Proposed changes for the next version,
> Add dma, dma-names, reg-names properties, and do the changes in
> example (rename node to mcpdm since it is different from generic pdm).
> reg-names:
> items:
> - const: mpu
> - const: dma
>
> dmas:
> maxItems: 2
>
> dma-names:
> items:
> - const: up_link
> - const: dn_link
>
> examples:
> - |
> #include <dt-bindings/interrupt-controller/arm-gic.h>
> mcpdm@0 {
> compatible = "ti,omap4-mcpdm";
> reg = <0x0 0x7f>, /* MPU private access */
> <0x49032000 0x7f>; /* L3 Interconnect */
> reg-names = "mpu", "dma";
> interrupts = <GIC_SPI 112 IRQ_TYPE_LEVEL_HIGH>;
> interrupt-parent = <&gic>;
> dmas = <&sdma 65>,
> <&sdma 66>;
These can be in one line to make it nice and tidy
> dma-names = "up_link", "dn_link";
> ti,hwmods = "mcpdm";
The ti,hwmods no longer needed since the sysc conversion
> clocks = <&twl6040>;
> clock-names = "pdmclk";
> };
>
> Remove ti.hwmods from required since some dts like
> omap4-duovero-parlor, omap4-panda etc do not use it which causes
> dtbs_check to not pass.
>
--
Péter
next prev parent reply other threads:[~2024-05-22 18:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 7:52 [PATCH v5] ASoC: dt-bindings: omap-mcpdm: Convert to DT schema Mighty
2024-05-22 8:42 ` Krzysztof Kozlowski
2024-05-22 13:46 ` Mithil
2024-05-22 14:15 ` Krzysztof Kozlowski
2024-05-22 13:56 ` Péter Ujfalusi
2024-05-22 14:16 ` Krzysztof Kozlowski
2024-05-22 14:43 ` Péter Ujfalusi
2024-05-22 15:22 ` Krzysztof Kozlowski
2024-05-22 16:01 ` Péter Ujfalusi
2024-05-22 16:42 ` Krzysztof Kozlowski
2024-05-22 17:02 ` Mithil
2024-05-22 17:07 ` Mithil
2024-05-22 17:07 ` Krzysztof Kozlowski
2024-05-22 17:30 ` Mithil
2024-05-22 17:47 ` Mithil
2024-05-22 18:49 ` Péter Ujfalusi [this message]
2024-05-22 18:39 ` Péter Ujfalusi
2024-05-23 6:08 ` Krzysztof Kozlowski
2024-05-22 17:05 ` DT schema bindings conversion mentorships (was Re: [PATCH v5] ASoC: dt-bindings: omap-mcpdm: Convert to DT schema) Krzysztof Kozlowski
2024-05-22 17:47 ` Javier Carrasco
2024-05-23 6:12 ` Krzysztof Kozlowski
2024-05-22 18:36 ` Conor Dooley
2024-05-23 12:33 ` Daniel Baluta
2024-05-23 12:30 ` Daniel Baluta
2024-05-23 16:24 ` Rob Herring
2024-05-23 16:31 ` Javier Carrasco
2024-05-22 14:22 ` [PATCH v5] ASoC: dt-bindings: omap-mcpdm: Convert to DT schema Rob Herring
2024-05-22 14:39 ` Péter Ujfalusi
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=bcbe109d-5974-428d-b74e-c29bec9f68b0@gmail.com \
--to=peter.ujfalusi@gmail.com \
--cc=bavishimithil@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=misael.lopez@ti.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).