Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757106Ab1FUSmg (ORCPT ); Tue, 21 Jun 2011 14:42:36 -0400 Received: from mail-gy0-f174.google.com ([209.85.160.174]:49788 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754679Ab1FUSmf convert rfc822-to-8bit (ORCPT ); Tue, 21 Jun 2011 14:42:35 -0400 MIME-Version: 1.0 In-Reply-To: <4E00E3D2.6050602@firmworks.com> References: <1308410354-21387-1-git-send-email-shawn.guo@linaro.org> <1308410354-21387-2-git-send-email-shawn.guo@linaro.org> <20110618161934.GH8195@ponder.secretlab.ca> <20110619073000.GA23171@S2100-06.ap.freescale.net> <20110621135558.GB9228@S2101-09.ap.freescale.net> <4E00E3D2.6050602@firmworks.com> From: Grant Likely Date: Tue, 21 Jun 2011 12:42:14 -0600 X-Google-Sender-Auth: 3GE1LX9lgB0xNLokmrUpUORYhZM Message-ID: Subject: Re: [PATCH 1/3] serial/imx: add device tree support To: Mitch Bradley Cc: Shawn Guo , patches@linaro.org, netdev@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, Jason Liu , linux-kernel@vger.kernel.org, Jeremy Kerr , Sascha Hauer , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1295 Lines: 23 On Tue, Jun 21, 2011 at 12:32 PM, Mitch Bradley wrote: > I wonder if it makes sense to create a new device node "/linux-devices" to express a desired mapping from device nodes to /dev entries? ?The properties could be the names of device special files and the values the corresponding node phandles. I've been trying /really/ hard to avoid doing something like that because a lot of the time the desired Linux dev name is a implementation detail, and a potentially unstable one at that. If Linux requires certain devices to have certain names because that is how it hooks up clocks (which is the current situation on some platforms), then I'd rather have Linux encode a lookup of the preferred name, at least until the that particular implementation detail goes away. As for enumerating devices, I don't think this is a Linux-specific thing. In this case it is entirely reasonable to want to say /this node/ is the second serial port, and /that node/ is the third, which is information needed regardless of the client OS. g. -- 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/