All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sameer Pujar <spujar@nvidia.com>
Cc: broonie@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	thierry.reding@gmail.com, catalin.marinas@arm.com,
	will@kernel.org, perex@perex.cz, tiwai@suse.com,
	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 v3 1/6] ASoC: tegra: Add binding doc for OPE module
Date: Fri, 3 Jun 2022 15:30:03 -0500	[thread overview]
Message-ID: <20220603203003.GA852734-robh@kernel.org> (raw)
In-Reply-To: <1654238172-16293-2-git-send-email-spujar@nvidia.com>

On Fri, Jun 03, 2022 at 12:06:07PM +0530, Sameer Pujar wrote:
> This patch adds YAML schema for DT bindings of Output Processing
> Engine (OPE) module. It consists of Parametric Equalizer (PEQ)
> and Multi Band Dynamic Range Compressor (MBDRC) sub blocks and
> binding doc for these blocks are added as well. The OPE will be
> registered as an ASoC component and can be plugged into an audio
> path as per need via ALSA mixer controls. The DT bindings are
> applicable on Tegra210 and later SoCs where OPE module is present.
> 
> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
> ---
>  .../bindings/sound/nvidia,tegra210-ahub.yaml       |  4 +
>  .../bindings/sound/nvidia,tegra210-mbdrc.yaml      | 47 ++++++++++++
>  .../bindings/sound/nvidia,tegra210-ope.yaml        | 87 ++++++++++++++++++++++
>  .../bindings/sound/nvidia,tegra210-peq.yaml        | 48 ++++++++++++
>  4 files changed, 186 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-mbdrc.yaml
>  create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-ope.yaml
>  create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-peq.yaml

Doesn't apply for me. I guess there is some undocumented dependency 
here? Resend after the merge window if that solves it.

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Sameer Pujar <spujar@nvidia.com>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
	catalin.marinas@arm.com, tiwai@suse.com, broonie@kernel.org,
	thierry.reding@gmail.com, linux-arm-kernel@lists.infradead.org,
	krzysztof.kozlowski+dt@linaro.org, linux-tegra@vger.kernel.org,
	jonathanh@nvidia.com, will@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/6] ASoC: tegra: Add binding doc for OPE module
Date: Fri, 3 Jun 2022 15:30:03 -0500	[thread overview]
Message-ID: <20220603203003.GA852734-robh@kernel.org> (raw)
In-Reply-To: <1654238172-16293-2-git-send-email-spujar@nvidia.com>

On Fri, Jun 03, 2022 at 12:06:07PM +0530, Sameer Pujar wrote:
> This patch adds YAML schema for DT bindings of Output Processing
> Engine (OPE) module. It consists of Parametric Equalizer (PEQ)
> and Multi Band Dynamic Range Compressor (MBDRC) sub blocks and
> binding doc for these blocks are added as well. The OPE will be
> registered as an ASoC component and can be plugged into an audio
> path as per need via ALSA mixer controls. The DT bindings are
> applicable on Tegra210 and later SoCs where OPE module is present.
> 
> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
> ---
>  .../bindings/sound/nvidia,tegra210-ahub.yaml       |  4 +
>  .../bindings/sound/nvidia,tegra210-mbdrc.yaml      | 47 ++++++++++++
>  .../bindings/sound/nvidia,tegra210-ope.yaml        | 87 ++++++++++++++++++++++
>  .../bindings/sound/nvidia,tegra210-peq.yaml        | 48 ++++++++++++
>  4 files changed, 186 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-mbdrc.yaml
>  create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-ope.yaml
>  create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-peq.yaml

Doesn't apply for me. I guess there is some undocumented dependency 
here? Resend after the merge window if that solves it.

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Sameer Pujar <spujar@nvidia.com>
Cc: broonie@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	thierry.reding@gmail.com, catalin.marinas@arm.com,
	will@kernel.org, perex@perex.cz, tiwai@suse.com,
	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 v3 1/6] ASoC: tegra: Add binding doc for OPE module
