From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Stijn Tintel <stijn@linux-ipv6.be>
Cc: linux-mips@vger.kernel.org, rdunlap@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] MIPS: Octeon: fix CN6640 hang on XAUI init
Date: Tue, 26 Apr 2022 16:30:38 +0200 [thread overview]
Message-ID: <20220426143038.GB18291@alpha.franken.de> (raw)
In-Reply-To: <20220403025950.837085-1-stijn@linux-ipv6.be>
On Sun, Apr 03, 2022 at 05:59:49AM +0300, Stijn Tintel wrote:
> Some CN66XX series Octeon II chips seem to hang if a reset is issued on
> XAUI initialization. Avoid the hang by disabling the reset.
>
> Tested on SNIC10E.
>
> Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
> ---
> arch/mips/cavium-octeon/executive/cvmx-helper-xaui.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/mips/cavium-octeon/executive/cvmx-helper-xaui.c b/arch/mips/cavium-octeon/executive/cvmx-helper-xaui.c
> index fea71a85bb29..a92632223497 100644
> --- a/arch/mips/cavium-octeon/executive/cvmx-helper-xaui.c
> +++ b/arch/mips/cavium-octeon/executive/cvmx-helper-xaui.c
> @@ -156,8 +156,9 @@ int __cvmx_helper_xaui_enable(int interface)
> xauiCtl.u64 = cvmx_read_csr(CVMX_PCSXX_CONTROL1_REG(interface));
> xauiCtl.s.lo_pwr = 0;
>
> - /* Issuing a reset here seems to hang some CN68XX chips. */
> - if (!OCTEON_IS_MODEL(OCTEON_CN68XX_PASS1_X) &&
> + /* Issuing a reset here seems to hang some CN66XX/CN68XX chips. */
> + if (!OCTEON_IS_MODEL(OCTEON_CN66XX) &&
> + !OCTEON_IS_MODEL(OCTEON_CN68XX_PASS1_X) &&
> !OCTEON_IS_MODEL(OCTEON_CN68XX_PASS2_X))
> xauiCtl.s.reset = 1;
>
> --
> 2.35.1
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-04-26 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 2:59 Stijn Tintel
2022-04-03 2:59 ` [PATCH 2/2] MIPS: Octeon: support all interfaces on CN66XX Stijn Tintel
2022-04-26 14:30 ` Thomas Bogendoerfer
2022-04-26 14:30 ` Thomas Bogendoerfer [this message]
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=20220426143038.GB18291@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=stijn@linux-ipv6.be \
/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
all inboxes | Powered by JetHome®