public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: icenowy@aosc.xyz (Icenowy Zheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] clk: sunxi-ng: add support for V3s CCU
Date: Wed, 18 Jan 2017 01:08:14 +0800	[thread overview]
Message-ID: <5926181484672894@web12g.yandex.ru> (raw)
In-Reply-To: <20170117090456.fgw6lpqgurwwcczj@lukather>



17.01.2017, 17:05, "Maxime Ripard" <maxime.ripard@free-electrons.com>:
> Hi,
>
> On Tue, Jan 17, 2017 at 02:01:14AM +0800, Icenowy Zheng wrote:
>> ?V3s has a similar but cut-down CCU to H3.
>>
>> ?Add support for it.
>>
>> ?Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
>> ?---
>
> Output from checkpatch:
> total: 5 errors, 2 warnings, 3 checks, 857 lines checked

I remembered some errors' code is directly derived from ccu-sun8i-h3.c,
so I generated a patch file for "clk: sunxi-ng: Add H3 clocks" and run
checkpatch on it:
total: 4 errors, 5 warnings, 1159 lines checked

Should I still get all errors fixed?

>
>> ?I think I should make a comparsion between V3s and H3 CCU here:
>> ?(I won't mention the missing/added clocks here, only list conflicting clocks)
>
> That should be in your commit log.
>
>> ?- "bus-ehci0" is at different bit (The bit that is "bus-ehci0" on V3s is
>> ???"bus-ehci2" on H3)
>> ?- The mux of "ce" is different. (According the view at V3s datasheet by the
>> ???author of sun4i-ss, V3s may have sun4i-ss, not sun8i-ce)
>> ?- The mux of "de" is different. (V3s do not have "pll-de", but it can mux "de"
>> ???to "pll-video")
>> ?- Clocks about CSI largely differs. (As V3s is designed as a camera SoC, and
>> ???it have an extra "pll-isp")
>
> OK.
>
> Thanks,
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com

  reply	other threads:[~2017-01-17 17:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 18:01 [PATCH v2 1/4] arm: sunxi: add support for V3s SoC Icenowy Zheng
2017-01-16 18:01 ` [PATCH v2 2/4] clk: sunxi-ng: add support for V3s CCU Icenowy Zheng
2017-01-17  9:04   ` Maxime Ripard
2017-01-17 17:08     ` Icenowy Zheng [this message]
2017-01-19 15:39       ` Maxime Ripard
2017-01-16 18:01 ` [PATCH v2 3/4] ARM: dts: sunxi: add dtsi file for V3s SoC Icenowy Zheng
2017-01-16 18:01 ` [PATCH v2 4/4] ARM: dts: sunxi: add support for Lichee Pi Zero board Icenowy Zheng
2017-01-17  9:05 ` [PATCH v2 1/4] arm: sunxi: add support for V3s SoC Maxime Ripard
2017-01-17 16:52   ` Icenowy Zheng

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=5926181484672894@web12g.yandex.ru \
    --to=icenowy@aosc.xyz \
    --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