From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755528AbcBHP6b (ORCPT ); Mon, 8 Feb 2016 10:58:31 -0500 Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:52833 "EHLO cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755354AbcBHP62 (ORCPT ); Mon, 8 Feb 2016 10:58:28 -0500 Subject: Re: [PATCH 05/11] drivers: pinctrl: add driver for Allwinner A64 SoC To: Rob Herring , Maxime Ripard 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> <20160204165151.GK4270@lukather> <20160208155405.GA4677@rob-hp-laptop> 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, Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , devicetree@vger.kernel.org From: Andre Przywara Organization: ARM Ltd. Message-ID: <56B8BB1A.8010705@arm.com> Date: Mon, 8 Feb 2016 15:58:18 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <20160208155405.GA4677@rob-hp-laptop> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 08/02/16 15:54, Rob Herring wrote: > On Thu, Feb 04, 2016 at 05:51:51PM +0100, Maxime Ripard wrote: >> 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. >>> >>> 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. > > I have to agree. Unless there is some agreement to move to another > naming scheme, then just follow the same pattern. If sunXi is just a > made up name outside of Allwinner to provide some logical grouping of > SoCs, then yes, that probably should not have been done. So I still don't like it, but will not waste my time or energy on that front. Maxime, do you want "allwinner,sun50i-a64" or would "allwinner,sunxi-a64" be OK as well? Cheers, Andre.