From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757319AbcFAGaP (ORCPT ); Wed, 1 Jun 2016 02:30:15 -0400 Received: from conssluserg-06.nifty.com ([210.131.2.91]:28134 "EHLO conssluserg-06.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753965AbcFAGaN (ORCPT ); Wed, 1 Jun 2016 02:30:13 -0400 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-06.nifty.com u516U3VR008930 X-Nifty-SrcIP: [209.85.161.181] MIME-Version: 1.0 In-Reply-To: <4992506.m4GEHIOqdc@wuerfel> References: <1464682628-12163-1-git-send-email-yamada.masahiro@socionext.com> <4992506.m4GEHIOqdc@wuerfel> Date: Wed, 1 Jun 2016 15:30:03 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] ARM: uniphier: drop code for old DT binding From: Masahiro Yamada To: Arnd Bergmann Cc: linux-arm-kernel , arm@kernel.org, Russell King , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Arnd. 2016-05-31 18:21 GMT+09:00 Arnd Bergmann : > On Tuesday, May 31, 2016 5:17:08 PM CEST Masahiro Yamada wrote: >> Commit 307d40c56b0c ("ARM: uniphier: rework SMP code to support new >> System Bus binding") added a new DT binding for SMP code, but still >> kept old code for the backward compatibility. >> >> Linux 4.6 was out with both bindings supported, so it should not >> hurt to drop the old code now. >> >> Signed-off-by: Masahiro Yamada >> > > That explanation is in general not sufficient. Are you sure that > nobody is shipping a machine with their own dts file that is not > merged upstream, and that there are no bootloaders that have a > hardcoded dtb file that we need to support indefinitely? > I have to confess that almost no one (except me) uses this upstreamed code directly. It can boot, but it is almost useless for practical uses (at least for production level) because it still lacks lots of drivers. Our products based on ARM 32bit SoCs were shipped with old kernel (without device tree) that were never upstreamed. Socionext is now trying to change the development procedure and the situation will be much better for ARM64 SoC products; it will be more community-based development, although they are not shipped yet. So, the answer is, nobody is shipping ARM32 products using this upstream code. Device Tree is not used in the first place. (But, I still believe I should keep upstreaming.) -- Best Regards Masahiro Yamada From mboxrd@z Thu Jan 1 00:00:00 1970 From: yamada.masahiro@socionext.com (Masahiro Yamada) Date: Wed, 1 Jun 2016 15:30:03 +0900 Subject: [PATCH] ARM: uniphier: drop code for old DT binding In-Reply-To: <4992506.m4GEHIOqdc@wuerfel> References: <1464682628-12163-1-git-send-email-yamada.masahiro@socionext.com> <4992506.m4GEHIOqdc@wuerfel> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Arnd. 2016-05-31 18:21 GMT+09:00 Arnd Bergmann : > On Tuesday, May 31, 2016 5:17:08 PM CEST Masahiro Yamada wrote: >> Commit 307d40c56b0c ("ARM: uniphier: rework SMP code to support new >> System Bus binding") added a new DT binding for SMP code, but still >> kept old code for the backward compatibility. >> >> Linux 4.6 was out with both bindings supported, so it should not >> hurt to drop the old code now. >> >> Signed-off-by: Masahiro Yamada >> > > That explanation is in general not sufficient. Are you sure that > nobody is shipping a machine with their own dts file that is not > merged upstream, and that there are no bootloaders that have a > hardcoded dtb file that we need to support indefinitely? > I have to confess that almost no one (except me) uses this upstreamed code directly. It can boot, but it is almost useless for practical uses (at least for production level) because it still lacks lots of drivers. Our products based on ARM 32bit SoCs were shipped with old kernel (without device tree) that were never upstreamed. Socionext is now trying to change the development procedure and the situation will be much better for ARM64 SoC products; it will be more community-based development, although they are not shipped yet. So, the answer is, nobody is shipping ARM32 products using this upstream code. Device Tree is not used in the first place. (But, I still believe I should keep upstreaming.) -- Best Regards Masahiro Yamada