From: Rob Herring <robh@kernel.org>
To: Lukasz Luba <l.luba@partner.samsung.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
b.zolnierkie@samsung.com, krzk@kernel.org, kgene@kernel.org,
cw00.choi@samsung.com, kyungmin.park@samsung.com,
m.szyprowski@samsung.com, s.nawrocki@samsung.com,
myungjoo.ham@samsung.com, keescook@chromium.org,
tony@atomide.com, jroedel@suse.de, treding@nvidia.com,
digetx@gmail.com, willy.mh.wolff.ml@gmail.com
Subject: Re: [PATCH v6 04/10] Documentation: dt: device tree bindings for LPDDR3 memories
Date: Thu, 25 Apr 2019 14:51:56 -0500 [thread overview]
Message-ID: <20190425195156.GA31128@bogus> (raw)
In-Reply-To: <1555683568-20882-5-git-send-email-l.luba@partner.samsung.com>
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 <l.luba@partner.samsung.com>
> ---
> .../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.
Maybe whatever properties are common should be put in a common doc.
> 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 <u32>
> +- max-freq : maximum DDR clock frequency for the speed-bin. Type is <u32>
> +
> +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 <u32> 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.
> + compatible = "jedec,lpddr3-timings";
> + min-freq = <100000000>;
> + max-freq = <800000000>;
> + tRFC = <65000>;
> + tRRD = <6000>;
> + tRPab = <12000>;
> + tRPpb = <12000>;
> + tRCD = <10000>;
> + tRC = <33750>;
> + tRAS = <23000>;
> + tWTR = <3750>;
> + tWR = <7500>;
> + tRTP = <3750>;
> + tW2W-C2C = <0>;
> + tR2R-C2C = <0>;
> + tFAW = <25000>;
> + tXSR = <70000>;
> + tXP = <3750>;
> + tCKE = <3750>;
> + tCKESR = <3750>;
> + tMRD = <7000>;
> +};
> diff --git a/Documentation/devicetree/bindings/lpddr3/lpddr3.txt b/Documentation/devicetree/bindings/lpddr3/lpddr3.txt
> new file mode 100644
> index 0000000..fc7875c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/lpddr3/lpddr3.txt
> @@ -0,0 +1,93 @@
> +* LPDDR3 SDRAM memories compliant to JEDEC JESD209-2
That's an LPDDR2 spec.
> +
> +Required properties:
> +- compatible : Should be - "jedec,lpddr3"
> +- density : <u32> representing density in Mb (Mega bits)
> +- io-width : <u32> representing bus width. Possible values are 8, 16, 32, 64
> +
> +Optional properties:
> +
> +The following optional properties represent the minimum value of some AC
> +timing parameters of the DDR device in terms of number of clock cycles.
> +These values shall be obtained from the device data-sheet.
> +- tRFC-min-tck
> +- tRRD-min-tck
> +- tRPab-min-tck
> +- tRPpb-min-tck
> +- tRCD-min-tck
> +- tRC-min-tck
> +- tRAS-min-tck
> +- tWTR-min-tck
> +- tWR-min-tck
> +- tRTP-min-tck
> +- tW2W-C2C-min-tck
> +- tR2R-C2C-min-tck
> +- tWL-min-tck
> +- tDQSCK-min-tck
> +- tRL-min-tck
> +- tFAW-min-tck
> +- tXSR-min-tck
> +- tXP-min-tck
> +- tCKE-min-tck
> +- tCKESR-min-tck
> +- tMRD-min-tck
> +
> +Child nodes:
> +- The lpddr3 node may have one or more child nodes of type "lpddr3-timings".
> + "lpddr3-timings" provides AC timing parameters of the device for
> + a given speed-bin. Please see Documentation/devicetree/
> + bindings/lpddr3/lpddr3-timings.txt for more information on "lpddr3-timings"
> +
> +Example:
> +
> +samsung_K3QF2F20DB: lpddr3 {
> + compatible = "Samsung,K3QF2F20DB","jedec,lpddr3";
> + density = <16384>;
> + io-width = <32>;
> +
> + tRFC-min-tck = <17>;
> + tRRD-min-tck = <2>;
> + tRPab-min-tck = <2>;
> + tRPpb-min-tck = <2>;
> + tRCD-min-tck = <3>;
> + tRC-min-tck = <6>;
> + tRAS-min-tck = <5>;
> + tWTR-min-tck = <2>;
> + tWR-min-tck = <7>;
> + tRTP-min-tck = <2>;
> + tW2W-C2C-min-tck = <0>;
> + tR2R-C2C-min-tck = <0>;
> + tWL-min-tck = <8>;
> + tDQSCK-min-tck = <5>;
> + tRL-min-tck = <14>;
> + tFAW-min-tck = <5>;
> + tXSR-min-tck = <12>;
> + tXP-min-tck = <2>;
> + tCKE-min-tck = <2>;
> + tCKESR-min-tck = <2>;
> + tMRD-min-tck = <5>;
> +
> + timings_samsung_K3QF2F20DB_800mhz: lpddr3-timings@0 {
> + compatible = "jedec,lpddr3-timings";
> + min-freq = <100000000>;
> + max-freq = <800000000>;
> + tRFC = <65000>;
> + tRRD = <6000>;
> + tRPab = <12000>;
> + tRPpb = <12000>;
> + tRCD = <10000>;
> + tRC = <33750>;
> + tRAS = <23000>;
> + tWTR = <3750>;
> + tWR = <7500>;
> + tRTP = <3750>;
> + tW2W-C2C = <0>;
> + tR2R-C2C = <0>;
> + tFAW = <25000>;
> + tXSR = <70000>;
> + tXP = <3750>;
> + tCKE = <3750>;
> + tCKESR = <3750>;
> + tMRD = <7000>;
> + };
> +}
> --
> 2.7.4
>
next prev parent reply other threads:[~2019-04-25 19:51 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190419141938eucas1p16ee6cdf897184df33cf67b55c5f3c449@eucas1p1.samsung.com>
2019-04-19 14:19 ` [PATCH v6 0/10] Exynos5 Dynamic Memory Controller driver Lukasz Luba
2019-04-19 14:19 ` [PATCH v6 01/10] clk: samsung: add needed IDs for DMC clocks in Exynos5420 Lukasz Luba
2019-04-30 4:47 ` Chanwoo Choi
2019-04-30 12:36 ` Lukasz Luba
2019-04-19 14:19 ` [PATCH v6 02/10] clk: samsung: add new clocks for DMC for Exynos5422 SoC Lukasz Luba
2019-04-30 1:31 ` Chanwoo Choi
2019-04-30 13:12 ` Lukasz Luba
2019-04-19 14:19 ` [PATCH v6 03/10] clk: samsung: add BPLL rate table for Exynos 5422 SoC Lukasz Luba
2019-05-02 5:15 ` Chanwoo Choi
2019-05-02 14:23 ` Lukasz Luba
2019-04-19 14:19 ` [PATCH v6 04/10] Documentation: dt: device tree bindings for LPDDR3 memories Lukasz Luba
2019-04-25 19:51 ` Rob Herring [this message]
2019-04-29 12:04 ` Lukasz Luba
2019-04-29 16:36 ` Rob Herring
2019-04-30 20:04 ` Lukasz Luba
2019-04-25 19:53 ` Rob Herring
2019-04-29 12:05 ` Lukasz Luba
2019-04-19 14:19 ` [PATCH v6 05/10] drivers: memory: extend of_memory by LPDDR3 support Lukasz Luba
2019-04-19 14:19 ` [PATCH v6 06/10] dt-bindings: memory-controllers: add Exynos5422 DMC device description Lukasz Luba
2019-04-25 19:57 ` Rob Herring
2019-04-29 12:14 ` Lukasz Luba
2019-04-29 16:43 ` Rob Herring
2019-04-30 20:15 ` Lukasz Luba
2019-04-30 4:46 ` Chanwoo Choi
2019-04-30 20:30 ` Lukasz Luba
2019-05-02 1:35 ` Chanwoo Choi
2019-05-02 18:56 ` Lukasz Luba
2019-04-19 14:19 ` [PATCH v6 07/10] drivers: memory: add DMC driver for Exynos5422 Lukasz Luba
2019-04-23 11:27 ` Krzysztof Kozlowski
2019-04-29 14:51 ` Lukasz Luba
2019-04-19 14:19 ` [PATCH v6 08/10] drivers: devfreq: events: add Exynos PPMU new events Lukasz Luba
2019-04-19 14:19 ` [PATCH v6 09/10] ARM: dts: exynos: add DMC device for exynos5422 Lukasz Luba
2019-04-23 11:03 ` Krzysztof Kozlowski
2019-04-29 12:38 ` Lukasz Luba
2019-04-19 14:19 ` [PATCH v6 10/10] ARM: exynos_defconfig: enable DMC driver Lukasz Luba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190425195156.GA31128@bogus \
--to=robh@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jroedel@suse.de \
--cc=keescook@chromium.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=l.luba@partner.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=myungjoo.ham@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=tony@atomide.com \
--cc=treding@nvidia.com \
--cc=willy.mh.wolff.ml@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.