Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752518AbbF3G05 (ORCPT ); Tue, 30 Jun 2015 02:26:57 -0400 Received: from mail-oi0-f51.google.com ([209.85.218.51]:35235 "EHLO mail-oi0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751817AbbF3G0q (ORCPT ); Tue, 30 Jun 2015 02:26:46 -0400 MIME-Version: 1.0 In-Reply-To: <1863259.t4daGE7nbQ@ubix> References: <1434101229-32695-1-git-send-email-eddie.huang@mediatek.com> <1434101229-32695-3-git-send-email-eddie.huang@mediatek.com> <1863259.t4daGE7nbQ@ubix> Date: Tue, 30 Jun 2015 08:26:45 +0200 Message-ID: Subject: Re: [PATCH v3 2/2] arm64: dts: mt8173: Add I2C device node From: Linus Walleij To: Matthias Brugger Cc: Daniel Kurtz , Eddie Huang , Sascha Hauer , "open list:OPEN FIRMWARE AND..." , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , linux-mediatek@lists.infradead.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 839 Lines: 21 On Fri, Jun 12, 2015 at 7:13 PM, Matthias Brugger wrote: > In the future when all the device drivers are implemented, this gets you a > really huge dtsi. AFAIK this can cause a somewhat long parsing time of the dtb > when booting the system. Boot time claims need to be backed up with ftrace logs or something. One of the arguments against device tree in the beginning was parse time and then we made measurements and it proved moot. However being unable to manage the dts[i] sources is a valid argument for simplifying and splitting up stuff. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/