From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Daney Subject: Re: [PATCH 05/44] mfd: as3722: Drop reference to pm_power_off from devicetree bindings Date: Tue, 07 Oct 2014 09:59:29 -0700 Message-ID: <54341BF1.9020001@gmail.com> References: <1412659726-29957-1-git-send-email-linux@roeck-us.net> <1412659726-29957-6-git-send-email-linux@roeck-us.net> <543412F7.8040909@landley.net> <20141007163131.GE28835@roeck-us.net> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=IQmBW/ecm0PlBOnNT1tmvTyGhPpEN+BG3k+K+8XnQAY=; b=pWBorCMq1eXduZiVcf3gaU7QHS/EPu8ZXHWt+PfF9KdK7ozE3k2wh89+u0Q8g8ikqp EQn+BXYNgkI3hRDGELWv+3nLHjQRlfe5O9Vb7vY1STmktBCVFAP+OFAKX0iRnva2EMus JfhaO00M36epbU0e4sCCgGOfCQw2xnM2O2jpfXFxCVdmqPycGvCCW9FgM1HTuS7sr9cB O64d7T/vj6muGVnt2VytRs6qAo+IFyfJul4+FqDxnqY7hEVUfD3Nhf4AypscddyjZTBL u64KIGIicQavYjyK29H/pF4hUkOr006m6zf0ypKh6fXqLkjVnW/y42h5kYgh3AJ3wOtG Ld4Q== In-Reply-To: <20141007163131.GE28835@roeck-us.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: driverdev-devel-bounces@linuxdriverproject.org Sender: "devel" Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Guenter Roeck , Rob Landley Cc: linux-m32r-ja@ml.linux-m32r.org, linux-mips@linux-mips.org, linux-efi@vger.kernel.org, linux-ia64@vger.kernel.org, linux-xtensa@linux-xtensa.org, Mark Rutland , devel@driverdev.osuosl.org, linux-s390@vger.kernel.org, lguest@lists.ozlabs.org, linux-c6x-dev@linux-c6x.org, linux-hexagon@vger.kernel.org, linux-sh@vger.kernel.org, linux-acpi@vger.kernel.org, Pawel Moll , xen-devel@lists.xenproject.org, devicetree@vger.kernel.org, user-mode-linux-devel@lists.sourceforge.net, linux-pm@vger.kernel.org, adi-buildroot-devel@lists.sourceforge.net, linux-m68k@lists.linux-m68k.org, linux-am33-list@redhat.com, linux-tegra@vger.kernel.org, openipmi-developer@lists.sourceforge.net, linux-metag@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-parisc@vger.kernel.org, linux-cris-kernel@axis.com, linux-kernel@vger.kernel.org, Rob On 10/07/2014 09:31 AM, Guenter Roeck wrote: > On Tue, Oct 07, 2014 at 11:21:11AM -0500, Rob Landley wrote: >> On 10/07/14 00:28, Guenter Roeck wrote: >>> Devicetree bindings are supposed to be operating system independent >>> and should thus not describe how a specific functionality is implemented >>> in Linux. >> >> So your argument is that linux/Documentation/devicetree/bindings should >> not be specific to Linux. Merely hosted in the Linux kernel source >> repository. >> >> Well that's certainly a point of view. >> > Not specifically my argument, really, and nothing new either. But, yes, I do > think that devicetree bindings descriptions should not include implementation > details, especially since those may change over time (as is the case here). > I fully agree. Many device trees come from outside the kernel (i.e. they are supplied by the system boot environment). Obviously these device trees cannot be changed at the whim of kernel developers, *and* it is perfectly reasonable to think that software other than the Linux kernel will run on this type of system too. So yes, it is really true, device trees are not a Linux kernel private implementation detail, they are really an external ABI that, although documented in the kernel source tree, cannot be changed in incompatible ways as time progresses. David Daney