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, kuninori.morimoto.gx@renesas.com,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: audio-graph-card: Drop remote-endpoint as required property
Date: Wed, 9 Dec 2020 20:15:50 -0600	[thread overview]
Message-ID: <20201210021550.GA1498001@robh.at.kernel.org> (raw)
In-Reply-To: <1607498532-19518-1-git-send-email-spujar@nvidia.com>

On Wed, Dec 09, 2020 at 12:52:12PM +0530, Sameer Pujar wrote:
> The remote-endpoint may not be available if it is part of some
> pluggable module. One such example would be an audio card, the
> Codec endpoint will not be available until it is plugged in.
> Hence drop 'remote-endpoint' as a required property.

Please hold off on this. I have more changes coming.

> 
> Cc: Rob Herring <robh@kernel.org>
> Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
> ---
>  Documentation/devicetree/bindings/sound/audio-graph-port.yaml | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/sound/audio-graph-port.yaml b/Documentation/devicetree/bindings/sound/audio-graph-port.yaml
> index 2005014..766e910 100644
> --- a/Documentation/devicetree/bindings/sound/audio-graph-port.yaml
> +++ b/Documentation/devicetree/bindings/sound/audio-graph-port.yaml
> @@ -71,9 +71,6 @@ properties:
>              description: CPU to Codec rate channels.
>              $ref: /schemas/types.yaml#/definitions/uint32
>  
> -        required:
> -          - remote-endpoint
> -
>    ports:
>      description: multi OF-Graph subnode
>      type: object
> -- 
> 2.7.4
> 

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,
	broonie@kernel.org, linux-kernel@vger.kernel.org,
	kuninori.morimoto.gx@renesas.com
Subject: Re: [PATCH] ASoC: audio-graph-card: Drop remote-endpoint as required property
Date: Wed, 9 Dec 2020 20:15:50 -0600	[thread overview]
Message-ID: <20201210021550.GA1498001@robh.at.kernel.org> (raw)
In-Reply-To: <1607498532-19518-1-git-send-email-spujar@nvidia.com>

On Wed, Dec 09, 2020 at 12:52:12PM +0530, Sameer Pujar wrote:
> The remote-endpoint may not be available if it is part of some
> pluggable module. One such example would be an audio card, the
> Codec endpoint will not be available until it is plugged in.
> Hence drop 'remote-endpoint' as a required property.

Please hold off on this. I have more changes coming.

> 
> Cc: Rob Herring <robh@kernel.org>
> Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
> ---
>  Documentation/devicetree/bindings/sound/audio-graph-port.yaml | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/sound/audio-graph-port.yaml b/Documentation/devicetree/bindings/sound/audio-graph-port.yaml
> index 2005014..766e910 100644
> --- a/Documentation/devicetree/bindings/sound/audio-graph-port.yaml
> +++ b/Documentation/devicetree/bindings/sound/audio-graph-port.yaml
> @@ -71,9 +71,6 @@ properties:
>              description: CPU to Codec rate channels.
>              $ref: /schemas/types.yaml#/definitions/uint32
>  
> -        required:
> -          - remote-endpoint
> -
>    ports:
>      description: multi OF-Graph subnode
>      type: object
> -- 
> 2.7.4
> 

  reply	other threads:[~2020-12-10  2:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09  7:22 [PATCH] ASoC: audio-graph-card: Drop remote-endpoint as required property Sameer Pujar
2020-12-09  7:22 ` Sameer Pujar
2020-12-10  2:15 ` Rob Herring [this message]
2020-12-10  2:15   ` Rob Herring
2020-12-10 14:44   ` Sameer Pujar
2020-12-10 14:44     ` Sameer Pujar
2020-12-28  6:45     ` Sameer Pujar
2020-12-28  6:45       ` Sameer Pujar
2021-01-11  4:49     ` Sameer Pujar
2021-01-11  4:49       ` 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=20201210021550.GA1498001@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spujar@nvidia.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.