From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758699AbaDXQGX (ORCPT ); Thu, 24 Apr 2014 12:06:23 -0400 Received: from top.free-electrons.com ([176.31.233.9]:41070 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757450AbaDXQGS (ORCPT ); Thu, 24 Apr 2014 12:06:18 -0400 Date: Thu, 24 Apr 2014 13:05:45 -0300 From: Ezequiel Garcia To: Arnd Bergmann , Ley Foon Tan Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, lftan.linux@gmail.com, cltang@codesourcery.com Subject: Re: [PATCH 19/28] nios2: Device tree support Message-ID: <20140424160545.GE1735@arch.cereza> References: <1397824031-4892-1-git-send-email-lftan@altera.com> <1397824031-4892-16-git-send-email-lftan@altera.com> <201404221542.16481.arnd@arndb.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201404221542.16481.arnd@arndb.de> User-Agent: Mutt/1.5.22 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Apr 22, Arnd Bergmann wrote: > On Friday 18 April 2014, Ley Foon Tan wrote: > > Are these all synthesized devices, or is there also some hardwired > logic? It often makes sense to split out the reusable parts into > a separate .dtsi file that gets included by every implementation. > In case you are not aware of this, devicetree files for Nios-II SoCs are produced through an automated tool calle sopc2dts: http://www.alterawiki.com/wiki/Sopc2dts http://git.rocketboards.org/sopc-tools.git/ You feed it with a sopcinfo file (AFAIK, Altera's specific format) and you obtain a full-fledged devicetree source file. Usually it works out-of-the-box, although I like to go over it and fix ranges, whitespaces, and do some cleaning. So I'm wondering -given we have such superb tool- why would we want to include the devicetree source's in the kernel? First, we'll be only supporting a *specific* configuration. Second, the dts is trivially easy to obtain. The binding documentation should be enough specification, and there's no need for further reference or examples. -- Ezequiel García, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com