linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v1] memory: tegra: Don't invoke Tegra30+ specific memory timing setup on Tegra20
@ 2018-07-19 13:24 Dmitry Osipenko
  2018-07-19 15:30 ` Jon Hunter
  0 siblings, 1 reply; 5+ messages in thread
From: Dmitry Osipenko @ 2018-07-19 13:24 UTC (permalink / raw)
  To: Thierry Reding; +Cc: linux-tegra, linux-kernel

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.

Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
---
 drivers/memory/tegra/mc.c | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/drivers/memory/tegra/mc.c b/drivers/memory/tegra/mc.c
index bd25faf6d13d..e56862495f36 100644
--- a/drivers/memory/tegra/mc.c
+++ b/drivers/memory/tegra/mc.c
@@ -664,12 +664,13 @@ static int tegra_mc_probe(struct platform_device *pdev)
 		}
 
 		isr = tegra_mc_irq;
-	}
 
-	err = tegra_mc_setup_timings(mc);
-	if (err < 0) {
-		dev_err(&pdev->dev, "failed to setup timings: %d\n", err);
-		return err;
+		err = tegra_mc_setup_timings(mc);
+		if (err < 0) {
+			dev_err(&pdev->dev, "failed to setup timings: %d\n",
+				err);
+			return err;
+		}
 	}
 
 	mc->irq = platform_get_irq(pdev, 0);
-- 
2.18.0


^ permalink raw reply related	[flat|nested] 5+ messages in thread

* Re: [PATCH v1] memory: tegra: Don't invoke Tegra30+ specific memory timing setup on Tegra20
  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
  0 siblings, 1 reply; 5+ messages in thread
From: Jon Hunter @ 2018-07-19 15:30 UTC (permalink / raw)
  To: Dmitry Osipenko, Thierry Reding; +Cc: linux-tegra, linux-kernel


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
-- 
nvpublic

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH v1] memory: tegra: Don't invoke Tegra30+ specific memory timing setup on Tegra20
  2018-07-19 15:30 ` Jon Hunter
@ 2018-07-19 15:38   ` Dmitry Osipenko
  2018-07-20  8:02     ` Jon Hunter
  0 siblings, 1 reply; 5+ messages in thread
From: Dmitry Osipenko @ 2018-07-19 15:38 UTC (permalink / raw)
  To: Jon Hunter; +Cc: Thierry Reding, linux-tegra, linux-kernel

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



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH v1] memory: tegra: Don't invoke Tegra30+ specific memory timing setup on Tegra20
  2018-07-19 15:38   ` Dmitry Osipenko
@ 2018-07-20  8:02     ` Jon Hunter
  2018-07-20 16:42       ` Dmitry Osipenko
  0 siblings, 1 reply; 5+ messages in thread
From: Jon Hunter @ 2018-07-20  8:02 UTC (permalink / raw)
  To: Dmitry Osipenko; +Cc: Thierry Reding, linux-tegra, linux-kernel


On 19/07/18 16:38, Dmitry Osipenko wrote:
> 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

Yes indeed, looks like we never supported this for Tegra20. OK, fine with me
I guess this was introduced during the consolidation of the MC drivers. Can
you add the appropriate fixes tag?

Otherwise ...

Acked-by: Jon Hunter <jonathanh@nvidia.com>

Cheers
Jon

-- 
nvpublic

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH v1] memory: tegra: Don't invoke Tegra30+ specific memory timing setup on Tegra20
  2018-07-20  8:02     ` Jon Hunter
@ 2018-07-20 16:42       ` Dmitry Osipenko
  0 siblings, 0 replies; 5+ messages in thread
From: Dmitry Osipenko @ 2018-07-20 16:42 UTC (permalink / raw)
  To: Jon Hunter; +Cc: Thierry Reding, linux-tegra, linux-kernel

On Friday, 20 July 2018 11:02:04 MSK Jon Hunter wrote:
> On 19/07/18 16:38, Dmitry Osipenko wrote:
> > 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.tx
> > t
> Yes indeed, looks like we never supported this for Tegra20. OK, fine with me
> I guess this was introduced during the consolidation of the MC drivers. Can
> you add the appropriate fixes tag?
> 

Sure, I can send v2 over next week.



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2018-07-20 16:42 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2018-07-20  8:02     ` Jon Hunter
2018-07-20 16:42       ` Dmitry Osipenko

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).