Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp987522ybe; Fri, 6 Sep 2019 10:09:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqwDIUep+SDRcvNuikNTXESiQg94NV75l3cEF503W8DY/rtIbZujfpEGjincrVP6SaW1Ikg3 X-Received: by 2002:a63:d84e:: with SMTP id k14mr8845726pgj.234.1567789761479; Fri, 06 Sep 2019 10:09:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567789761; cv=none; d=google.com; s=arc-20160816; b=G0D55k5hEw3s+WNnMT0pt9RsOFv55qKp77NTlTwJAh3hcpmdjKJX9AR6g0GQggR3Ad DXRHwxKDbJMEH68iYyNuNExlrOeomrAzbtr0IOwLBON4eTh/WSBVbEsUUKHYEbg++6mN +Rx9WtY+AbcQL+5ONG2hADk6QaNFBbeBS3WzAhHWzf2AN0/T6ebb0kU+LX6YiloaaN3m 5r85780kT3tlaY1o9Fyq26u+Et7S2v8c0h3Jc8GF7JXgjMMD/UBEtmmpNOweqHb6JEGK VZaLpJD4D547ybsg4RuO9iwf5qoFgYJ+G0kIEal2h2jXBh3FjgFVjyseGdD0B7zCd2is 8LRg== 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=RXqlGYGyjTS3h85sTJmW7Y8PsUDNMFyHVUyxGnYhqno=; b=UoeXd0XCPkKjlqaa8LfwpwZvPjfyLgxS7UeargeL7MCIX/PS++rFgEJzEPGA9JHMhY EMOYBHQ9QCWd/WlpJiVaauQi77PiV9np/Zv3diVzfwWxMbJuEYzwY5PXCEDflegzBa8E Flelk3TuYDYmaOOpt5gc8qFlvPhHXNEzk5K0L/PDEyvq5q/ay70NVUPmkTHjCPMrkHCl 4gdywyXf7FwOGt0P/t6L9ItI3I7g4WuN84yD4OS9fN5cJPCwmfROgnAFCnSe0HX+bISn gZt9zDrf1T+tp96BTEYlAqqq9q1z215/GMHvgcB3QYTvdZP3+JEpIsHomEvyn6i9k/QR M39Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=N0csuP4J; 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 v185si4864503pgd.340.2019.09.06.10.09.05; Fri, 06 Sep 2019 10:09:21 -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=N0csuP4J; 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 S2391026AbfIFLul (ORCPT + 99 others); Fri, 6 Sep 2019 07:50:41 -0400 Received: from mail.kernel.org ([198.145.29.99]:43964 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389867AbfIFLul (ORCPT ); Fri, 6 Sep 2019 07:50:41 -0400 Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com [209.85.208.179]) (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 2D6C9214DE; Fri, 6 Sep 2019 11:50:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567770639; bh=6UFqIwtKvW1eriIbgBgmH3OSdsldJSwILczL2ULz+PM=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=N0csuP4JYNSPIcZcs0RweApE9TD0NSFN9lth+8XvaWizi5oye5mSl1exsL720mVul 8hs0HcoXfks1iXMpZQRUSutucTK2AHQM5cfFa4//G1fsXWd9hwFBbihKbHHv9wm8nc zYiitj3mdsobc6gRClSXtKkB6rbLd2JR/WaCCElc= Received: by mail-lj1-f179.google.com with SMTP id j16so5737941ljg.6; Fri, 06 Sep 2019 04:50:39 -0700 (PDT) X-Gm-Message-State: APjAAAVomMaKdraHykT5qZVoJbRMSOgFbJtBKYqY5/mknH4vy6mcW2Ju jrWr3+q9EZB5Cc4mrWcg6YW5Tk8ARIxfK/rh+5k= X-Received: by 2002:a2e:99cc:: with SMTP id l12mr5508092ljj.5.1567770637352; Fri, 06 Sep 2019 04:50:37 -0700 (PDT) MIME-Version: 1.0 References: <20190906101344.3535-1-l.luba@partner.samsung.com> <20190906101344.3535-4-l.luba@partner.samsung.com> <52963d0d-cf48-7085-5581-a94c6e15e0bd@partner.samsung.com> In-Reply-To: <52963d0d-cf48-7085-5581-a94c6e15e0bd@partner.samsung.com> From: Krzysztof Kozlowski Date: Fri, 6 Sep 2019 13:50:26 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 3/3] dt-bindings: ddr: Add bindings for Samsung LPDDR3 memories To: Lukasz Luba Cc: devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , linux-pm@vger.kernel.org, "linux-samsung-soc@vger.kernel.org" , linux-arm-kernel@lists.infradead.org, =?UTF-8?B?QmFydMWCb21pZWogxbtvxYJuaWVya2lld2ljeg==?= , kgene@kernel.org, mark.rutland@arm.com, robh+dt@kernel.org, Chanwoo Choi , kyungmin.park@samsung.com, Marek Szyprowski , s.nawrocki@samsung.com, myungjoo.ham@samsung.com, 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 Fri, 6 Sep 2019 at 13:39, Lukasz Luba wrote: > > Hi Krzysztof, > > On 9/6/19 12:56 PM, Krzysztof Kozlowski wrote: > > On Fri, 6 Sep 2019 at 12:14, Lukasz Luba wrote: > >> > >> Add description of bindings for Samsung k3qf2f20db LPDDR3 memory. > >> Minor fixes in the old documentation. > >> > >> Signed-off-by: Lukasz Luba > >> --- > >> .../devicetree/bindings/ddr/lpddr3.txt | 29 +++++++++++++++++-- > >> 1 file changed, 27 insertions(+), 2 deletions(-) > >> > >> diff --git a/Documentation/devicetree/bindings/ddr/lpddr3.txt b/Documentation/devicetree/bindings/ddr/lpddr3.txt > >> index 3b2485b84b3f..de0905239767 100644 > >> --- a/Documentation/devicetree/bindings/ddr/lpddr3.txt > >> +++ b/Documentation/devicetree/bindings/ddr/lpddr3.txt > >> @@ -40,10 +40,34 @@ Child nodes: > >> a given speed-bin. Please see Documentation/devicetree/ > >> bindings/ddr/lpddr3-timings.txt for more information on "lpddr3-timings" > >> > >> +Samsung K3QF2F20DB LPDDR3 memory > >> +------------------------------------------------------------ > >> + > >> +This binding uses the LPDDR3 binding (described above) > >> + > >> +Required properties: > >> +- compatible: Should be: > >> + "samsung,K3QF2F20DB" > >> + followed by "jedec,lpddr3" > >> +- density : representing density in Mb (Mega bits) > >> +- io-width : representing bus width. Possible value 32 > >> +- #address-cells: Must be set to 1 > >> +- #size-cells: Must be set to 0 > > > > If you decided to repeat all properties again, then it deserves its > > own bindings file. However I though about simpler solution - just > > document compatible. Exactly the same as AT24 or AT25 EEPROM bindings. > > There is not much benefit from copying all these properties. > OK, I see. I will add only 'compatible' and skip the rest then. > So the lpddr3.txt file will get this addition: > > +Samsung K3QF2F20DB LPDDR3 memory > +------------------------------------------------------------ > + > +This binding uses the LPDDR3 binding (described above) > + > +Required properties: > +- compatible: Should be: > + "samsung,K3QF2F20DB" > + followed by "jedec,lpddr3" > + > +Optional properties: > + > +The optional properties are the same as in the LPDDR3 generic bindings and > +values should be taken from the data-sheet. Detailed bindings are described > +above. > + > +Child nodes: > + > +Detailed bindings are described in LPDDR3 generic bindings described above. > + > > Is it OK? To me it is still a lot of text just for one compatible and I can image more of such entries for other memories... However I do not mind and anyway, YAML will simplify it. If you're in doubt, wait for Rob's reply as this is his part. Best regards, Krzysztof