From: Dmitry Osipenko <digetx@gmail.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Joseph Lo <josephl@nvidia.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/3] memory: tegra: Introduce Tegra30 EMC driver
Date: Fri, 12 Apr 2019 17:01:28 +0300 [thread overview]
Message-ID: <0e61d2a7-3f13-3868-954f-86562c546be1@gmail.com> (raw)
In-Reply-To: <20190411230221.31362-3-digetx@gmail.com>
12.04.2019 2:02, Dmitry Osipenko пишет:
> Introduce driver for the External Memory Controller (EMC) found on Tegra30
> chips, it controls the external DRAM on the board. The purpose of this
> driver is to program memory timing for external memory on the EMC clock
> rate change.
>
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
I realized that the MC_SAME_FREQ timing configuration need be properly handled for T30 and that is missed in this version. Will fix it up in v2. Although, seems it's not critical since things appear to work properly and probably only arbitration is not optimally configured because of the MC/EMC setup mismatch.
next prev parent reply other threads:[~2019-04-12 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 23:02 [PATCH v1 0/3] memory: Introduce NVIDIA " Dmitry Osipenko
2019-04-11 23:02 ` [PATCH v1 1/3] dt-bindings: memory: Add binding for NVIDIA Tegra30 External Memory Controller Dmitry Osipenko
2019-04-11 23:02 ` [PATCH v1 2/3] memory: tegra: Introduce Tegra30 EMC driver Dmitry Osipenko
2019-04-12 14:01 ` Dmitry Osipenko [this message]
2019-04-11 23:02 ` [PATCH v1 3/3] ARM: dts: tegra30: Add External Memory Controller node Dmitry Osipenko
2019-04-12 8:01 ` Peter De Schrijver
2019-04-12 10:09 ` Dmitry Osipenko
2019-04-12 8:06 ` Peter De Schrijver
2019-04-12 10:11 ` Dmitry Osipenko
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=0e61d2a7-3f13-3868-954f-86562c546be1@gmail.com \
--to=digetx@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=josephl@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pdeschrijver@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®