From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: Vishnu Patekar <vishnupatekar0510@gmail.com>,
emilio@elopez.com.ar, sboyd@codeaurora.org, wens@csie.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] clk: sunxi: predivider handling for factors clock
Date: Tue, 31 May 2016 10:59:15 +0200 [thread overview]
Message-ID: <20160531085915.GK4908@lukather> (raw)
In-Reply-To: <20160531103905.faf5e2b80d60d46c8757ad1c@free.fr>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
On Tue, May 31, 2016 at 10:39:05AM +0200, Jean-Francois Moine wrote:
> On Mon, 30 May 2016 20:45:32 +0200
> Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
>
> > I went over all the A83T clocks, and most of them could be
> > covered. The issue only lies in the PLLs and their additional 1-bit
> > dividers.
> >
> > If we just choos to ignore (one of) them, it should be pretty trivial
> > to implement with the current clock classes we have.
>
> Hi Maxime,
>
> I already did the job for all the A83T clocks.
> It is not fully tested yet, but, to be sure we are on the same way,
> I am sending a RFC series.
Awesome, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-05-31 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 16:47 [PATCH v2] sunxi factors clock predivider handling Vishnu Patekar
2016-04-19 16:47 ` [PATCH v2] clk: sunxi: predivider handling for factors clock Vishnu Patekar
2016-04-25 14:51 ` Chen-Yu Tsai
2016-04-26 17:55 ` Vishnu Patekar
2016-05-02 11:13 ` Maxime Ripard
[not found] ` <CAEzqOZvnKKNs_sXUJrwTykA5mzwKMg+HpaFcKgBTFr+utT4qQg@mail.gmail.com>
2016-05-30 18:45 ` Maxime Ripard
2016-05-31 8:39 ` Jean-Francois Moine
2016-05-31 8:59 ` Maxime Ripard [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=20160531085915.GK4908@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=emilio@elopez.com.ar \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=moinejf@free.fr \
--cc=sboyd@codeaurora.org \
--cc=vishnupatekar0510@gmail.com \
--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