linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <mka@chromium.org>
To: Judy Hsiao <judyhsiao@chromium.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Srini Kandagatla <srinivas.kandagatla@linaro.org>,
	dianders@chromium.org, dgreid@chromium.org, cychiang@google.com,
	judyhsiao@google.com, tzungbi@chromium.org, swboyd@chromium.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sc7180: trogdor: Update audio codec to Max98360A
Date: Fri, 25 Jun 2021 08:26:54 -0700	[thread overview]
Message-ID: <YNX1vvwHfCkZHyaY@google.com> (raw)
In-Reply-To: <20210625045010.2914289-1-judyhsiao@chromium.org>

On Fri, Jun 25, 2021 at 12:50:10PM +0800, Judy Hsiao wrote:
> Use max98360a dts node to correctly describe the hardware.
> 
> Signed-off-by: Judy Hsiao <judyhsiao@chromium.org>

Confirmed that this matches the schematics. Apparently 'max98357a' was
used initially because 'max98360a' wasn't supported yet in the kernel
that was used for development and ships on trogdor devices (v5.4).

Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

  reply	other threads:[~2021-06-25 15:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25  4:50 [PATCH] arm64: dts: qcom: sc7180: trogdor: Update audio codec to Max98360A Judy Hsiao
2021-06-25 15:26 ` Matthias Kaehlcke [this message]
2021-07-21 15:27 ` Doug Anderson
2021-07-21 16:09   ` Bjorn Andersson

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=YNX1vvwHfCkZHyaY@google.com \
    --to=mka@chromium.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=cychiang@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dgreid@chromium.org \
    --cc=dianders@chromium.org \
    --cc=judyhsiao@chromium.org \
    --cc=judyhsiao@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=swboyd@chromium.org \
    --cc=tzungbi@chromium.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).