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 2/2] MIPS: Octeon: support all interfaces on CN66XX
Date: Tue, 26 Apr 2022 16:30:50 +0200 [thread overview]
Message-ID: <20220426143050.GC18291@alpha.franken.de> (raw)
In-Reply-To: <20220403025950.837085-2-stijn@linux-ipv6.be>
On Sun, Apr 03, 2022 at 05:59:50AM +0300, Stijn Tintel wrote:
> CN66XX_PASS1_0 has 7 interfaces, other revisions have 8 interfaces.
>
> Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
> ---
> arch/mips/cavium-octeon/executive/cvmx-helper.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/mips/cavium-octeon/executive/cvmx-helper.c b/arch/mips/cavium-octeon/executive/cvmx-helper.c
> index b22f664e2d29..6f49fd9be1f3 100644
> --- a/arch/mips/cavium-octeon/executive/cvmx-helper.c
> +++ b/arch/mips/cavium-octeon/executive/cvmx-helper.c
> @@ -61,6 +61,12 @@ int cvmx_helper_get_number_of_interfaces(void)
> {
> if (OCTEON_IS_MODEL(OCTEON_CN68XX))
> return 9;
> + if (OCTEON_IS_MODEL(OCTEON_CN66XX)) {
> + if (OCTEON_IS_MODEL(OCTEON_CN66XX_PASS1_0))
> + return 7;
> + else
> + return 8;
> + }
> if (OCTEON_IS_MODEL(OCTEON_CN56XX) || OCTEON_IS_MODEL(OCTEON_CN52XX))
> return 4;
> if (OCTEON_IS_MODEL(OCTEON_CN7XXX))
> --
> 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 ]
next 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 [PATCH 1/2] MIPS: Octeon: fix CN6640 hang on XAUI init 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 [this message]
2022-04-26 14:30 ` [PATCH 1/2] MIPS: Octeon: fix CN6640 hang on XAUI init Thomas Bogendoerfer
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=20220426143050.GC18291@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;
as well as URLs for NNTP newsgroup(s).