Message-ID: <20220610102028.p5nif76fncz2oyv7@mobilestation>
Date:   Fri, 10 Jun 2022 13:20:28 +0300
From:   Serge Semin <fancer.lancer@...il.com>
To:     Luca Ceresoli <luca@...aceresoli.net>
Cc:     Serge Semin <Sergey.Semin@...kalelectronics.ru>,
        Stephen Boyd <sboyd@...nel.org>,
        Philipp Zabel <p.zabel@...gutronix.de>,
        Michael Turquette <mturquette@...libre.com>,
        Marek Vasut <marek.vasut@...il.com>,
        Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
        Pavel Parkhomenko <Pavel.Parkhomenko@...kalelectronics.ru>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        linux-clk@...r.kernel.org, linux-mips@...r.kernel.org,
        linux-kernel@...r.kernel.org, Stephen Boyd <sboyd@...eaurora.org>
Subject: Re: [PATCH v4 2/8] clk: vc5: Fix 5P49V6901 outputs disabling when
 enabling FOD

On Fri, Jun 10, 2022 at 11:39:18AM +0200, Luca Ceresoli wrote:
> Hi Serge,
> 
> thank you for your patch!
> 
> On 10/06/22 09:21, Serge Semin wrote:
> > We have discovered random glitches during the system boot up procedure.
> > The problem investigation led us to the weird outcomes: when none of the
> > Renesas 5P49V6901 ports are explicitly enabled by the kernel driver, the
> > glitches disappeared. It was a mystery since the SoC external clock
> > domains were fed with different 5P49V6901 outputs. The driver code didn't
> > seem like bogus either. We almost despaired to find out a root cause when
> > the solution was found for a more modern revision of the chip. It turned
> > out the 5P49V6901 clock generator stopped its output for a short period of
> > time during the VC5_OUT_DIV_CONTROL register writing. The same problem has
> > was found for the 5P49V6965 revision of the chip and the was successfully
> > fixed in commit fc336ae622df ("clk: vc5: fix output disabling when
> > enabling a FOD") by enabling the "bypass_sync" flag hidden inside "Unused
> > Factory Reserved Register". Even though the 5P49V6901 registers
> > description and programming guide doesn't provide any intel regarding that
> > flag, setting it up anyway in the officially unused register completely
> > eliminated the denoted glitches. Thus let's activate the functionality
> > submitted in commit fc336ae622df ("clk: vc5: fix output disabling when
> > enabling a FOD") for the Renesas 5P49V6901 chip too in order to remove
> > the ports implicit inter-dependency.
> 

> Sadly, you have been through the same troubles I had on the 6965.

Hi Luca

Yeah, it was a nightmare fixing that weird problem. Thanks god you
have committed the solution. Last time I had to face something similar
was when I was fixing a problem in the IDT NTB controller, which caused
PCIe MRd TLPs successfully passed from one side to another, but not in
the opposite direction. I spent months trying to figure out the root
cause of the problem or at least find some workaround. I wrote several
messages to the support team but for some reason they didn't respond.
After all the struggle I've found the IDT PCIe bridges configuration
tool, hacked it's XML config files where I found the info regarding the
Vendor-specific PCIe config-space undocumented flags. It turned out that
by default the controller discarded the PCIe MRd responses coming from
the link-partner with non-zero device number. In order to make things
working a vendor-specific flag needed to be set.

> 
> > Fixes: dbf6b16f5683 ("clk: vc5: Add support for IDT VersaClock 5P49V6901")
> > Signed-off-by: Serge Semin <Sergey.Semin@...kalelectronics.ru>
> 
> Reviewed-by: Luca Ceresoli <luca@...aceresoli.net>
> Reviewed-by: Luca Ceresoli <luca.ceresoli@...tlin.com>
> 
> (not sure which address is appropriate as I sent patches to update to
> the Bootlin one and they are being applied one y one on the various
> maintainers branches)

Thanks. I'll use the top one then since it was used in the patch
Author tag.

-Sergey

> 
> -- 
> Luca

Powered by blists - more mailing lists