From: Dmitry Osipenko <digetx@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] memory: tegra: Don't invoke Tegra30+ specific memory timing setup on Tegra20
Date: Thu, 19 Jul 2018 18:38:46 +0300 [thread overview]
Message-ID: <31916977.CHrX6e343J@dimapc> (raw)
In-Reply-To: <39607791-3e71-7784-37db-4e05a316d7a8@nvidia.com>
On Thursday, 19 July 2018 18:30:48 MSK Jon Hunter wrote:
> On 19/07/18 14:24, Dmitry Osipenko wrote:
> > This fixes irrelevant "tegra-mc 7000f000.memory-controller: no memory
> > timings for RAM code 0 registered" warning message during of kernels
> > boot-up on Tegra20.
>
> Looking at the tegra20-emc.txt bindings doc [0], the 'nvidia,ram-code'
> property is also valid for Tegra20. In fact, I see this warning on the
> Tegra30 Cardhu because this property is not populated. So I think that
> this warning is valid and harmless.
>
> Cheers
> Jon
>
> [0] Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-emc.txt
That is the irrelevant binding, the relevant one for this driver is [0]. The
warning is valid for T30+, but not for T20.
[0] Documentation/devicetree/bindings/memory-controllers/nvidia,tegra20-mc.txt
next prev parent reply other threads:[~2018-07-19 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 13:24 [PATCH v1] memory: tegra: Don't invoke Tegra30+ specific memory timing setup on Tegra20 Dmitry Osipenko
2018-07-19 15:30 ` Jon Hunter
2018-07-19 15:38 ` Dmitry Osipenko [this message]
2018-07-20 8:02 ` Jon Hunter
2018-07-20 16:42 ` 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=31916977.CHrX6e343J@dimapc \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.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