Devicetree
 help / color / mirror / Atom feed
From: Icenowy Zheng <icenowy-ymACFijhrKM@public.gmane.org>
To: "maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org"
	<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	linux-kernel
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org"
	<linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>
Subject: Re: Re: [PATCH 2/3] clk: sunxi-ng: add support for PRCM CCUs
Date: Thu, 02 Mar 2017 23:13:53 +0800	[thread overview]
Message-ID: <2899221488467633@web38j.yandex.ru> (raw)
In-Reply-To: <20170302140931.tq3vpncln6giyjpr@lukather>



02.03.2017, 22:09, "Maxime Ripard" <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>:
> 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?

The legacy form of clocks.

>
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
>
> --
> You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2017-03-02 15:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 12:22 [PATCH 2/3] clk: sunxi-ng: add support for PRCM CCUs Icenowy Zheng
     [not found] ` <20170301152236.MUXmRgOe-3YhIAYTWRJA0PDqKvflMoHmW9unr2Ajn@public.gmane.org>
2017-03-02 14:09   ` Maxime Ripard
2017-03-02 15:13     ` Icenowy Zheng [this message]
     [not found]       ` <2899221488467633-+LZv1VrpgWBxpj1cXAZ9Bg@public.gmane.org>
2017-03-03 14:51         ` maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8
  -- strict thread matches above, loose matches on Subject: below --
2017-03-01 12:17 Icenowy Zheng
     [not found] ` <20170301152220.MEgmqtKw-8ttnI0T0xQU0PDqKvflMoHmW9unr2Ajn@public.gmane.org>
2017-03-02 14:08   ` Maxime Ripard
2017-03-02 15:13     ` Icenowy Zheng
     [not found]       ` <3232491488467598-MaJ972yi255xpj1cXAZ9Bg@public.gmane.org>
2017-03-03 14:48         ` 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=2899221488467633@web38j.yandex.ru \
    --to=icenowy-ymacfijhrkm@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=wens-jdAy2FN1RRM@public.gmane.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