Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3857224yba; Mon, 29 Apr 2019 09:37:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqyF6ZFyFyFzExkWgsRu9XUeozoQv0HxdUtZtfDu0cFJ5c6iVmRYPh3RraJKBJKoGXE33boB X-Received: by 2002:a17:902:6843:: with SMTP id f3mr37169863pln.218.1556555857768; Mon, 29 Apr 2019 09:37:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556555857; cv=none; d=google.com; s=arc-20160816; b=J6AQou6lNf283llb4fJZlrHY7EPITPI8h44Ntb+2u32G7HIjzvTLdxQPZBuaOxmuH4 YIumuDBETUozIHErlBY4Bh3HD6wTwfG4zuTq38dyGdU8z+3ReIVAtAPocTSpEjRVsD3I FbR6SoNESjQw5pQtszFDRIBbRdhPON/DyPKK/nL9oZTYpqL9ZmzQDSS2nRKfYd1o2ud/ Dk89zL9guWgzbmjCTbVOzACqpnNc4Yth4oYgioU+IORevKJ71qOSxKXxf9qN7cJuP7Hs /Olr9WvmcnOiIUnTVt45Ox5Fj4WDBmSHdVDFIx7Doom7l5ifqJDK18s6TTnnU8STs+c/ LyGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=QwXQyYz9u0bJguhriGY8krE/DeM5QzoXuFH0bgRg2/Y=; b=E0dd930FfiELj5tRXqfCiIWfYAPTNOaAOlT3LZSRfULe2nsHQjUbVZeSbCnSa4ZwTc E0BVdNj7cTqARe/5h7pZjxMJGuMUkkwPHEpZfAa2F6WZMDjMqJnp0mQzYg/DiX//us5i Ge4grEstBYgJrc11q53Coe11AxDZrzmKqNQybdz9LbkyaFnaqeP4+UfEBHeWS6ubmzdk GUz0pdzyj3NhGXn8ayeseR72SAhwj4Xf8bPS1tAchX/nAwnzWCV939P7jLv/qVvlU785 b7slD24fEVtZ+dcpjWM7W9n4z6Av/p1jOuApLfl3z7QHOhbhX0b5KehUV1Ga8OKfzMm0 lMWg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=0uGf7RAK; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p10si25500675pgb.314.2019.04.29.09.37.21; Mon, 29 Apr 2019 09:37:37 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=0uGf7RAK; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728767AbfD2Qga (ORCPT + 99 others); Mon, 29 Apr 2019 12:36:30 -0400 Received: from mail.kernel.org ([198.145.29.99]:57846 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728707AbfD2Qg3 (ORCPT ); Mon, 29 Apr 2019 12:36:29 -0400 Received: from mail-qt1-f173.google.com (mail-qt1-f173.google.com [209.85.160.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BEAC520675; Mon, 29 Apr 2019 16:36:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1556555788; bh=qQbtWgQhCca4rsTLpa6lcPV0wpNOsN4+0Bq5NvGiYVI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=0uGf7RAKBRgmpV6Z6NSoVx1AWvGHbHcuebfzbLoIKGWWgOyt7s+fbaaEguzbdjvpa BkwWjWKRIm1tRB1JrBnfcAh4OJ4FhiYSQ8CdH/2WBqrSRvBIju/pJkpHFXn1IfTtM0 xxRL2O8RQ2Xqni94b9UBU7Qs6XLdjfzX5N6fVEDI= Received: by mail-qt1-f173.google.com with SMTP id e5so5745735qtq.2; Mon, 29 Apr 2019 09:36:28 -0700 (PDT) X-Gm-Message-State: APjAAAVijzm/Q/7+J0oD8AxnZ8yW1dZFvPai7FdmKOAwXvjbzC6UskjV ePCJDJ/d2gqNDqgBuSi9R2HeVCYOOoqCsHCW3g== X-Received: by 2002:aed:306c:: with SMTP id 99mr2928926qte.38.1556555788034; Mon, 29 Apr 2019 09:36:28 -0700 (PDT) MIME-Version: 1.0 References: <1555683568-20882-1-git-send-email-l.luba@partner.samsung.com> <1555683568-20882-5-git-send-email-l.luba@partner.samsung.com> <20190425195156.GA31128@bogus> <86715dda-c1b0-5354-17d2-419f8137cb91@partner.samsung.com> In-Reply-To: <86715dda-c1b0-5354-17d2-419f8137cb91@partner.samsung.com> From: Rob Herring Date: Mon, 29 Apr 2019 11:36:16 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v6 04/10] Documentation: dt: device tree bindings for LPDDR3 memories To: Lukasz Luba Cc: devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , "open list:THERMAL" , linux-samsung-soc , Bartlomiej Zolnierkiewicz , Krzysztof Kozlowski , Kukjin Kim , Chanwoo Choi , Kyungmin Park , Marek Szyprowski , Sylwester Nawrocki , MyungJoo Ham , Kees Cook , Tony Lindgren , Joerg Roedel , Thierry Reding , Dmitry Osipenko , willy.mh.wolff.ml@gmail.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 29, 2019 at 7:05 AM Lukasz Luba wrote: > > Hi Rob, > > On 4/25/19 9:51 PM, Rob Herring wrote: > > On Fri, Apr 19, 2019 at 04:19:22PM +0200, Lukasz Luba wrote: > >> The device tree bindings for LPDDR3 SDRAM memories. > >> > >> For specifying the AC timing parameters of the memory device > >> the 'lpddr3' binding uses binding 'lpddr2-timings'. > >> > >> Signed-off-by: Lukasz Luba > >> --- > >> .../devicetree/bindings/lpddr3/lpddr3-timings.txt | 57 +++++++++++++ > >> .../devicetree/bindings/lpddr3/lpddr3.txt | 93 ++++++++++++++++++++++ > > > > Please rename the lpddr2 directory to 'ddr' and add these to it. > OK, I will rename it in the nex patch set. > > > > Maybe whatever properties are common should be put in a common doc. > There are maybe a few common properties, but I would not dare to merge > lpddr2 and lpddr3 before consulting it with TI engineers who made > LPDDR2 support. Why not. You aren't changing anything. Just rearranging. > Could we work on a common file after the patch set got merged? Yes, but please still move everything to a common directory. > > > >> 2 files changed, 150 insertions(+) > >> create mode 100644 Documentation/devicetree/bindings/lpddr3/lpddr3-timings.txt > >> create mode 100644 Documentation/devicetree/bindings/lpddr3/lpddr3.txt > >> > >> diff --git a/Documentation/devicetree/bindings/lpddr3/lpddr3-timings.txt b/Documentation/devicetree/bindings/lpddr3/lpddr3-timings.txt > >> new file mode 100644 > >> index 0000000..ebf3e00 > >> --- /dev/null > >> +++ b/Documentation/devicetree/bindings/lpddr3/lpddr3-timings.txt > >> @@ -0,0 +1,57 @@ > >> +* AC timing parameters of LPDDR3 memories for a given speed-bin. > >> +* The structures are based on LPDDR2 and extended where needed. > >> + > >> +Required properties: > >> +- compatible : Should be "jedec,lpddr3-timings" > >> +- min-freq : minimum DDR clock frequency for the speed-bin. Type is > >> +- max-freq : maximum DDR clock frequency for the speed-bin. Type is > >> + > >> +Optional properties: > >> + > >> +The following properties represent AC timing parameters from the memory > >> +data-sheet of the device for a given speed-bin. All these properties are > >> +of type and the default unit is ps (pico seconds). > >> +- tRFC > >> +- tRRD > >> +- tRPab > >> +- tRPpb > >> +- tRCD > >> +- tRC > >> +- tRAS > >> +- tWTR > >> +- tWR > >> +- tRTP > >> +- tW2W-C2C > >> +- tR2R-C2C > >> +- tFAW > >> +- tXSR > >> +- tXP > >> +- tCKE > >> +- tCKESR > >> +- tMRD > >> + > >> +Example: > >> + > >> +timings_samsung_K3QF2F20DB_800mhz: lpddr3-timings@0 { > > > > Since the lpddr2 version was written, we've gotten stricter about > > allowing unit-address without reg property. Perhaps 'reg' should be the > > max-freq instead. > OK, so I will rename 'max-freq' to 'reg' and add a comment with: > '/* workaround: it shows max-freq */ > Does it make sense? Sure. Rob