From: Thierry Reding <thierry.reding@gmail.com>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/4] memory: tegra: Fix memory arbitration programming
Date: Thu, 18 Apr 2019 11:37:04 +0200 [thread overview]
Message-ID: <20190418093704.GB26909@ulmo> (raw)
In-Reply-To: <20190411221250.23233-1-digetx@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On Fri, Apr 12, 2019 at 01:12:46AM +0300, Dmitry Osipenko wrote:
> Hello, this series properly addresses the bugged memory arbitration
> programming and in result the previous suspend-resume workaround change
> is reverted as it was not entirely correct.
>
> Dmitry Osipenko (4):
> memory: tegra: Fix missed registers values latching
> memory: tegra: Fix integer overflow on tick value calculation
> memory: tegra: Replace readl-writel with mc_readl-mc_writel
> Revert "ARM: tegra: Restore memory arbitration on resume from LP1 on
> Tegra30+"
>
> arch/arm/mach-tegra/iomap.h | 9 ---------
> arch/arm/mach-tegra/sleep-tegra30.S | 21 ---------------------
> drivers/memory/tegra/mc.c | 16 +++++++++++-----
> 3 files changed, 11 insertions(+), 35 deletions(-)
Applied to for-5.2/memory, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-04-18 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 22:12 [PATCH v1 0/4] memory: tegra: Fix memory arbitration programming Dmitry Osipenko
2019-04-11 22:12 ` [PATCH v1 1/4] memory: tegra: Fix missed registers values latching Dmitry Osipenko
2019-04-11 22:12 ` [PATCH v1 2/4] memory: tegra: Fix integer overflow on tick value calculation Dmitry Osipenko
2019-04-11 22:12 ` [PATCH v1 3/4] memory: tegra: Replace readl-writel with mc_readl-mc_writel Dmitry Osipenko
2019-04-11 22:12 ` [PATCH v1 4/4] Revert "ARM: tegra: Restore memory arbitration on resume from LP1 on Tegra30+" Dmitry Osipenko
2019-04-18 9:37 ` Thierry Reding [this message]
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=20190418093704.GB26909@ulmo \
--to=thierry.reding@gmail.com \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
/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.