From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753772AbbBYPhl (ORCPT ); Wed, 25 Feb 2015 10:37:41 -0500 Received: from pmta2.delivery8.ore.mailhop.org ([54.148.222.11]:36653 "EHLO pmta2.delivery8.ore.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753008AbbBYPhk (ORCPT ); Wed, 25 Feb 2015 10:37:40 -0500 X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 104.193.169.186 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX19/tdUMErIrmFEjB6wPgS/i Date: Wed, 25 Feb 2015 07:23:25 -0800 From: Tony Lindgren To: Roger Quadros Cc: Robert ABEL , linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, linux@arm.linux.org.uk Subject: Re: [PATCH 5/8 v2] ARM OMAP2+ GPMC: change get_gpmc_timing_reg output for DTS Message-ID: <20150225152324.GN11056@atomide.com> References: <1424808331-17592-1-git-send-email-rabel@cit-ec.uni-bielefeld.de> <1424808331-17592-2-git-send-email-rabel@cit-ec.uni-bielefeld.de> <1424808331-17592-3-git-send-email-rabel@cit-ec.uni-bielefeld.de> <1424808331-17592-4-git-send-email-rabel@cit-ec.uni-bielefeld.de> <1424808331-17592-5-git-send-email-rabel@cit-ec.uni-bielefeld.de> <54EDCD29.3010404@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54EDCD29.3010404@ti.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Roger Quadros [150225 05:28]: > On 24/02/15 22:05, Robert ABEL wrote: > > DTS output was formatted to require additional work when copy-pasting into DTS. > > Nano-second timings were removed, because they were not a confidence interval nor > > an indication what timing values would result in the same #ticks > > If they were not is it possible to dump min,max timings that will result in > the same ticks? Yeah my plan was o display the nanosecond range resulting in the same tick value. That makes it a bit easier to compare the timings to the data sheet. So maybe show both tick and ns range? Ideally the timings would be from the device data sheet with the latency added for components that are on the line in addition to the device, such as level shifters and FPGA. Regards, Tony