[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9235D6609DB808459E95D78E17F2E43D40D55B0A@CHN-SV-EXMX02.mchp-main.com>
Date: Tue, 1 May 2018 20:07:09 +0000
From: <Woojung.Huh@...rochip.com>
To: <f.fainelli@...il.com>, <netdev@...r.kernel.org>
CC: <andrew@...n.ch>, <rmk@...linux.org.uk>,
<linux-kernel@...r.kernel.org>, <davem@...emloft.net>,
<cphealy@...il.com>, <nikita.yoush@...entembedded.com>,
<vivien.didelot@...oirfairelinux.com>, <Nisar.Sayed@...rochip.com>,
<UNGLinuxDriver@...rochip.com>
Subject: RE: [RFC net-next 4/5] net: phy: Add support for IEEE standard test
modes
Hi Florian,
> Not sure I completely understand your suggestion, do you mean that I
> should break down the body of that function above such that there are
> per-speed lower level functions? Something like the pseudo-code below:
>
> genphy_set_test() {
> switch (mode) {
> case PHY_STD_TEST_MODE_100BASET2_1:
> ..
> case PHY_STD_TEST_MODE_100BASET2_3:
> return genphy_set_100baset2();
>
> case PHY_STD_TEST_MODE_1000BASET_1:
> ..
> case PHY_STD_TEST_MODE_1000BASET_4:
> return genphy_set_1000baset();
>
> case PHY_STD_TEST_MODE_8021BWQCQ_1:
> return genphy_set_100baset1();
>
> }
Yes, I should write pseudo code. Sorry about confusion.
User can override this function or expand to other modes.
Thanks.
Woojung
Powered by blists - more mailing lists