public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
	lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
	quic_plai@quicinc.com, bgoswami@quicinc.com, perex@perex.cz,
	tiwai@suse.com, srinivas.kandagatla@linaro.org,
	quic_rohkumar@quicinc.com, linux-arm-msm@vger.kernel.org,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, swboyd@chromium.org,
	judyhsiao@chromium.org
Subject: Re: [RESEND v5 2/2] ASoC: qcom: soundwire: Enable software clock gating requirement flag
Date: Mon, 4 Jul 2022 11:06:24 +0530	[thread overview]
Message-ID: <YsJ8WHgiybU0cQP/@matsya> (raw)
In-Reply-To: <1656659827-27450-3-git-send-email-quic_srivasam@quicinc.com>

On 01-07-22, 12:47, Srinivasa Rao Mandadapu wrote:
> Enable software clock gating flag in private data for SC7280
> based platforms, which are soundwire 1.6.0 version based.

why is this tagged ASoC... ???

I have fixed it up while applying

-- 
~Vinod

  reply	other threads:[~2022-07-04  5:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01  7:17 [RESEND v5 0/2] Add software clock gating requirement check Srinivasa Rao Mandadapu
2022-07-01  7:17 ` [RESEND v5 1/2] soundwire: qcom: Add flag for software clock gating check Srinivasa Rao Mandadapu
2022-07-01  7:17 ` [RESEND v5 2/2] ASoC: qcom: soundwire: Enable software clock gating requirement flag Srinivasa Rao Mandadapu
2022-07-04  5:36   ` Vinod Koul [this message]
2022-07-04  5:39     ` Srinivasa Rao Mandadapu

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=YsJ8WHgiybU0cQP/@matsya \
    --to=vkoul@kernel.org \
    --cc=agross@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bgoswami@quicinc.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=judyhsiao@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=quic_plai@quicinc.com \
    --cc=quic_rohkumar@quicinc.com \
    --cc=quic_srivasam@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=swboyd@chromium.org \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox