From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Mon, 10 Aug 2015 21:47:09 -0600 Subject: [U-Boot] [PATCH v3 06/11] arm: rpi: Enable device tree control for Rasberry Pi In-Reply-To: <1438954951-13329-7-git-send-email-sjg@chromium.org> References: <1438954951-13329-1-git-send-email-sjg@chromium.org> <1438954951-13329-7-git-send-email-sjg@chromium.org> Message-ID: <55C9703D.9040200@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 08/07/2015 07:42 AM, Simon Glass wrote: > Enable device tree control so that we can use driver model fully and avoid > using platform data. I'm still not convinced about this change. Re: the commit message about: What about the driver model is not being fully used without DT? Overall: What advantage does using DT have to either a developer or an end-user? I don't believe this patch fixes and bugs or enables any new features for an end-user. >From the maintainer perspective: It seems to me that it's far simpler to have a tiny struct for each device in the C code than to pull in a whole slew of DT parsing cruft just to work out the same struct at run-time. As such, this patch can only make it harder to maintain the code since there's more of it, and it's more complex. I just don't see the advantage of switching to DT for U-Boot control.