Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754417Ab1BBPiK (ORCPT ); Wed, 2 Feb 2011 10:38:10 -0500 Received: from mail-iy0-f174.google.com ([209.85.210.174]:65419 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754394Ab1BBPiI (ORCPT ); Wed, 2 Feb 2011 10:38:08 -0500 Date: Wed, 2 Feb 2011 08:38:03 -0700 From: Grant Likely To: Thomas Chou Cc: Dmitry Torokhov , linux-kernel@vger.kernel.org, nios2-dev@sopc.et.ntust.edu.tw, linux-input@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, Walter Goossens Subject: Re: [PATCH v2] altera_ps2: Add devicetree support Message-ID: <20110202153803.GC20275@angua.secretlab.ca> References: <20110117220415.GB17963@angua.secretlab.ca> <1295848693-28472-1-git-send-email-thomas@wytron.com.tw> <20110202043121.GF29148@angua.secretlab.ca> <4D4944AA.5040900@wytron.com.tw> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D4944AA.5040900@wytron.com.tw> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1463 Lines: 36 On Wed, Feb 02, 2011 at 07:48:58PM +0800, Thomas Chou wrote: > On 02/02/2011 12:31 PM, Grant Likely wrote: > >>+static const struct of_device_id altera_ps2_match[] = { > >>+ { .compatible = "altr,ps2-1.0", }, > > > >I thought I had seen 'altera' instead of an abbreviation being used in > >a previous patch. I don't care much whether 'altr' or 'altera' is > >used, but I'd like to know that there is consensus from the Altera > >users so that all the drivers use the same prefix. > > > > We had discussed on nios2-dev mailing list, and decided to use > 'altr' as Walter suggested that it saves space. > > About the documentation on dts binding, shall we have a single > altera.txt to describe all Altera related binding, and opencores.txt > to describe all OpenCores binding? Or separate file for each core in > its driver class? Since I'm reorganizing the binding documentation to reflect subsystems (bindings/spi, bindings/i2c, bindings/powerpc, etc) I'd prefer to see a separate file for each type of core. Eventually, I'd like to define a record format for documenting bindings that can generate searchable and crosslinked output, but I've not spent any time looking at that seriously yet. g. > > - Thomas -- 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/