U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Markus Niebel <Markus.Niebel@tq-group.com>,
	u-boot@lists.denx.de,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Alexander Stein <alexander.stein@ew.tq-group.com>
Subject: Re: [PATCH] tqma6: Fix DDR configuration
Date: Tue, 12 Dec 2023 17:21:30 +0100	[thread overview]
Message-ID: <20231212172130.2193caea@xps-13> (raw)
In-Reply-To: <CAOMZO5AwuiZAohLhRwFQx-UeL5eoxfCgVqVvM77+4eRKbmt6dA@mail.gmail.com>

Hi Fabio,

festevam@gmail.com wrote on Tue, 12 Dec 2023 13:11:53 -0300:

> On Fri, Nov 17, 2023 at 1:50 PM Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> >
> > Initially investigating a Linux network issue causing a lot of drop and
> > poor network performances on a custom system based on a TQMA6A module
> > (based on an iMX6Q), [1st link below].
> >
> > I eventually correlated my observations with a contention at the NIC
> > level when in concurrency with the graphics pipeline. Troubleshooting
> > this in the kernel lead to disabling DMA bursts accesses made by the IPU
> > in order to avoid triggering the QoS at the interconnect level, reducing
> > from 50 to 10% the drop rate on eth0, [2nd link below]. The solution
> > worked on my setup but not on others, which still suffered from
> > abnormally high drop rates even with this "fix".
> >
> > After looking a while into TQ Systems BSP I figured out a number of
> > differences in recent U-Boot out-of-tree patches they had in their
> > repository [3rd link]. Parsing the differences one after the other lead
> > me to this final solution.
> >
> > The reset pad of the DDR controller was apparently misconfigured, Bit
> > 18-19 picturing the "DDR select field". The current value b11 is
> > reserved. The only defined value as of version 6 of the iMX6Q manual was
> > b00 "DDR3 and LPDDR2 mode". In practice no register difference has been
> > spotted after changing this configuration but all issues tracked thus
> > far just vanished. All previous fixes have been proven irrelevant. Just
> > clearing this field solved all our network issues and the drop rate as
> > measured by iperf3 felt back to 0%.
> >
> > Link: https://lore.kernel.org/netdev/20231012193410.3d1812cf@xps-13/
> > Link: https://lists.freedesktop.org/archives/dri-devel/2023-October/428251.html
> > Link: https://github.com/tq-systems/u-boot-tqmaxx/commit/15eb6abbefbf6916c28467b85485911dad3da6bc
> > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>  
> 
> Applied, thanks.

Thanks a lot. Any chances you would have access to additional
information to explain how the network vs video pipeline
interact without this patch? I am eager to understand.

Cheers,
Miquèl

  reply	other threads:[~2023-12-12 16:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 15:00 [PATCH] tqma6: Fix DDR configuration Miquel Raynal
2023-11-29 18:21 ` Fabio Estevam
2023-12-12 16:11 ` Fabio Estevam
2023-12-12 16:21   ` Miquel Raynal [this message]
2023-12-12 16:31     ` Fabio Estevam
     [not found] <mailman.3902.1700255720.703.u-boot@lists.denx.de>
2023-11-23 13:04 ` Markus Niebel
2023-11-23 13:12   ` Miquel Raynal
2023-11-23 13:44     ` Alexander Stein
2023-11-23 13:54       ` Miquel Raynal

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=20231212172130.2193caea@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=Markus.Niebel@tq-group.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=festevam@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=u-boot@lists.denx.de \
    /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