From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965880AbcBDS5n (ORCPT ); Thu, 4 Feb 2016 13:57:43 -0500 Received: from down.free-electrons.com ([37.187.137.238]:40342 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S965120AbcBDS5X (ORCPT ); Thu, 4 Feb 2016 13:57:23 -0500 Date: Thu, 4 Feb 2016 17:51:51 +0100 From: Maxime Ripard To: Andre Przywara Cc: Karsten Merker , Chen-Yu Tsai , linux-sunxi@googlegroups.com, Arnd Bergmann , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Linus Walleij , Vishnu Patekar , linux-gpio@vger.kernel.org, Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , devicetree@vger.kernel.org Subject: Re: [PATCH 05/11] drivers: pinctrl: add driver for Allwinner A64 SoC Message-ID: <20160204165151.GK4270@lukather> References: <1454348370-3816-1-git-send-email-andre.przywara@arm.com> <1454348370-3816-6-git-send-email-andre.przywara@arm.com> <20160201182754.GA14737@excalibur.cnev.de> <56AFE0EC.8080207@arm.com> <20160202100046.GM4652@lukather> <56B0DF26.10203@arm.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45wMVEkw4XUbiYON" Content-Disposition: inline In-Reply-To: <56B0DF26.10203@arm.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --45wMVEkw4XUbiYON Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Andre, On Tue, Feb 02, 2016 at 04:53:58PM +0000, Andre Przywara wrote: > > So, droping it in the filenames, why not. But I'd really like to keep > > the same compatible scheme. >=20 > And I still don't get this: in the DT compatible scheme we always have a > vendor prefix, so allwinner,a64 is surely not a mysterious ARM Ltd. core > or a new Apple SoC. Instead it is the A64 from Allwinner, full stop. So > why should we add an arbitrary and confusing sun50i naming to it (when > it actually should be more like "sun8i-a64"). I don't decide on their marketing names. And I know you want to start anew with the arm64 SoCs, but the truth is, you don't. Most of the compatibles in the DTSI are from earlier SoCs, and we have to keep that legacy and remain consistent with it. With all the good and bad things a legacy imply. Maxime --=20 Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com --45wMVEkw4XUbiYON Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJWs4GnAAoJEBx+YmzsjxAg2TUP/j6w12l0vR/opYqJsd21DLUh s5pXrZVaBJqmkZQd3ZdAxxmoC6Pa1WkJWtKBE67OHjPGtUFE/cZJzDK/MMfM4+vH 3qtVMahQ/yVMyKoqig7KlsZPLrOOV21JCkFk2U7/+kNI07z19FtQMgrD0sK5cXoG PlwxJNyn7a2QZK4WzqPfqjtdjlqZX3n3vlRjpwOxY3eAKXVbVL+ad+cfDo57obix H0IX8MNABBtHuXxosBpL97fq5VOlRYpp3SstcEORWcbptC/mQvS2TFM8oihfDq1D R+HyyNrnxNmu2QvZ5k0L7yVpZ9uwZuTjvW++oH7/fpDr98u7rd50TUvruO0P+VwF 6hzjm9Cxt2Epp44wbKZK9tJ7Ks0Ia2by4qiG5ik+W4GdWedSUfY5nXWuiJSSFLT9 PZSk+UnXAWQfFMG+Yx24VKmhki9cRFw200SwDis/0i6s4tqisy6gjooGhzMojHYF 0YAEDUIhRpBZFIyboYyXdC0ZgP8mriBXUgFVWsb5tay6bOeSzWvSqGOumj2kzGEz FZSUX5Y03LGUj/0c0kgQfV/aBcSGevyQJcFYm38USPhdOJLPX2pi21rVnMnt61Ul TKDKcCZ5pnhwliahXQbHI008xtR6D4RNDTY41OtyY61BveJeFu2PxjEELP3nschb MEMWO/mjJ2Zjdx52tzNC =uGiF -----END PGP SIGNATURE----- --45wMVEkw4XUbiYON--