From: Jerome Brunet <jbrunet@baylibre.com>
To: Jian Hu <jian.hu@amlogic.com>, Neil Armstrong <narmstrong@baylibre.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
Carlo Caione <carlo@caione.org>, Rob Herring <robh@kernel.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Yixun Lan <yixun.lan@amlogic.com>,
Jianxin Pan <jianxin.pan@amlogic.com>,
linux-clk@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] clk: meson-g12a: Add AO Clock controller driver
Date: Mon, 27 Aug 2018 15:07:46 +0200 [thread overview]
Message-ID: <89b058a7bba26058fab95dea01155221dbb642ce.camel@baylibre.com> (raw)
In-Reply-To: <fff1f982-c9f3-8aa4-b108-6c0998827e79@amlogic.com>
On Fri, 2018-08-24 at 21:34 +0800, Jian Hu wrote:
> >
>
> I am confued about aoclk81's parent clocks.
>
> I can not get the example of axg audio clock driver, Could you provide
> the link? Had it merged into clk-meson.git?
Yes and mainline as well : drivers/clk/meson/axg-audio.c
Basically this driver is creating bypass input clocks (audio_pclk, mst_in[0-9],
etc...) .
This allows to collect input clocks from DT (like any consumer should) will
keeping constant in the controller clock tree.
From what I've seen of your controller drivers, the EE controller should have
one input, the AO should have 3.
next prev parent reply other threads:[~2018-08-27 13:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 9:54 [PATCH 0/2] clk: meson-g12a: Add AO clock " Jian Hu
2018-08-10 9:54 ` [PATCH 1/2] dt-bindings: clk: meson-g12a: Add G12A AO Clock Bindings Jian Hu
2018-08-14 20:48 ` Rob Herring
2018-08-15 5:35 ` Jian Hu
2018-08-10 9:54 ` [PATCH 2/2] clk: meson-g12a: Add AO Clock controller driver Jian Hu
2018-08-14 12:40 ` Jerome Brunet
2018-08-24 13:34 ` Jian Hu
2018-08-27 13:07 ` Jerome Brunet [this message]
2018-08-28 3:35 ` Jian Hu
2018-09-14 8:33 ` Jerome Brunet
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=89b058a7bba26058fab95dea01155221dbb642ce.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=jian.hu@amlogic.com \
--cc=jianxin.pan@amlogic.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=narmstrong@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=yixun.lan@amlogic.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
all inboxes | Powered by JetHome®