From mboxrd@z Thu Jan 1 00:00:00 1970 From: lars@metafoo.de (Lars-Peter Clausen) Date: Wed, 20 Apr 2016 13:15:27 +0200 Subject: [PATCH 1/2] Documentation: DT: vdma: Add clock support for vdma In-Reply-To: References: <1461136800-20334-1-git-send-email-appanad@xilinx.com> Message-ID: <571764CF.6070003@metafoo.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 04/20/2016 10:39 AM, Appana Durga Kedareswara Rao wrote: [...] >> however we should keep the names same as the TRM. > > Why?? Why can't we use simple convenient names that refers to equivalent clocks of h/w Because it is confusing. If you use the same name it's very straight forward to understand which clock is being referred to. That's not the case if you come up with random new names. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars-Peter Clausen Subject: Re: [PATCH 1/2] Documentation: DT: vdma: Add clock support for vdma Date: Wed, 20 Apr 2016 13:15:27 +0200 Message-ID: <571764CF.6070003@metafoo.de> References: <1461136800-20334-1-git-send-email-appanad@xilinx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Appana Durga Kedareswara Rao , Shubhrajyoti Datta Cc: Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Michal Simek , Soren Brinkmann , "vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org" , "dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org" , Moritz Fischer , Laurent Pinchart , "luis-HiykPkW1eAzzDCI4PIEvbQC/G2K4zDHf@public.gmane.org" , Anirudha Sarangi , Punnaiah Choudary Kalluri , "dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" List-Id: devicetree@vger.kernel.org On 04/20/2016 10:39 AM, Appana Durga Kedareswara Rao wrote: [...] >> however we should keep the names same as the TRM. > > Why?? Why can't we use simple convenient names that refers to equivalent clocks of h/w Because it is confusing. If you use the same name it's very straight forward to understand which clock is being referred to. That's not the case if you come up with random new names. -- 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 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755009AbcDTLPm (ORCPT ); Wed, 20 Apr 2016 07:15:42 -0400 Received: from www381.your-server.de ([78.46.137.84]:35584 "EHLO www381.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751751AbcDTLPk (ORCPT ); Wed, 20 Apr 2016 07:15:40 -0400 Subject: Re: [PATCH 1/2] Documentation: DT: vdma: Add clock support for vdma To: Appana Durga Kedareswara Rao , Shubhrajyoti Datta References: <1461136800-20334-1-git-send-email-appanad@xilinx.com> Cc: Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Michal Simek , Soren Brinkmann , "vinod.koul@intel.com" , "dan.j.williams@intel.com" , Moritz Fischer , Laurent Pinchart , "luis@debethencourt.com" , Anirudha Sarangi , Punnaiah Choudary Kalluri , "dmaengine@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" From: Lars-Peter Clausen Message-ID: <571764CF.6070003@metafoo.de> Date: Wed, 20 Apr 2016 13:15:27 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Authenticated-Sender: lars@metafoo.de Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/20/2016 10:39 AM, Appana Durga Kedareswara Rao wrote: [...] >> however we should keep the names same as the TRM. > > Why?? Why can't we use simple convenient names that refers to equivalent clocks of h/w Because it is confusing. If you use the same name it's very straight forward to understand which clock is being referred to. That's not the case if you come up with random new names.