Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Diogo Ivo <diogo.ivo@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Animesh Agarwal <animeshagarwal28@gmail.com>,
	Thierry Reding <thierry.reding@kernel.org>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/2] ASoC: dt-bindings: realtek,rt5677: Add clock property
Date: Thu, 3 Sep 2026 15:26:46 +0200	[thread overview]
Message-ID: <0746f828-a424-4001-8054-1e52ed07139b@bootlin.com> (raw)
In-Reply-To: <aplEfd33wSz59iLS@sirena.org.uk>

Hi Mark,

On 9/3/26 11:57 AM, Mark Brown wrote:
> On Thu, Sep 03, 2026 at 12:11:00AM +0200, Diogo Ivo wrote:
>> Add a clock property as the RT5677 codec can be fed an
>> external clock signal.
> 
>> +  clocks:
>> +    items:
>> +      - description: phandle and clock specifier for codec MCLK.
>> +
>> +  clock-names:
>> +    items:
>> +      - const: mclk
> 
> The driver code has a reference to MCLK1 which implies multiple MCLKs,
> unfortunately no pinout seems to be available and other references in
> the driver are just to MCLK so it could be cut'n'paste.

Thanks for raising this point, I had missed it completely. In fact,
looking at rt5677.h there are two places where MCLK2 is mentioned:

#define RT5677_MCLK_SRC_SFT                     10
#define RT5677_MCLK1_SRC                        (0x0 << 10)
#define RT5677_MCLK2_SRC                        (0x1 << 10)

and

#define RT5677_PLL2_PR_SRC_SFT                  15
#define RT5677_PLL2_PR_SRC_MCLK1                (0x0 << 15)
#define RT5677_PLL2_PR_SRC_MCLK2                (0x1 << 15)

so to me it _looks_ like there are indeed two MCLK inputs, both of which
can drive the MCLK clock and can also be the input of PLL2. However, as
you mentioned I also wasn't able to find the pinout/datasheet and I have
no way of testing this. I think the safest bet here is that I send a v2
where I rename "mclk" to "mclk1" that we know for a fact exists, and
then later on if someone with access to the actual datasheet comes along
and confirms the existence of "mclk2" we can add it to the binding.

Let me know what you think!

Best regards,
Diogo

  reply	other threads:[~2026-09-03 13:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 22:10 [PATCH 0/2] rt5677: add mclk to DT binding and define it for Smaug Diogo Ivo
2026-09-02 22:11 ` [PATCH 1/2] ASoC: dt-bindings: realtek,rt5677: Add clock property Diogo Ivo
2026-09-03  9:57   ` Mark Brown
2026-09-03 13:26     ` Diogo Ivo [this message]
2026-09-03 21:01       ` Mark Brown
2026-09-04  9:06         ` Diogo Ivo
2026-09-02 22:11 ` [PATCH 2/2] arm64: tegra: smaug: Add rt5677 mclk input Diogo Ivo

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=0746f828-a424-4001-8054-1e52ed07139b@bootlin.com \
    --to=diogo.ivo@bootlin.com \
    --cc=animeshagarwal28@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@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