From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-sunxi@googlegroups.com, devicetree@vger.kernel.org,
Chen-Yu Tsai <wens@csie.org>
Subject: Re: [PATCH 2/3] clk: sunxi-ng: add support for PRCM CCUs
Date: Thu, 2 Mar 2017 15:09:31 +0100 [thread overview]
Message-ID: <20170302140931.tq3vpncln6giyjpr@lukather> (raw)
In-Reply-To: <20170301152236.MUXmRgOe@smtp1m.mail.yandex.net>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Wed, Mar 01, 2017 at 08:22:13PM +0800, Icenowy Zheng wrote:
> > I'm a bit worried by that to be honest. You claim to support the A31,
> > yet jugdging by the current state of that code you never actually
> > tested it on that SoC.
> >
> > What makes you say that the PRCM clocks are the same for the H3 and
> > A64? We have to be sure, otherwise we might not be able to get the DT
> > binding right from the very beginning, and we might not be able to fix
> > it later.
>
> In fact, if we worry about this, we shouldn't make r-ccu, as
> dedicated clocks are more easy to fix.
>
> For newer SoCs' PRCM, we never have enough documents, and Allwinner
> have said that they cannot provide it. (I asked them for this.)
>
> The best solution is to implement mature enough dedicated clocks
> before we convert to ccu.
What do you mean by dedicated clocks?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next parent reply other threads:[~2017-03-02 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170301152236.MUXmRgOe@smtp1m.mail.yandex.net>
2017-03-02 14:09 ` Maxime Ripard [this message]
[not found] ` <2899221488467633@web38j.yandex.ru>
2017-03-03 14:51 ` [linux-sunxi] " maxime.ripard
[not found] <20170301041541.24388-1-icenowy@aosc.xyz>
[not found] ` <20170301041541.24388-3-icenowy@aosc.xyz>
2017-03-01 10:47 ` Maxime Ripard
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=20170302140931.tq3vpncln6giyjpr@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®