From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergei Shtylyov Subject: Re: [PATCH v2 2/2] sh_eth: add device tree support Date: Tue, 10 Sep 2013 22:01:11 +0400 Message-ID: <522F5E67.8070006@cogentembedded.com> References: <201309070343.25640.sergei.shtylyov@cogentembedded.com> <522E3770.9020305@wwwdotorg.org> <522F2F3A.5070406@cogentembedded.com> <522F37A7.90804@wwwdotorg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <522F37A7.90804@wwwdotorg.org> Sender: linux-sh-owner@vger.kernel.org To: Stephen Warren Cc: rob.herring@calxeda.com, pawel.moll@arm.com, mark.rutland@arm.com, ian.campbell@citrix.com, grant.likely@linaro.org, devicetree@vger.kernel.org, linux-sh@vger.kernel.org, nobuhiro.iwamatsu.yj@renesas.com, rob@landley.net, linux-doc@vger.kernel.org List-Id: devicetree@vger.kernel.org Hello. On 09/10/2013 07:15 PM, Stephen Warren wrote: >>> Do you need any clocks properties, IP block reset signals, power domains? >> Currently not. > What does "currently" mean? Does that mean that the Linux driver simply > doesn't touch those entities at present? There's Ether clock but the driver doesn't manipulate it directly, assumingly it does this thru the runtime PM interface. As for the others, I simply don't know. > If so, that's not enough to say > that those entities should not be described in the DT binding. We should > strive to make the binding completely describe all aspects of the HW, > irrespective of whether a particular driver happens to use that > information at present. There's no DT representation for the clocks in SH-Mobile subarch yet. The same applies to the other entities you mentioned. WBR, Sergei