From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Parshuram Raju Thombare <pthombar@cadence.com>,
Sean Anderson <sean.anderson@seco.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: Milind Parab <mparab@cadence.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Antoine Tenart <atenart@kernel.org>,
"Russell King" <linux@armlinux.org.uk>
Subject: Re: [net-next PATCH v5] net: macb: Fix several edge cases in validate
Date: Thu, 4 Nov 2021 16:15:53 +0100 [thread overview]
Message-ID: <5305c72d-e8f0-c4cd-3a85-2f12a0f644c8@microchip.com> (raw)
In-Reply-To: <CY4PR07MB27576B46D37E39F9F1789A31C18C9@CY4PR07MB2757.namprd07.prod.outlook.com>
On 03/11/2021 at 11:14, Parshuram Raju Thombare wrote:
> Hi Sean,
>
> Thanks for this improvement.
>
>> + if (!macb_is_gem(bp) ||
>> + (bp->caps & MACB_CAPS_GIGABIT_MODE_AVAILABLE)) {
>> + have_1g = true;
>> + if (bp->caps & MACB_CAPS_PCS)
>> + have_sgmii = true;
>> + if (bp->caps & MACB_CAPS_HIGH_SPEED)
>> + have_10g = true;
>
> As I understand, MACB_CAPS_GIGABIT_MODE_AVAILABLE is used as a quirk in configs
> to prevent giga bit operation support, Nicolas should have more information about this.
That's right Parshuram.
> macb_is_gem() tells whether giga bit operations is supported by HW, MACB_CAPS_PCS indicate
> whether PCS is included in the design (needed for SGMII and 10G operation), MACB_CAPS_HIGH_SPEED
> indicate if design supports 10G operation.
>
> I believe this should be
>
>> + if (macb_is_gem(bp) &&
>> + (bp->caps & MACB_CAPS_GIGABIT_MODE_AVAILABLE)) {
>> + have_1g = true;
>> + if (bp->caps & MACB_CAPS_PCS)
>> + have_sgmii = true;
>> + if (bp->caps & MACB_CAPS_HIGH_SPEED)
>> + have_10g = true;
Regards,
Nicolas
--
Nicolas Ferre
prev parent reply other threads:[~2021-11-04 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 15:04 [net-next PATCH v5] net: macb: Fix several edge cases in validate Sean Anderson
2021-11-03 10:14 ` Parshuram Raju Thombare
2021-11-04 15:08 ` Sean Anderson
2021-11-04 15:15 ` Nicolas Ferre [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=5305c72d-e8f0-c4cd-3a85-2f12a0f644c8@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=atenart@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mparab@cadence.com \
--cc=netdev@vger.kernel.org \
--cc=pthombar@cadence.com \
--cc=sean.anderson@seco.com \
/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).