From: Stephen Boyd <sboyd@kernel.org>
To: Conor Dooley <conor+dt@kernel.org>, Jai Luthra <j-luthra@ti.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: Vignesh Raghavendra <vigneshr@ti.com>, Andrew Davis <afd@ti.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Jai Luthra <j-luthra@ti.com>
Subject: Re: [PATCH v3 2/2] clk: keystone: syscon-clk: Add support for audio refclk
Date: Fri, 16 Jun 2023 12:16:29 -0700 [thread overview]
Message-ID: <7c1dbb26bb7693929bca45a7b28bf9c8.sboyd@kernel.org> (raw)
In-Reply-To: <20230515-refclk-v3-2-37c0b550f406@ti.com>
Quoting Jai Luthra (2023-06-15 04:55:36)
> TI's AM62 SoC can optionally provide two audio reference clocks
> (AUDIO_REFCLKx) to external peripherals.
>
> By default this reference clock is looped-back inside the SoC to a mux
> that goes to McASP AHCLK, but can optionally be enabled as an output to
> peripherals outside the SoC by setting a bit through CTRL_MMR registers.
>
> This bit only controls the direction of the clock, while the parent
> is a muxed input from sci-clk [1] which may be a configurable PLL or a
> master clock from one of the McASP instances.
>
> Link: http://downloads.ti.com/tisci/esd/latest/5_soc_doc/am62x/clocks.html#clocks-for-board0-device [1]
> Signed-off-by: Jai Luthra <j-luthra@ti.com>
> ---
Applied to clk-next
prev parent reply other threads:[~2023-06-16 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 11:55 [PATCH v3 0/2] clk: keystone: syscon-clk: Enable audio reference clock Jai Luthra
2023-06-15 11:55 ` [PATCH v3 1/2] dt-bindings: clock: Add binding documentation for TI Audio REFCLK Jai Luthra
2023-06-16 19:16 ` Stephen Boyd
2023-06-15 11:55 ` [PATCH v3 2/2] clk: keystone: syscon-clk: Add support for audio refclk Jai Luthra
2023-06-16 19:16 ` Stephen Boyd [this message]
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=7c1dbb26bb7693929bca45a7b28bf9c8.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-luthra@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).