Date: Fri, 3 Jun 2022 15:30:03 -0500	[thread overview]
Message-ID: <20220603203003.GA852734-robh@kernel.org> (raw)
In-Reply-To: <1654238172-16293-2-git-send-email-spujar@nvidia.com>

On Fri, Jun 03, 2022 at 12:06:07PM +0530, Sameer Pujar wrote:
> This patch adds YAML schema for DT bindings of Output Processing
> Engine (OPE) module. It consists of Parametric Equalizer (PEQ)
> and Multi Band Dynamic Range Compressor (MBDRC) sub blocks and
> binding doc for these blocks are added as well. The OPE will be
> registered as an ASoC component and can be plugged into an audio
> path as per need via ALSA mixer controls. The DT bindings are
> applicable on Tegra210 and later SoCs where OPE module is present.
> 
> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
> ---
>  .../bindings/sound/nvidia,tegra210-ahub.yaml       |  4 +
>  .../bindings/sound/nvidia,tegra210-mbdrc.yaml      | 47 ++++++++++++
>  .../bindings/sound/nvidia,tegra210-ope.yaml        | 87 ++++++++++++++++++++++
>  .../bindings/sound/nvidia,tegra210-peq.yaml        | 48 ++++++++++++
>  4 files changed, 186 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-mbdrc.yaml
>  create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-ope.yaml
>  create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-peq.yaml

Doesn't apply for me. I guess there is some undocumented dependency 
here? Resend after the merge window if that solves it.

Rob

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-06-03 20:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  6:36 [PATCH v3 0/6] OPE support on Tegra210 and later Sameer Pujar
2022-06-03  6:36 ` Sameer Pujar
2022-06-03  6:36 ` Sameer Pujar
2022-06-03  6:36 ` [PATCH v3 1/6] ASoC: tegra: Add binding doc for OPE module Sameer Pujar
2022-06-03  6:36   ` Sameer Pujar
2022-06-03  6:36   ` Sameer Pujar
2022-06-03 20:30   ` Rob Herring [this message]
2022-06-03 20:30     ` Rob Herring
2022-06-03 20:30     ` Rob Herring
2022-06-06  8:17     ` Sameer Pujar
2022-06-06  8:17       ` Sameer Pujar
2022-06-06  8:17       ` Sameer Pujar
2022-06-06 13:48       ` Rob Herring
2022-06-06 13:48         ` Rob Herring
2022-06-06 13:48         ` Rob Herring
2022-06-03  6:36 ` [PATCH v3 2/6] ASoC: tegra: Add Tegra210 based OPE driver Sameer Pujar
2022-06-03  6:36   ` Sameer Pujar
2022-06-03  6:36   ` Sameer Pujar
2022-06-03  6:36 ` [PATCH v3 3/6] ASoC: tegra: AHUB routes for OPE module Sameer Pujar
2022-06-03  6:36   ` Sameer Pujar
2022-06-03  6:36   ` Sameer Pujar
2022-06-03  6:36 ` [PATCH v3 4/6] arm64: defconfig: Build Tegra " Sameer Pujar
2022-06-03  6:36   ` Sameer Pujar
2022-06-03  6:36   ` Sameer Pujar
2022-06-03  6:36 ` [PATCH v3 5/6] arm64: tegra: Add OPE device on Tegra210 and later Sameer Pujar
2022-06-03  6:36   ` Sameer Pujar
2022-06-03  6:36   ` Sameer Pujar
2022-06-03  6:36 ` [PATCH v3 6/6] arm64: tegra: Enable OPE on various platforms Sameer Pujar
2022-06-03  6:36   ` Sameer Pujar
2022-06-03  6:36   ` Sameer Pujar
2022-06-07 10:55 ` (subset) [PATCH v3 0/6] OPE support on Tegra210 and later Mark Brown
2022-06-07 10:55   ` Mark Brown
2022-06-07 10:55   ` Mark Brown

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=20220603203003.GA852734-robh@kernel.org \
    --to=robh@kernel.org \
    --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=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=spujar@nvidia.com \
    --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 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.