| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20201115212922.4390-1-digetx@gmail.com>
Date: Mon, 16 Nov 2020 00:29:05 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Georgi Djakov <georgi.djakov@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Peter De Schrijver <pdeschrijver@...dia.com>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
Mikko Perttunen <cyndis@...si.fi>,
Viresh Kumar <vireshk@...nel.org>,
Peter Geis <pgwipeout@...il.com>,
Nicolas Chauvet <kwizart@...il.com>,
Krzysztof Kozlowski <krzk@...nel.org>
Cc: linux-tegra@...r.kernel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org
Subject: [PATCH v9 00/17] Introduce memory interconnect for NVIDIA Tegra SoCs
This series brings initial support for memory interconnect to Tegra20,
Tegra30 and Tegra124 SoCs.
For the starter only display controllers and devfreq devices are getting
interconnect API support, others could be supported later on. The display
controllers have the biggest demand for interconnect API right now because
dynamic memory frequency scaling can't be done safely without taking into
account bandwidth requirement from the displays. In particular this series
fixes distorted display output on T30 Ouya and T124 TK1 devices.
Changelog:
v9: - Squashed "memory: tegra30-emc: Factor out clk initialization" into
patch "tegra30: Support interconnect framework".
Suggested by Krzysztof Kozlowski.
- Improved Kconfig in the patch "memory: tegra124-emc: Make driver modular"
by adding CONFIG_TEGRA124_CLK_EMC entry, which makes clk-driver changes
to look a bit more cleaner. Suggested by Krzysztof Kozlowski.
- Dropped voltage regulator support from ICC and DT patches for now
because there is a new discussion about using a power domain abstraction
for controlling the regulator, which is likely to happen.
- Replaced direct "operating-points-v2" property checking in EMC drivers
with checking of a returned error code from dev_pm_opp_of_add_table().
Note that I haven't touched T20 EMC driver because it's very likely
that we'll replace that code with a common helper soon anyways.
Suggested by Viresh Kumar.
- The T30 DT patches now include EMC OPP changes for Ouya board, which
is available now in linux-next.
Dmitry Osipenko (17):
memory: tegra30: Support interconnect framework
memory: tegra124-emc: Make driver modular
memory: tegra124-emc: Continue probing if timings are missing in
device-tree
memory: tegra124: Support interconnect framework
drm/tegra: dc: Support memory bandwidth management
drm/tegra: dc: Extend debug stats with total number of events
PM / devfreq: tegra30: Support interconnect and OPPs from device-tree
PM / devfreq: tegra30: Separate configurations per-SoC generation
PM / devfreq: tegra20: Deprecate in a favor of emc-stat based driver
ARM: tegra: Correct EMC registers size in Tegra20 device-tree
ARM: tegra: Add interconnect properties to Tegra20 device-tree
ARM: tegra: Add interconnect properties to Tegra30 device-tree
ARM: tegra: Add interconnect properties to Tegra124 device-tree
ARM: tegra: Add nvidia,memory-controller phandle to Tegra20 EMC
device-tree
ARM: tegra: Add EMC OPP properties to Tegra20 device-trees
ARM: tegra: Add EMC OPP and ICC properties to Tegra30 EMC and ACTMON
device-tree nodes
ARM: tegra: Add EMC OPP and ICC properties to Tegra124 EMC and ACTMON
device-tree nodes
MAINTAINERS | 1 -
arch/arm/boot/dts/tegra124-apalis-emc.dtsi | 8 +
.../arm/boot/dts/tegra124-jetson-tk1-emc.dtsi | 8 +
arch/arm/boot/dts/tegra124-nyan-big-emc.dtsi | 10 +
.../arm/boot/dts/tegra124-nyan-blaze-emc.dtsi | 10 +
.../boot/dts/tegra124-peripherals-opp.dtsi | 419 ++++++++++++++++++
arch/arm/boot/dts/tegra124.dtsi | 31 ++
.../boot/dts/tegra20-acer-a500-picasso.dts | 5 +
arch/arm/boot/dts/tegra20-colibri.dtsi | 4 +
arch/arm/boot/dts/tegra20-paz00.dts | 4 +
.../arm/boot/dts/tegra20-peripherals-opp.dtsi | 92 ++++
arch/arm/boot/dts/tegra20.dtsi | 33 +-
...30-asus-nexus7-grouper-memory-timings.dtsi | 12 +
arch/arm/boot/dts/tegra30-ouya.dts | 8 +
.../arm/boot/dts/tegra30-peripherals-opp.dtsi | 383 ++++++++++++++++
arch/arm/boot/dts/tegra30.dtsi | 33 +-
drivers/clk/tegra/Kconfig | 3 +
drivers/clk/tegra/Makefile | 2 +-
drivers/clk/tegra/clk-tegra124-emc.c | 41 +-
drivers/clk/tegra/clk-tegra124.c | 26 +-
drivers/clk/tegra/clk.h | 18 +-
drivers/devfreq/Kconfig | 10 -
drivers/devfreq/Makefile | 1 -
drivers/devfreq/tegra20-devfreq.c | 210 ---------
drivers/devfreq/tegra30-devfreq.c | 154 ++++---
drivers/gpu/drm/tegra/Kconfig | 1 +
drivers/gpu/drm/tegra/dc.c | 359 +++++++++++++++
drivers/gpu/drm/tegra/dc.h | 19 +
drivers/gpu/drm/tegra/drm.c | 14 +
drivers/gpu/drm/tegra/hub.c | 3 +
drivers/gpu/drm/tegra/plane.c | 121 +++++
drivers/gpu/drm/tegra/plane.h | 15 +
drivers/memory/tegra/Kconfig | 5 +-
drivers/memory/tegra/tegra124-emc.c | 382 ++++++++++++++--
drivers/memory/tegra/tegra124.c | 82 +++-
drivers/memory/tegra/tegra30-emc.c | 349 ++++++++++++++-
drivers/memory/tegra/tegra30.c | 173 +++++++-
include/linux/clk/tegra.h | 8 +
include/soc/tegra/emc.h | 16 -
39 files changed, 2699 insertions(+), 374 deletions(-)
create mode 100644 arch/arm/boot/dts/tegra124-peripherals-opp.dtsi
create mode 100644 arch/arm/boot/dts/tegra20-peripherals-opp.dtsi
create mode 100644 arch/arm/boot/dts/tegra30-peripherals-opp.dtsi
delete mode 100644 drivers/devfreq/tegra20-devfreq.c
delete mode 100644 include/soc/tegra/emc.h
--
2.29.2
Powered by blists - more mailing lists