From mboxrd@z Thu Jan 1 00:00:00 1970 From: Viresh Kumar Subject: Re: [PATCH 8/8] dt: cpufreq: st: Provide bindings for ST's CPUFreq implementation Date: Tue, 23 Jun 2015 14:30:16 +0530 Message-ID: <20150623090016.GL16776@linux> References: <1434987837-24212-1-git-send-email-lee.jones@linaro.org> <1434987837-24212-9-git-send-email-lee.jones@linaro.org> <20150623023458.GC16776@linux> <20150623070651.GA3245@x1> <20150623075509.GF16776@linux> <20150623083856.GH3245@x1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20150623083856.GH3245@x1> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Lee Jones Cc: robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org, rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org, linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, ajitpal.singh-qxv4g6HH51o@public.gmane.org List-Id: linux-pm@vger.kernel.org On 23-06-15, 09:38, Lee Jones wrote: > Do you always write your documentation before implementing a > feature? > > Surely it goes; > Requirements Gathering > Plan and Prepare > Implement > Test > Document > Deliver > > ;) DT bindings aren't just simple documentation of how things are working. I do things in the way you wrote earlier though :) > That's not what it looks like to me: > > git grep -C20 "compatible.*cpufreq" -- arch Yeah, that's wrong. They got in much earlier and the bindings weren't well thought through. But they are discouraged today .. -- viresh -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: viresh.kumar@linaro.org (Viresh Kumar) Date: Tue, 23 Jun 2015 14:30:16 +0530 Subject: [PATCH 8/8] dt: cpufreq: st: Provide bindings for ST's CPUFreq implementation In-Reply-To: <20150623083856.GH3245@x1> References: <1434987837-24212-1-git-send-email-lee.jones@linaro.org> <1434987837-24212-9-git-send-email-lee.jones@linaro.org> <20150623023458.GC16776@linux> <20150623070651.GA3245@x1> <20150623075509.GF16776@linux> <20150623083856.GH3245@x1> Message-ID: <20150623090016.GL16776@linux> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 23-06-15, 09:38, Lee Jones wrote: > Do you always write your documentation before implementing a > feature? > > Surely it goes; > Requirements Gathering > Plan and Prepare > Implement > Test > Document > Deliver > > ;) DT bindings aren't just simple documentation of how things are working. I do things in the way you wrote earlier though :) > That's not what it looks like to me: > > git grep -C20 "compatible.*cpufreq" -- arch Yeah, that's wrong. They got in much earlier and the bindings weren't well thought through. But they are discouraged today .. -- viresh From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932499AbbFWJAZ (ORCPT ); Tue, 23 Jun 2015 05:00:25 -0400 Received: from mail-pd0-f180.google.com ([209.85.192.180]:34816 "EHLO mail-pd0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752466AbbFWJAU (ORCPT ); Tue, 23 Jun 2015 05:00:20 -0400 Date: Tue, 23 Jun 2015 14:30:16 +0530 From: Viresh Kumar To: Lee Jones Cc: robh@kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kernel@stlinux.com, rjw@rjwysocki.net, linux-pm@vger.kernel.org, devicetree@vger.kernel.org, ajitpal.singh@st.com Subject: Re: [PATCH 8/8] dt: cpufreq: st: Provide bindings for ST's CPUFreq implementation Message-ID: <20150623090016.GL16776@linux> References: <1434987837-24212-1-git-send-email-lee.jones@linaro.org> <1434987837-24212-9-git-send-email-lee.jones@linaro.org> <20150623023458.GC16776@linux> <20150623070651.GA3245@x1> <20150623075509.GF16776@linux> <20150623083856.GH3245@x1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150623083856.GH3245@x1> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23-06-15, 09:38, Lee Jones wrote: > Do you always write your documentation before implementing a > feature? > > Surely it goes; > Requirements Gathering > Plan and Prepare > Implement > Test > Document > Deliver > > ;) DT bindings aren't just simple documentation of how things are working. I do things in the way you wrote earlier though :) > That's not what it looks like to me: > > git grep -C20 "compatible.*cpufreq" -- arch Yeah, that's wrong. They got in much earlier and the bindings weren't well thought through. But they are discouraged today .. -- viresh