From: Krzysztof Kozlowski <krzk@kernel.org>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org, soc@kernel.org
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
linux-kernel@vger.kernel.org, Thierry Reding <treding@nvidia.com>
Subject: [GIT PULL 2/2] memory: Second pull for Tegra MC for v5.11
Date: Mon, 7 Dec 2020 08:57:58 +0100 [thread overview]
Message-ID: <20201207075758.5501-2-krzk@kernel.org> (raw)
In-Reply-To: <20201207075758.5501-1-krzk@kernel.org>
Hi,
On top of previous pull request. This will remove annoying warning coming from
the previous patches, so it would be good if it goes this cycle. The warning
itself does not mean anything is broken - just message that new features are
not supported yet.
Best regards,
Krzysztof
The following changes since commit 0e1bcf2c05d0a681c04351fbd60812aea99354b6:
memory: tegra30-emc: Remove unnecessary of_node_put in tegra_emc_probe (2020-11-26 18:50:37 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git tags/memory-controller-drv-tegra-5.11-3
for you to fetch changes up to d76fa3f2c252421faf326afd5f445bed5d34075f:
memory: tegra30: Support interconnect framework (2020-12-05 14:54:36 +0100)
----------------------------------------------------------------
Memory controller drivers for v5.11 - Tegra SoC, part two
Continuation of work on Tegra SoC memory controllers towards adding
interconnect support and integration with devfreq.
This brings few more patches including one which removes/fixes annoying
warning if the DTS patches get applied. This is expected and only
informs that new features of Tegra memory controller drivers will not be
enabled however the warning itself could look worrying.
----------------------------------------------------------------
Dmitry Osipenko (3):
dt-bindings: memory: tegra20-emc: Document opp-supported-hw property
memory: tegra20: Support hardware versioning and clean up OPP table initialization
memory: tegra30: Support interconnect framework
.../memory-controllers/nvidia,tegra20-emc.txt | 6 +
drivers/memory/tegra/Kconfig | 1 +
drivers/memory/tegra/tegra20-emc.c | 48 ++-
drivers/memory/tegra/tegra30-emc.c | 344 +++++++++++++++++++--
drivers/memory/tegra/tegra30.c | 173 ++++++++++-
5 files changed, 522 insertions(+), 50 deletions(-)
next prev parent reply other threads:[~2020-12-07 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 7:57 [GIT PULL 1/2] memory: Second pull for v5.11 Krzysztof Kozlowski
2020-12-07 7:57 ` Krzysztof Kozlowski [this message]
2020-12-08 23:31 ` [GIT PULL 2/2] memory: Second pull for Tegra MC " Arnd Bergmann
2020-12-08 23:31 ` [GIT PULL 1/2] memory: Second pull " Arnd Bergmann
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=20201207075758.5501-2-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=treding@nvidia.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.