From: Sameer Pujar <spujar@nvidia.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
broonie@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, thierry.reding@gmail.com,
catalin.marinas@arm.com, will@kernel.org, perex@perex.cz,
tiwai@suse.com
Cc: jonathanh@nvidia.com, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/6] ASoC: tegra: Add binding doc for OPE module
Date: Fri, 20 May 2022 09:49:26 +0530 [thread overview]
Message-ID: <90680cfb-c611-63cd-ab5f-5afb86c91cec@nvidia.com> (raw)
In-Reply-To: <049173a1-0fa6-510b-9169-ebe869b8a3b3@linaro.org>
Thanks Krzysztof for review.
On 19-05-2022 17:10, Krzysztof Kozlowski wrote:
> On 18/05/2022 19:36, Sameer Pujar wrote:
>> +description: |
>> + The Multi Band Dynamic Range Compressor (MBDRC) is part of Output
>> + Processing Engine (OPE) which interfaces with Audio Hub (AHUB) via
>> + Audio Client Interface (ACIF). MBDRC can be used as a traditional
>> + single full band or a dual band or a multi band dynamic processor.
>> +
>> +maintainers:
>> + - Jon Hunter <jonathanh@nvidia.com>
>> + - Mohan Kumar <mkumard@nvidia.com>
>> + - Sameer Pujar <spujar@nvidia.com>
>> +
>> +properties:
>> + $nodename:
>> + pattern: "^mbdrc@[0-9a-f]*$"
> Why? We enforce only generic names in shared schemas and this is neither
> shared schema nor is it generic name.
Idea was to keep these node names consistent across DT files and parent
node can allow a given list of child nodes with strict checks. Does name
like "dynamic-range-compressor@xxx"
>
>> +
>> + compatible:
>> + oneOf:
>> + - const: nvidia,tegra210-mbdrc
>> + - items:
>> + - enum:
>> + - nvidia,tegra234-mbdrc
>> + - nvidia,tegra194-mbdrc
>> + - nvidia,tegra186-mbdrc
>> + - const: nvidia,tegra210-mbdrc
>> +
>> + reg:
>> + maxItems: 1
>> +
>> +required:
>> + - compatible
>> + - reg
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> +
> No need for space
will remove
>> +
>> + compatible:
>> + oneOf:
>> + - const: nvidia,tegra210-ope
>> + - items:
>> + - enum:
>> + - nvidia,tegra234-ope
>> + - nvidia,tegra194-ope
>> + - nvidia,tegra186-ope
>> + - const: nvidia,tegra210-ope
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + "#address-cells":
>> + const: 1
>> +
>> + "#size-cells":
>> + const: 1
>> +
>> + ranges: true
>> +
>> + sound-name-prefix:
>> + pattern: "^OPE[1-9]$"
>> +
>> + ports:
>> + $ref: /schemas/graph.yaml#/properties/ports
>> + properties:
>> + port@0:
>> + $ref: audio-graph-port.yaml#
>> + unevaluatedProperties: false
>> + description: |
> No need for |
will remove.
>
>> + ope@702d8000 {
> I would suggest generic node name, if it is possible.
May be "processing-engine@xxx" ?
> peq@702d8100 {
> Generic node name, so this is "equalizer", I guess?
Yes, I can use this name.
next prev parent reply other threads:[~2022-05-20 4:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 17:36 [PATCH 0/6] OPE support on Tegra210 and later Sameer Pujar
2022-05-18 17:36 ` [PATCH 1/6] ASoC: tegra: Add binding doc for OPE module Sameer Pujar
2022-05-19 11:40 ` Krzysztof Kozlowski
2022-05-19 17:40 ` Mark Brown
2022-05-20 4:19 ` Sameer Pujar [this message]
2022-05-20 6:51 ` Krzysztof Kozlowski
2022-05-21 6:46 ` Sameer Pujar
2022-05-18 17:36 ` [PATCH 2/6] ASoC: tegra: Add Tegra210 based OPE driver Sameer Pujar
2022-05-18 17:36 ` [PATCH 3/6] ASoC: tegra: AHUB routes for OPE module Sameer Pujar
2022-05-18 17:36 ` [PATCH 4/6] arm64: defconfig: Build Tegra " Sameer Pujar
2022-05-18 17:36 ` [PATCH 5/6] arm64: tegra: Add OPE device on Tegra210 and later Sameer Pujar
2022-05-18 17:36 ` [PATCH 6/6] arm64: tegra: Enable OPE on various platforms Sameer Pujar
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=90680cfb-c611-63cd-ab5f-5afb86c91cec@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.com \
--cc=will@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