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 v2 0/3] NVIDIA Tegra30 EMC driver improvements
Date: Fri, 10 Jan 2020 15:46:14 +0100 [thread overview]
Message-ID: <20200110144614.GH2233456@ulmo> (raw)
In-Reply-To: <20191220020849.11175-1-digetx@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
On Fri, Dec 20, 2019 at 05:08:46AM +0300, Dmitry Osipenko wrote:
> Hello,
>
> I took a refreshed look at the driver's code and spotted few things that
> could be improved. No critical fixes here, just improvements. Please
> review and apply, thanks in advance!
>
> Changelog:
>
> v2: - Now using WRITE/READ_ONCE() in the "Firm up hardware programming
> sequence" patch for interrupt handler interactions, to firm driver
> even further.
>
> Dmitry Osipenko (3):
> memory: tegra30-emc: Firm up suspend/resume sequence
> memory: tegra30-emc: Firm up hardware programming sequence
> memory: tegra30-emc: Correct error message for timed out auto
> calibration
>
> drivers/memory/tegra/tegra30-emc.c | 179 +++++++++++++++++------------
> 1 file changed, 104 insertions(+), 75 deletions(-)
Applied to for-5.6/memory, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-10 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 2:08 [PATCH v2 0/3] NVIDIA Tegra30 EMC driver improvements Dmitry Osipenko
2019-12-20 2:08 ` [PATCH v2 1/3] memory: tegra30-emc: Firm up suspend/resume sequence Dmitry Osipenko
2019-12-20 2:08 ` [PATCH v2 2/3] memory: tegra30-emc: Firm up hardware programming sequence Dmitry Osipenko
2019-12-20 2:08 ` [PATCH v2 3/3] memory: tegra30-emc: Correct error message for timed out auto calibration Dmitry Osipenko
2020-01-10 14:46 ` 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=20200110144614.GH2233456@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.