From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [RFC PATCH 4/9] clk: sunxi-ng: support R40 SoC
Date: Thu, 23 Feb 2017 16:20:28 -0800 [thread overview]
Message-ID: <20170224002028.miupa6dzefgxbfse@lukather> (raw)
In-Reply-To: <20170222231738.HXRSmi86@smtp1o.mail.yandex.net>
On Wed, Feb 22, 2017 at 01:54:58PM +0800, Icenowy Zheng wrote:
>
> 2017?2?22? 07:03? Maxime Ripard <maxime.ripard@free-electrons.com>???
> >
> > Hi,
> >
> > On Sat, Feb 18, 2017 at 01:37:17AM +0800, Icenowy Zheng wrote:
> > > Allwinner R40 SoC have a clock controller module in the style of the
> > > SoCs beyond sun6i, however, it's more rich and complex.
> > >
> > > Add support for it.
> > >
> > > As the user manual is still not available, this driver is made with
> > > knowledge from clk-sun8iw11.c in the BSP kernel source.
> >
> > Missing SoB.
> >
> > Why are some patches tagged as RFC and some don't?
>
> There's still no open User Manual for R40, so I tagged CCU-related
> drivers RFC.
>
> Pinctrl driver can be written with the datasheet draft, which is
> available now.
>
> For USB we have never user manual so everything is educated guess --
> so it's not RFC.
It's still kind of weird to mix and match patches with and without RFC
tags.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170223/c982a9c2/attachment.sig>
next parent reply other threads:[~2017-02-24 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170222231738.HXRSmi86@smtp1o.mail.yandex.net>
2017-02-24 0:20 ` Maxime Ripard [this message]
2017-02-28 15:50 ` [linux-sunxi] Re: [RFC PATCH 4/9] clk: sunxi-ng: support R40 SoC Chen-Yu Tsai
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=20170224002028.miupa6dzefgxbfse@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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