linux-stable.git/drivers/memory/tegra/mc.c, branch v5.1.2

memory: tegra: Clean up error messages

2019-01-16T12:54:13+00:00

Make all messages to start with a lower case and don't unnecessarily go
over 80 chars in the code.

Signed-off-by: Dmitry Osipenko 
Signed-off-by: Joerg Roedel

memory: tegra: Do not ask for IRQ sharing

2019-01-16T12:54:13+00:00

Memory Controller driver never shared IRQ with any other driver and very
unlikely that it will. Hence there is no need to request IRQ sharing and
the corresponding flag can be dropped safely.

Signed-off-by: Dmitry Osipenko 
Signed-off-by: Joerg Roedel

memory: tegra: Do not try to probe SMMU on Tegra20

2019-01-16T12:54:13+00:00

Tegra20 doesn't have SMMU. Move out checking of the SMMU presence from
the SMMU driver into the Memory Controller driver. This change makes code
consistent in regards to how GART/SMMU presence checking is performed.

Signed-off-by: Dmitry Osipenko 
Signed-off-by: Joerg Roedel

iommu/tegra: gart: Integrate with Memory Controller driver

2019-01-16T12:54:12+00:00

The device-tree binding has been changed. There is no separate GART device
anymore, it is squashed into the Memory Controller. Integrate GART module
with the MC in a way it is done for the SMMU on Tegra30+.

Signed-off-by: Dmitry Osipenko 
Signed-off-by: Joerg Roedel

memory: tegra: Use of_device_get_match_data()

2019-01-16T12:54:12+00:00

There is no need to match device with the DT node since it was already
matched, use of_device_get_match_data() helper to get the match-data.

Signed-off-by: Dmitry Osipenko 
Acked-by: Thierry Reding 
Signed-off-by: Joerg Roedel

memory: tegra: Read client ID on GART page fault

2019-01-16T12:54:11+00:00

With the device tree binding changes, now Memory Controller has access to
GART registers. Hence it is now possible to read client ID on GART page
fault to get information about what memory client causes the fault.

Signed-off-by: Dmitry Osipenko 
Acked-by: Thierry Reding 
Signed-off-by: Joerg Roedel

memory: tegra: Adapt to Tegra20 device-tree binding changes

2019-01-16T12:54:11+00:00

The tegra20-mc device-tree binding has been changed, GART has been
squashed into Memory Controller and now the clock property is mandatory
for Tegra20, the DT compatible has been changed as well. Adapt driver to
the DT changes.

Signed-off-by: Dmitry Osipenko 
Acked-by: Thierry Reding 
Signed-off-by: Joerg Roedel

memory: tegra: Don't invoke Tegra30+ specific memory timing setup on Tegra20

2019-01-16T12:54:11+00:00

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.

Fixes: a8d502fd3348 ("memory: tegra: Squash tegra20-mc into common tegra-mc driver")
Signed-off-by: Dmitry Osipenko 
Acked-by: Jon Hunter 
Acked-by: Thierry Reding 
Signed-off-by: Joerg Roedel

memory: Convert to using %pOFn instead of device_node.name

2018-11-27T16:54:39+00:00

In preparation to remove the node name pointer from struct device_node,
convert printf users to use the %pOFn format specifier.

Cc: Roger Quadros 
Cc: Kukjin Kim 
Cc: Jonathan Hunter 
Cc: linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-samsung-soc@vger.kernel.org
Cc: linux-tegra@vger.kernel.org
Acked-by: Thierry Reding 
Acked-by: Tony Lindgren 
Acked-by: Krzysztof Kozlowski 
Signed-off-by: Rob Herring

memory: tegra: Correct driver probe order

2018-07-10T15:29:15+00:00

The Reset Controller should be registered in the end of probe, otherwise
Memory Controller device goes away if IRQ requesting fails and the Reset
Controller stays registered. To avoid having to unwind the MC probing in
a case of SMMU probe failure, let's simply print the error message without
failing the MC probe. This allows us to just move the Reset Controller
registering before the SMMU registration, reducing code churning. Also
let's not fail MC probe in a case of Reset Controller registration failure
as it doesn't prevent the MC driver to work.

Signed-off-by: Dmitry Osipenko 
Signed-off-by: Thierry Reding