[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdY4=SSZQRQY_ydcsv-S8ezrYbzp2rdD4qRuHkF8oowOEw@mail.gmail.com>
Date: Tue, 30 Jun 2015 08:26:45 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Matthias Brugger <matthias.bgg@...il.com>
Cc: Daniel Kurtz <djkurtz@...omium.org>,
Eddie Huang <eddie.huang@...iatek.com>,
Sascha Hauer <s.hauer@...gutronix.de>,
"open list:OPEN FIRMWARE AND..." <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v3 2/2] arm64: dts: mt8173: Add I2C device node
On Fri, Jun 12, 2015 at 7:13 PM, Matthias Brugger
<matthias.bgg@...il.com> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists