From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: devicetree@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
linux-sunxi@googlegroups.com, Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org, Chen-Yu Tsai <wens@csie.org>,
Rob Herring <robh+dt@kernel.org>,
Andre Przywara <andre.przywara@arm.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 2/7] clk: sunxi-ng: rename sun8i-h3 driver to sunxi-h3-h5
Date: Mon, 27 Feb 2017 13:24:44 +0100 [thread overview]
Message-ID: <20170227122444.6523qu4wwm4ihlfx@lukather> (raw)
In-Reply-To: <20170226011956.53581-3-icenowy@aosc.xyz>
[-- Attachment #1.1: Type: text/plain, Size: 739 bytes --]
Hi,
On Sun, Feb 26, 2017 at 09:19:51AM +0800, Icenowy Zheng wrote:
> As the CCU in the Allwinner H5 SoC is very similar to the one in H3,
> rename the H3 driver to sunxi-h3-h5 so that it can be extended with H5
> support.
>
> Trasitional header symlinks are created, to ensure current device tree
> files which included sun8i-h3-ccu.h can compile.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
Just like for the R40, I wonder whether this is needed at all. We have
a lot of other drivers that we don't have to rename to support new
SoCs. This is kind of weird to make an exception for this one only.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2017-02-27 12:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 1:19 [PATCH v5 0/7] Allwinner H5 and Orange Pi PC2 support Icenowy Zheng
2017-02-26 1:19 ` [PATCH v5 1/7] arm64: allwinner: Kconfig: add essential pinctrl driver for H5 Icenowy Zheng
2017-02-27 8:25 ` Maxime Ripard
2017-02-26 1:19 ` [PATCH v5 2/7] clk: sunxi-ng: rename sun8i-h3 driver to sunxi-h3-h5 Icenowy Zheng
2017-02-26 9:52 ` Rask Ingemann Lambertsen
2017-02-26 14:57 ` Icenowy Zheng
2017-02-27 12:24 ` Maxime Ripard [this message]
2017-02-26 1:19 ` [PATCH v5 3/7] clk: sunxi-ng: add support for Allwinner H5 SoC Icenowy Zheng
2017-02-26 1:19 ` [PATCH v5 4/7] ARM: dts: sun8i: convert H3 dtsi to use new sunxi-h3-h5 binding header Icenowy Zheng
2017-02-26 1:19 ` [PATCH v5 5/7] arm: dts: sun8i: split Allwinner H3 .dtsi Icenowy Zheng
2017-02-26 3:46 ` Chen-Yu Tsai
2017-02-27 8:20 ` Marc Zyngier
2017-02-26 1:19 ` [PATCH v5 6/7] arm64: dts: allwinner: add Allwinner H5 .dtsi Icenowy Zheng
2017-02-26 8:55 ` Rask Ingemann Lambertsen
2017-02-26 9:00 ` Chen-Yu Tsai
2017-02-26 14:54 ` Icenowy Zheng
2017-02-26 1:19 ` [PATCH v5 7/7] arm64: dts: sunxi: add support for the Orange Pi PC 2 board Icenowy Zheng
2017-02-26 9:19 ` Rask Ingemann Lambertsen
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=20170227122444.6523qu4wwm4ihlfx@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.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 \
--cc=will.deacon@arm.com \
/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