From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tero Kristo <t-kristo@ti.com>, Mike Turquette <mturquette@linaro.org>
Cc: Benoit Cousson <bcousson@baylibre.com>,
Tony Lindgren <tony@atomide.com>, <devicetree@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/3] clk: Add clock driver for DRA7 ATL (Audio Tracking Logic)
Date: Thu, 24 Apr 2014 12:14:32 +0300 [thread overview]
Message-ID: <5358D5F8.3010401@ti.com> (raw)
In-Reply-To: <1396446907-20383-1-git-send-email-peter.ujfalusi@ti.com>
Hi Mike,
On 04/02/2014 04:55 PM, Peter Ujfalusi wrote:
> Hi,
>
> Audio Tracking Logic is designed to be used by HD Radio
> applications to synchronize the audio output clocks to the
> baseband clock. ATL can be also used to track errors between
> two reference clocks (BWS, AWS) and generate a modulated
> clock output which averages to some desired frequency.
>
> To be able to integrate the ATL provided clocks to the clock tree we need
> two types of DT binding:
> - DT clock nodes to represent the ATL clocks towards the CCF
> - binding for the ATL IP itself which is going to handle the hw
> configuration
>
> The reason for this type of setup is that ATL itself is a separate device
> in the SoC, it has it's own address space and clock domain. Other IPs can
> use the ATL generated clock as their functional clock (McASPs for example)
> and external components like audio codecs can also use the very same clock
> as their MCLK.
>
> With setup pm_runtime can handle the ATL clock on demand of it's use and
> all the IP which needs ATL clock can be sure that it is enabled for them.
>
> The first patch fixes the name of atl clkin3 node in dtsi file.
Can you take a look at this series?
Thanks,
Péter
>
> Regards,
> Peter
> ---
> Peter Ujfalusi (3):
> ARM: dts: dra7xx-clocks: Correct name for atl clkin3 clock
> clk: Driver for DRA7 ATL (Audio Tracking Logic)
> ARM: DTS: dra7/dra7xx-clocks: ATL related changes
>
> .../devicetree/bindings/clock/ti/dra7-atl.txt | 97 +++++++
> arch/arm/boot/dts/dra7.dtsi | 11 +
> arch/arm/boot/dts/dra7xx-clocks.dtsi | 38 +--
> drivers/clk/ti/Makefile | 3 +-
> drivers/clk/ti/clk-7xx.c | 2 +-
> drivers/clk/ti/clk-dra7-atl.c | 313 +++++++++++++++++++++
> include/dt-bindings/clk/ti-dra7-atl.h | 40 +++
> 7 files changed, 483 insertions(+), 21 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/clock/ti/dra7-atl.txt
> create mode 100644 drivers/clk/ti/clk-dra7-atl.c
> create mode 100644 include/dt-bindings/clk/ti-dra7-atl.h
>
prev parent reply other threads:[~2014-04-24 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 13:55 [PATCH 0/3] clk: Add clock driver for DRA7 ATL (Audio Tracking Logic) Peter Ujfalusi
2014-04-02 13:55 ` [PATCH 1/3] ARM: dts: dra7xx-clocks: Correct name for atl clkin3 clock Peter Ujfalusi
2014-04-02 13:55 ` [PATCH 2/3] clk: Driver for DRA7 ATL (Audio Tracking Logic) Peter Ujfalusi
2014-04-02 13:55 ` [PATCH 3/3] ARM: DTS: dra7/dra7xx-clocks: ATL related changes Peter Ujfalusi
2014-04-24 9:14 ` Peter Ujfalusi [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=5358D5F8.3010401@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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